mailman unsubscribing people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | GNU Mailman |
Undecided
|
Mark Sapiro | ||
Bug Description
CRITICAL!!!!
Today 2/10/12) at 3:10 p.m. CST, the mailman software started unsubscribing people to our mailing list - PURRS1 mailing list. They receive a message from <email address hidden> and are then deleted from the mailing list. Beofre this we had over 2000 addresses in our mailing list, now we are down to 776.
I contacted LunarPages.Com who hosts our website, but they said we need to contact you about this problem. Please help ASAP.
| Mark Sapiro (msapiro) wrote : | #1 |
| Changed in mailman: | |
| assignee: | nobody → Mark Sapiro (msapiro) |
| status: | New → Incomplete |
Hi.
We think it was bounceprocessing but there is an errror in it..all those emails did not bounce back..reading down it appears that lunarpages says we hit some quota that may have caused the error..we are switching to constant contact once this is fixed. Please note the following email string and the two attachments and see if this helps.Thanks. Barb -----Original Message-----
From: <email address hidden>
Sender: <email address hidden>
Date: Fri, 10 Feb 2012 13:10:23
To: <email address hidden>
Subject: Bounce action notification
This is a Mailman mailing list bounce action notice:
List: Purrs1
Member: <email address hidden>
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
<email address hidden>.
--Forwarded Message Attachment--
Date: Fri, 10 Feb 2012 20:55:28 +0000
From: <email address hidden>
To: <email address hidden>
Subject: Delivery failure
Message from yahoo.com.
Unable to deliver message to the following address(es).
<email address hidden>:
This user doesn't have a yahoo.com account (<email address hidden>) [0]
<email address hidden>:
Sorry your message to <email address hidden> cannot be delivered. This account has been disabled or discontinued [#102].
<email address hidden>:
This user doesn't have a yahoo.com account (<email address hidden>) [0]
<email address hidden>:
This user doesn't have a yahoo.com account (<email address hidden>) [0]
<email address hidden>:
Sorry your message to <email address hidden> cannot be delivered. This account has been disabled or discontinued [#102].
--- Original message follows.
The original message is over 5K. Message truncated.
Return-Path: <email address hidden>
Received-SPF: none (domain of purrsnaperville.org does not designate permitted sender hosts)
X-YMailISG: _CdUgx0WLDsTDSe
ZLjLeL.
qVqX2IXaZPCY2X
VdJXjdnEEq6XyF
R1RcWZmQ2hrFcE
wDBE.cDUyi2jio
EY9rwC61SvvLnu
e4XkfHvMVtPmt.
x6mY7opbrUBN2r
lOdzi9K2NQnzwJ
StoqBxZzo3_
PU3ySCEJJ3Ocfi
OBeum77B1H1Hh5
_yYEP02TUhs96T
HfEHAvr46C3fVy
C.2riMO0iMa1FJ
T0DzVf_
_L.tPuINApf4g.
pMievipShk529q
L9v7l4zuvI3iIW
Here's another email string.
Also, we'd like to know if mailman has a backup of our email subscription list from Thursday 2/9/12 or earlier before any of this occurred. We would want to have it restored as we think we lost around 1700 emails.
Thanks.
Barb
Subject: Fw: Bounce action notification
To: <email address hidden>
From: <email address hidden>
Date: Sat, 11 Feb 2012 14:17:20 +0000
This has the quota at the end too
Sent via BlackBerry by AT&T
-----Original Message-----
From: <email address hidden>
Sender: <email address hidden>
Date: Fri, 10 Feb 2012 13:10:24
To: <email address hidden>
Subject: Bounce action notification
This is a Mailman mailing list bounce action notice:
List: Purrs1
Member: <email address hidden>
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
<email address hidden>.
--Forwarded Message Attachment--
From: <email address hidden>
To: <email address hidden>
Subject: Mail delivery failed: returning message to sender
Date: Fri, 10 Feb 2012 20:56:15 +0000
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
<email address hidden>
SMTP error from remote mail server after end of data:
host mta3.am0.
dd This user doesn't have a rocketmail.com account (<email address hidden>) [-15] - mta1069.
<email address hidden>
SMTP error from remote mail server after RCPT TO:<email address hidden>:
host MX2.firstam.
<email address hidden>
SMTP error from remote mail server after RCPT TO:<email address hidden>:
host hrndva-
550 5.1.1 - Invalid mailbox: <email address hidden>
<email address hidden>
SMTP error from remote mail server after RCPT TO:<email address hidden>:
host mailin-
Recipient address rejected: aol.com
<email address hidden>
SMTP error from remote mail server after RCPT TO:<email address hidden>:
host mailin-
Recipient address rejected: aol.com
<email address hidden>
SMTP error from remote mail server after RCPT TO:<email address hidden>:
host mailin-
Recipient address rejected: aol.com
<email address hidden>
SMTP error from remote mail server after RCPT TO:<email address hidden>:
host mx1.hotmail.com [65.54.188.94]: 550 Requested action not taken:
mailbox unavailable
<email address hidden>
SMTP error from remote mail server after RCPT TO:<email address hidden>:
host mx01.wow.
<email address hidden>
SMTP error from remote mail server after RCPT TO:<Feber...
| Mark Sapiro (msapiro) wrote : | #4 |
All of the reports in comment #2 appear to be legitimate bounces. The first 14 addresses in the notice in comment #3 also appear to be legitimate. The remaining "Domain purrsnaperville.org has exceeded the max emails per hour (400) allowed. Message discarded." messages indeed appear to be the result of a quota on outgoing mail from your domain imposed by your hosting provider. This is not a Mailman issue. Mailman has been told the address was undeliverable, so Mailman treats it as a bounce.
The problem is your hosting service apparently can't support a mailman list with more than about 400 subscribers and can't support even that many if there is more than one post in an hour. This probably means it won't support anything that generates mail to more than 400 recipients in an hour.
This is something you will have to discuss with your hosting provider. There is little that Mailman can do about it. See the FAQ at <http://
Regarding backups, only the hosting provider can tell you if they made any backups and if they still have them. They would need to restore Mailman's lists/purrs1/
| Changed in mailman: | |
| status: | Incomplete → Invalid |
The members were almost certainly unsubscribed by Mailman's bounce processing. Your hosting provider can review Mailman's 'bounce' log to verify this and can examine the logs of the outgoing MTA to possibly find out more.
You can review your list's bounce processing settings for appropriateness and ensure that all the owner notifications are turned on so that you will receive notification when a member's delivery is disabled by bounce and before the member is removed.
Without additional information to indicate that this is actually a bug and not a result of normal bounce processing, I can only assume that this is not a bug.