MySQL Bugs: #19941: leaving emails on server/blocked messages

Bug #19941	leaving emails on server/blocked messages
Submitted:	19 May 2006 13:05	Modified:	22 May 2006 12:23
Reporter:	Rick Mulder	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Eventum	Severity:	S3 (Non-critical)
Version:	1.7.1	OS:	Linux (Debian Linux)
Assigned to:	Bryan Alsdorf	CPU Architecture:	Any

Description:
When enabling the option "Leave Copy of Messages On Server" blocked messages are being retrieved over and over again. The next morning your mailbox is flooded with '[blocked]' emails of the eventum system.

How to repeat:
Enable the option 'Leave Copy of Messages On Server' in the settings. Create issue by sending an email (not an eventum user) and reply to the auto-notification mail you receive after that.

Every time that the eventum mailbox is checked with the script 'download_emails.php' a new message is being send over and over again and an internal note is created over and over again.

The problem seems to only occur with blocked messages. When you authorize this user (manual) or choose to convert internal-note to email and then authorize, the problem is gone...

Suggested fix:
I guess the retrieved emails are compared to the emails in the system and not to the internal-notes. 

I think that if the system retrieves an email from an user (that doesn't exists in eventum) this user should be automaticaly authorized to reply to his own issue.

Possible solution for this bug

Attachment: bug_19941_fix.diff (text/x-patch), 1.25 KiB.

Rick,

I have attached a diff to this bug that should solve your problem. Please apply it and let me know how it works for you.

Best Regards,
/bryan

Bryan,

I applied the patch but it didn't change anything. The system still reads messages the are already imported into the system.

Rick,

I had a slight bug in my previous diff. On line #2431, change $t['full_email'] to $email['full_email'].

I have tested this, and it solves the problem. It will be in our next release.

Best Regards,
/bryan

Bryan,

Problem solved.. ;-)