Unsubscribe queue resend to patron after the email was subscribed
Hello,
Previously, we set our mailing list to do 2-steps unsubscribe (email confirmation). We have a patron, who was unsubscribe from our mailing list on Mar 1st. The subscribe log has the entry (delete test@web-ster.com; email confirmed). On May 6th, the patron then received an email states that the unsubscribe didn't go through due to invalid confirmation string. We search the list and couldn't find the patron listed anymore. How do we check and clear pending queues so patrons wont receive these notices again?
Thank you,
Here is the bounce email message:
The results of your email command are provided below. Attached is your original message.
Results: Invalid confirmation string. Note that confirmation strings expire approximately 3 days after the initial subscription request. If your confirmation has expired, please try to re-submit your original request or message.
Unprocessed: RE: Your confirmation is required to leave the CSD_parents mailing list Remove from this mailing list plz. -----Original Message----- From:
csd_parents-confirm+64c6698239b5f1f3cc281ed426738364ff3e7bdd@mailman.canby.k 12.or.us
[mailto:csd_parents-confirm+64c6698239b5f1f3cc281ed426738364ff3e7bdd@mailman .canby.k12.or.us] Sent: Friday, March 01, 2013 1:31 PM To: test@web-ster.com Subject: Your confirmation is required to leave the CSD_parents mailing list Mailing list removal confirmation notice for mailing list CSD_parents We have received a request for the removal of your email address, "test@web-ster.com" from the csd_parents@mailman.canby.k12.or.us mailing list. To confirm that you want to be removed from this mailing list, simply reply to this message, keeping the Subject: header intact. Or visit this web page:
http://mailman.canby.k12.or.us/mailman/confirm/csd_parents/64c6698239b5f1f3c c281ed426738364ff3e7bdd
Ignored: Or include the following line -- and only the following line -- in a message to csd_parents-request@mailman.canby.k12.or.us:
confirm 64c6698239b5f1f3cc281ed426738364ff3e7bddNote that simply sending a `reply' to this message should work from most mail readers, since that usually leaves the Subject: line in the right form (additional "Re:" text in the Subject: is okay).
On 06/10/2013 03:17 PM, Hung Phan wrote:
Previously, we set our mailing list to do 2-steps unsubscribe (email confirmation). We have a patron, who was unsubscribe from our mailing list on Mar 1st. The subscribe log has the entry (delete test@web-ster.com; email confirmed). On May 6th, the patron then received an email states that the unsubscribe didn't go through due to invalid confirmation string. We search the list and couldn't find the patron listed anymore. How do we check and clear pending queues so patrons wont receive these notices again?
Your patron requested unsubscribe and answered the confirmation on Mar 1 and was then removed from the list. Subsequently on May 6 the patron replied again to the original May 1 confirmation email which was still in his/her mailbox. This time the confirmation token had expired and that was reported back to the patron.
Mailman didn't queue or resend anything.
Also, I'm sure it's not relevant to this issue, but your post to mailman-users was stuck in a gmail server for over 4 days.
Received: by mail-pa0-f45.google.com with SMTP id bi5so1209161pad.4 for mailman-users@python.org; Fri, 14 Jun 2013 20:32:15 -0700 (PDT) [...] Received: from [10.30.163.42] (host-198-236-7-20.canby.k12.or.us. [198.236.7.20]) by mx.google.com with ESMTPSA id nt6sm11806639pbb.4.2013.06.10.15.17.52 for mailman-users@python.org (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 10 Jun 2013 15:17:53 -0700 (PDT)
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
Your patron requested unsubscribe and answered the confirmation on Mar 1 and was then removed from the list. Subsequently on May 6 the patron replied again to the original May 1 confirmation email which was still in his/her mailbox. This time the confirmation token had expired and that was reported back to the patron.
[Be careful, Mark. It's true in my experience that in most cases like this it's due to some action by the subscriber, but let's not start by blaming the victim.]
As Mark explained, there is no need for administrative action, because Mailman only sends these messages only in response to a mail being received. If the subscriber doesn't send another confirmation, there shouldn't be any more responses.
While Mailman didn't queue or resend, there are several possibilities for mail system failure outside of Mailman that could cause this. It's not necessarily the case that the user sent more than one response, and it's possible that the mail that triggered the response was injected into the mail system months ago. In that case, it could recur, but it's a problem elsewhere in the mail system that you should investigate; you may be losing mail. You should be concerned, since your post to mailman-users was also delayed unreasonably long.
In order to do more than speculate, we need to see the headers, not the content, of the error mail received by the user. Without looking at those headers, the most we can say, as Mark said, is that statistically the most likely explanation is that the user confirmed twice.
Regards,
participants (3)
-
Hung Phan -
Mark Sapiro -
Stephen J. Turnbull