View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0010174||phpList 3 application||Batch Processing||public||03-06-07 10:48||23-05-12 16:00|
|Target Version||Fixed in Version|
|Summary||0010174: Processqueue gets stuck in infinite loop with concatenated email addresses|
|Description||I found that the processqueue will get stuck in an infinite loop if two email address get concatenated accidentally. That is, it keeps trying to send over and over and over to that one address but keeps failing because it's a bad address.|
Email format like this: "firstname.lastname@example.org;email@example.com" will be imported and NOT flagged as invalid and "reconcile users" does not pick it up.
Of course the ISP fails it because it's invalid, but processqueue keeps trying to send it every batch time.
Can you folks add a check in the import function to guard against two @ signs?
This is a problem because as process queue gets stuck in an infinite loop I cannot tell if the mails have been successfully sent...
|Tags||No tags attached.|
|duplicate of||0013672||new||how often to retry sending to an address that fails, and give up|
|related to||0002705||closed||PHPList v2.11 release|
|related to||0014970||resolved||michiel||"Duplicate" emails selected but not counted in total sent. Message remains "inprocess".|
|related to||0011976||resolved||michiel||detect process queue looping and cut if off|
OK, I've tested this with some test lists and all the people apart from those with a concatenated email receive the message fine so this is really a just a minor issue not a major one. Just have to leave the process queue page after I think all messages sent....
Still annoying as I get multiple report messages delivered too - one each loop.
Seems related to http://mantis.phplist.com/view.php?id=11976
Similar issues have also been reported in these forum threads:
I've noted the same behavior when the email is valid, but it does not exist. I tested it using an email in my domain like firstname.lastname@example.org
This issue has also been reported for recent releases, including 2.10.12/13.
In this forum post, thisisit3 suggests a minor code change as a (temporary) fix: http://forums.phplist.com/viewtopic.php?p=31375#p31375