0012345: Mantis may stop to send email when it encounters an invalid email address

ID	Project	Category	View Status	Date Submitted	Last Update
0012345	mantisbt	email	public	2010-09-14 04:15	2014-02-12 12:54

Reporter	ldsandon	Assigned To	dregad
Priority	normal	Severity	major	Reproducibility	random
Status	closed	Resolution	no change required
Product Version	1.2.2

Summary	0012345: Mantis may stop to send email when it encounters an invalid email address
Description	It looks that Mantis may stop to send email when it encounters an invalid address. Our system had a queue of about 3000 undelivered email. Sometimes when a mail was triggered it was delivered alone, sometimes with some other, often just enqueued. After we truncated the email table, we observed that the mail flow was ok until we spotted an invalid mail address (a name with a "c" instead of a "k") in the email table, which was never removed. From then on, Mantis started again to have issue delivering email. What happens when the mail sending code can't send a mail? Is the random behaviour due to the actual order of the query result? I would also suggest to delete undelivered mails after a given number of retries, or after x days, when delivering is not possible.
Tags	No tags attached.

ldsandon 2010-09-21 04:44 reporter ~0026826	Additional info: mail server is QMail with chkuser active. Since we switched to the async mail delivery with the cronjob (and of course corrected addresses), the mail queue is emptied correctly.

dregad 2012-08-17 07:05 developer ~0032605	Would you be able to test this with a nightly build >= 18-Aug-2012 and report if problem still exists. With regards to purging the email queue, you should use the relevant admin page (http://url/to/mantis/admin/email_queue.php)

ldsandon 2012-08-22 17:55 reporter ~0032620	I'm not able to test on the actual system because it's a production system and I can't install a nightly build. I'll ask my system administator to make a backup of the database to perform a test as soon as possible.

dregad 2012-08-23 04:09 developer ~0032624	Thanks for that. Let me know how it goes.

dregad 2012-10-06 05:48 developer ~0033058	You did not provide any feedback; I assume that the issue no longer occurs using a recent nightly build, and will be resolved in upcoming stable release 1.2.12 Feel free to reopen the issue at a later time and provide the requested information.