August 14, 2014
I have the mail queue plugin installed in a multi-site configuration so all my subscribe2 mail is going to a single table. That table is full of messages that are attempting to be sent and failing.
I know the larger problem is having bogus email addresses that are ‘verified’ in subscribe2, but in most cases they were valid addresses while those folks were employed with a school district and now they’ve moved on. Our subscriber base is pretty mobile so this is always going to be a problem.
After the number of bogus messages is greater than the send threshold, the queue will stop sending messages because its clogged up with undeliverable email that it keeps trying to submit.
What should probably happen is for subscribe2 to un-subscribe the person from the list but it doesn’t look like the mail queue is saving enough information to tell subscribe2 an email address is bogus for a specific list.
wpmq needs to have a way to persist information about send failures including the number of delivery attempts, the kind of failure, and the list it came from.
That would then enable subscribe2 to deal with it or the mail queue to auto purge messages after a failure threshold is reached.
December 13, 2012