I have 2 servers with Ubuntu 10.04 and mailman 2.1.13-1ubuntu0.2
Both servers have the same problem, the owner and/or the moderator of the
list don't receive notification of pending request. Also the sender does
a notification saying his email was hold. Each server hosts about 330 lists.
It is not an individual configuration but it's on all of them.
As administrator, I verified the option admin_immed_notify was at
yes. To be
sure I have everything set correctly, I created my own mailing list with
my email, etc.
and it is not working. I can't see anything in the postfix log or
The only clue I have is when I start mailman I have this:
# /etc/init.d/mailman start
close failed in file object destructor:
Error in sys.excepthook:
Original exception was:
* Starting Mailman master qrunner mailmanctl
Any help would be very appreciated!
We are using Mailman 2.15 and have an unusual problem that I was hoping
that someone can help me with. We have close to 109 lists running
successfully, however there are times when bounce processing sends the
following message (over 100 times) in the span of a few hours to one
user/subscriber to the list. They are not the admin:
This is a Mailman mailing list bounce action notice:
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
The original message was received at Mon, 7 May 2012 09:50:13 -0400 from
----- The following addresses had permanent fatal errors -----
(reason: 550 5.1.1 unknown or illegal user:
(reason: 550 #5.1.0 Address rejected.)
(reason: 550 Host unknown)
I understand why a user would get this message if they exceeded their
threshold, but why are over 100 of the same messages being sent to one
On Wed, May 9, 2012 at 4:01 PM, David <dave(a)fiteyes.com> wrote:
> Re: Giving away the secrets of 99.3% email delivery
> 1. Constantly monitor spam blacklists. We have a set of Nagios alerts
that regularly check if we’re listed on any delivery blacklists, and
whenever they go off we take whatever corrective action we need to get back
off the blacklist.
> 2. Have valid SPF records. Don’t impersonate your users. When running a
web app like Basecamp, which sends email that are generated by another
user, it can be tempting to send the email from that user (e.g., so that a
comment I wrote on Basecamp would appear to come from noah at 37signals dot
com), which might make people feel more comfortable. Unfortunately, this is
a surefire way to end up on spam lists, since you’ll likely be sending from
an IP address that does not have the valid SPF records. And chances are, if
the user’s domain does have an SPF record, it doesn’t include your
> 3. Sign the mail! DKIM and Domain Keys. Yahoo and Gmail both score signed
> 4. Dedicated and conditioned email sending IPs.
> 5. Configure reverse dns entries. Most of the “big boys” won’t accept
mail from your servers if your reverse dns entries don’t match. You might
need your IP provider to help with setting up these records.
> 6. Enroll in feedback loops. We haven’t automated our parsing of
feedback, but a daily / weekly review of feedback loop emails helps us know
when there’s an unhappy user, or other problem. Too many complaints and
you’ve got trouble.
I started by setting up an SPF record (#2 on the list above). However,
shortly after setting it up, we got a bounce with this reason:
SPF MAIL FROM check failed: [MAIL_FROM]
I searched a bit and came across things like this:
But nothing I found answered my questions.
Looking at the headers of the bounced message, I note:
Received-SPF: pass (domain of lists.example.com designates 10.10.10.99 as
That would seem to indicate things are OK, but maybe X-Originating-IP isn't
the line I need to be looking at... I'm not sure what [MAIL_FROM] (in the
SPF check failed line) matches in the email header.
Also, I note:
X-YahooFilteredBulk: 10.10.10.99 <-- what does "X-YahooFilteredBulk" mean?
And there is another value for this field.
These are the headers of the bounced message:
Subject: Failure Notice
Sorry, we were unable to deliver your message to the following address.
Remote host said: 550 5.7.1 SPF MAIL FROM check failed: [MAIL_FROM]
--- Below this line is a copy of the message.
Received: from [126.96.36.199] by nm1.bullet.mail.sp2.yahoo.com with NNFMP;
09 May 2012 21:51:02 -0000
Received: from [188.8.131.52] by tm13.bullet.mail.sp2.yahoo.com with
NNFMP; 09 May 2012 21:51:02 -0000
Received: from [184.108.40.206] by t5.bullet.mud.yahoo.com with NNFMP; 09
May 2012 21:51:01 -0000
Received: from [127.0.0.1] by omp1007.access.mail.mud.yahoo.com with NNFMP;
09 May 2012 21:51:01 -0000
X-Yahoo-Forwarded: from recipient(a)destination.com to
Received-SPF: pass (domain of lists.example.com designates 10.10.10.99 as
Authentication-Results: mta1017.biz.mail.mud.yahoo.com from=
lists.example.com; domainkeys=neutral (no sig); from=att.net;
dkim=permerror (bad sig)
Received: from 127.0.0.1 (EHLO localhost) (10.10.10.99)
by mta1017.biz.mail.mud.yahoo.com with SMTP; Wed, 09 May 2012 14:51:01
Received: from myhost.hostingprovider.com (localhost [127.0.0.1])
by localhost (Postfix) with ESMTP id E9CA1123AB;
Wed, 9 May 2012 21:43:23 +0000 (UTC)
Received: from fmailhost01.isp.att.net (fmailhost01.isp.att.net
[220.127.116.11]) by localhost (Postfix) with ESMTP id 1D84D123A4
for <list(a)lists.example.com>; Wed, 9 May 2012 20:52:06 +0000 (UTC)
DKIM-Signature: v=1; q=dns/txt; d=att.net; s=dkim01; i=member1(a)domain.net;
a=rsa-sha256; c=relaxed/relaxed; t=1336596725; h=Content-Type:
Received: from homecomputer3
by worldnet.att.net (frfwmhc01) with SMTP
id <20120509205204H0100sdv2pe>; Wed, 9 May 2012 20:52:05 +0000
From: "Member One" <member1(a)domain.net>
To: "'Example Discussion'" <list(a)lists.example.com>
Date: Wed, 9 May 2012 16:52:07 -0400
X-Mailer: Microsoft Office Outlook 12.0
X-Mailman-Approved-At: Wed, 09 May 2012 21:43:22 +0000
Subject: [Example Discussion 110] Re: Example Subject
Reply-To: Example Discussion <list(a)lists.example.com>
List-Id: Example Discussion <all.lists.example.com>
> Ian Prietz wrote:
> >We have multiple lists set up with our Mailman host. We have had some
> >delivery issues recently. One of the new lists has had some real trouble getting the
> >messages delivered. However, there are members of "LIST A" that are also
> >member of the problem list, "LIST B".
> might possibly be related to a recipient's
> having list_a-bounces at example.com but not list_b-bounces at example.com
> in her address book.
> Mark Sapiro <mark at msapiro.net>
Mark, In your response above, why did you specify that "list_a-bounces
at example.com" should be added to the recipient's address book
instead of "list_a at example.com"?
I had discuss the similar issue couple of Months back here.
Actually the mails sent by the senders are not reaching to all the subscribers of my mailing list.
I got some steps here and forwarded them to our web service provider but they could not resolve the issue.
After facing huge problems, I finally shifted to the new service provider and they are Internationally known as very good service provider and their mail delivery and other services seem to be working fine but the issue of non delivery of E-mails to some users still remain there.
I have discussed this matter with other moderators of two different mailing list and they told me that they also confront the same issue some time. so what does it mean? Is this a bug on Mailman? Can we expect not to be happened in mailman 3 in the coming future?
Please, I would appreciate if someone can make me understand to do something in simple steps.
How can I pull out from the cli how many topics are configured in
mailman, and who's subscribed to them? Do I need to write a script or
is one available somewhere on the intertubes?
Note: I know I can check the admin page for the list of topics.
Kanwar Ranbir Sandhu
Linux 3.3.2-6.fc16.x86_64 x86_64 GNU/Linux
18:33:23 up 1 day, 11:15, 2 users, load average: 0.00, 0.03, 0.05
What is the solution for this?
OSError: [Errno 13] Permission denied:
# ls -la /var/lib/mailman/archives/private/list/attachments
ls: cannot access /var/lib/mailman/archives/private/list/attachments: No
such file or directory
Should I just create the directory and set permissions? Why didn't it get