Help with list mail not sending
Hello,
I've gone through all the steps in http://wiki.list.org/display/DOC/4.78+Troubleshooting-+No+mail+going+out+to+... but I'm still unable to get email to send out on my mailing list.
I'm using Postfix and Mailman 2.1.12 on an Ubuntu server. Most things work fine: the web interface
- Users get subscribe/unsubscribe and welcome emails
- Web interface works as expected, can create new lists and the like
- Emails sent to the list get added to the archive, viewable through
However, two kind of major things don't work:
- Emails sent to the list don't get sent to subscribers
- Members can't view the subscriber list through the listinfo page
The fact that welcome emails get sent but mails to the list don't baffles me. Here are the Postfix logs from a welcome email that gets sent properly:
Sep 10 12:18:30 CTNSRV postfix/smtpd[11951]: A76E242BF0: client=CTNSRV[127.0.0.1] Sep 10 12:18:30 CTNSRV postfix/cleanup[11955]: A76E242BF0: message-id=<mailman.0.1284135509.11950.mailman@ctnsrv.uwaterloo.ca> Sep 10 12:18:30 CTNSRV postfix/qmgr[31165]: A76E242BF0: from=<mailman-bounces@ctnsrv.uwaterloo.ca>, size=775, nrcpt=1 (queue active) Sep 10 12:18:32 CTNSRV postfix/smtp[11956]: A76E242BF0: to=<tbekolay@gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.95.27]:25, delay=1.5, delays=0.08/0.02/0.27/1.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1284136169 f15si7083603ibb.1) Sep 10 12:18:32 CTNSRV postfix/qmgr[31165]: A76E242BF0: removed
And here are the Postfix logs from an email that Mailman tries to send to list subscribers:
Sep 10 12:19:09 CTNSRV postfix/smtpd[11967]: 0415246459: client=CTNSRV[127.0.0.1] Sep 10 12:19:09 CTNSRV postfix/cleanup[11955]: 0415246459: message-id=<AANLkTimPGM63MsD3rv8FUPL8FkCiyEs_XZWbQLgZV71s@mail.gmail.com> Sep 10 12:19:09 CTNSRV postfix/qmgr[31165]: 0415246459: from=<mailman-bounces@ctnsrv.uwaterloo.ca>, size=2693, nrcpt=1 (queue active) Sep 10 12:19:09 CTNSRV postfix/smtp[11969]: 0415246459: to=<tbekolay@gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.95.27]:25, delay=0.69, delays=0.05/0.01/0.13/0.5, dsn=2.0.0, status=sent (250 2.0.0 OK 1284136207 f15si7070693ibb.27) Sep 10 12:19:09 CTNSRV postfix/qmgr[31165]: 0415246459: removed
Yet the first email appears in my inbox and the second one doesn't.
Any help would be greatly appreciated!
Trevor Bekolay wrote:
^^^^^^^^^^Google throws it away. See the FAQ at <http://wiki.list.org/x/2IA9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Trevor Bekolay wrote:
What happens when they try?
Is Privacy options... -> Subscription rules -> private_roster set to 'Anyone' or 'List members'?
Is General Options -> new_member_options -> Conceal the member's address unchecked?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks a lot, mail is sending fine now (as it always did, apparently).
The problem, for reference if anyone else has this issue (getting "You must supply a valid email address." when trying to see the subscribers list), the problem was in editing the html for the listinfo page. <MM-Form-End> was deleted, but <MM-Subscribe-Form-Start> remained, so the <MM-Roster-Form-Start> tag was basically getting ignored.
On Sat, Sep 11, 2010 at 10:32 AM, Mark Sapiro <mark@msapiro.net> wrote:
Trevor Bekolay wrote:
Mailman 2.1.14, currently in the release cycle (see <http://mail.python.org/pipermail/mailman-announce/2010-September/000153.html>) with the final targeted for next Monday, addresses this at least partially by moving the <MM-Subscribe-Form-Start> tag closer to the start of the actual subscribe form where it is less likely to be overlooked when editing the page to remove the subscribe form.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
Is there any script or method that can export 1 or all lists to a "common" format?
What's involved in migrating to a new version of Mailman?
regards
Steven Jones Technical Specialist Linux/Vmware Tele 64 4 463 6272 Victoria University Kelburn New Zealand
On Tue, Sep 14, 2010 at 11:24 PM, Steven Jones <Steven.Jones@vuw.ac.nz>wrote:
What do you mean by a common format?
Grab the source and extract it, i.e. mailman-2.1.14, then read the file named UPGRADING.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
"If you have nothing good to say about someone, just shut up!." -- Lucky Dube
Hi,
"common format"
I had no idea what they meant.....neither did they.....
I was just told to get an answer....
;?
I think they mean something a Microsoft (based) product can read and import.....
regards
Steven Jones Technical Specialist Linux/Vmware Tele 64 4 463 6272 Victoria University Kelburn New Zealand
From: Odhiambo Washington [mailto:odhiambo@gmail.com] Sent: Wednesday, 15 September 2010 9:14 a.m. To: Steven Jones Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Exporting or upgrading mailman lists
On Tue, Sep 14, 2010 at 11:24 PM, Steven Jones <Steven.Jones@vuw.ac.nz<mailto:Steven.Jones@vuw.ac.nz>> wrote: Hi,
- Is there any script or method that can export 1 or all lists to a "common" format?
What do you mean by a common format?
- What's involved in migrating to a new version of Mailman?
Grab the source and extract it, i.e. mailman-2.1.14, then read the file named UPGRADING.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
"If you have nothing good to say about someone, just shut up!." -- Lucky Dube
Steven Jones wrote:
Mailman keeps three kinds of data - archives, list configuration and list membership (including member options).
In an installation with default global archiving settings there is both an HTML archive and a global *nix mbox, both of which can be considered "common formats". The mbox can be used to rebuild the HTML archive. The mbox is the definitive archive containing maximum information.
Again, in most Mailman installations (those with the default MemberAdaptor), the list configuration and membership data are all saved in a single Python pickle (the lists/LISTNAME/config.pck file). If you are interested in moving a list to another Mailman installation of the same or newer or in some cases, older version, this file and the archives are all you need to move.
There are also various scripts included with Mailman to extract list configuration or membership to flat text files.
Various aspects of all this are covered in the FAQ at <http://wiki.list.org/x/AgA3>, particularly articles such as <http://wiki.list.org/x/aYA9>, <http://wiki.list.org/x/oIA9> and the posts linked from <http://wiki.list.org/x/2oA9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Steven Jones writes:
I had no idea what they meant.....neither did they.....
My suggestion is to put your resume in a common format; this company is not long for this world. ;-) More seriously (unless and until my speculation proves correct :-/ ) ...
I think they mean something a Microsoft (based) product can read and import.....
What do they want from the lists? If it's just full name and email address, then "bin/list_members --fullnames $LIST_NAME"[1] from the mailman directory will spew a list of lines of the form "First M. Last <inbox@firm.tld>", which you can then run through "sed -e 's/ </,/' -e 's/>//'" or similar to get a CSV file that any program should be able to read. They also probably should be able to read the raw text output, since that's a standard format. You probably should grep for double quotes and commas in the original output before trusting that sed script, of course.
If they want user config parameters (like "nomail" or "moderated"), that's a little harder.
I don't think the list config parameters (which you get from bin/config_list)
Typically that's all you need to do. ISTR that in the case of 2.1.9 to 2.1.10 or later, there are a couple of parameters in mm_cfg.py which you should confirm are appropriate, and a couple more new ones in Defaults.py that you should consider customizing (by adding them to mm_cfg.py, of course).
IIRC, I looked but didn't need to touch anything.
And, of course, when in doubt, you know where to find us. :-)
Footnotes: [1] Just bin/list_members gives you a usage message. You may be interested in the --output, --preserve, and --unicode options, depending on your needs and the configuration of your lists.
Trevor Bekolay wrote:
^^^^^^^^^^Google throws it away. See the FAQ at <http://wiki.list.org/x/2IA9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Trevor Bekolay wrote:
What happens when they try?
Is Privacy options... -> Subscription rules -> private_roster set to 'Anyone' or 'List members'?
Is General Options -> new_member_options -> Conceal the member's address unchecked?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks a lot, mail is sending fine now (as it always did, apparently).
The problem, for reference if anyone else has this issue (getting "You must supply a valid email address." when trying to see the subscribers list), the problem was in editing the html for the listinfo page. <MM-Form-End> was deleted, but <MM-Subscribe-Form-Start> remained, so the <MM-Roster-Form-Start> tag was basically getting ignored.
On Sat, Sep 11, 2010 at 10:32 AM, Mark Sapiro <mark@msapiro.net> wrote:
Trevor Bekolay wrote:
Mailman 2.1.14, currently in the release cycle (see <http://mail.python.org/pipermail/mailman-announce/2010-September/000153.html>) with the final targeted for next Monday, addresses this at least partially by moving the <MM-Subscribe-Form-Start> tag closer to the start of the actual subscribe form where it is less likely to be overlooked when editing the page to remove the subscribe form.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
Is there any script or method that can export 1 or all lists to a "common" format?
What's involved in migrating to a new version of Mailman?
regards
Steven Jones Technical Specialist Linux/Vmware Tele 64 4 463 6272 Victoria University Kelburn New Zealand
On Tue, Sep 14, 2010 at 11:24 PM, Steven Jones <Steven.Jones@vuw.ac.nz>wrote:
What do you mean by a common format?
Grab the source and extract it, i.e. mailman-2.1.14, then read the file named UPGRADING.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
"If you have nothing good to say about someone, just shut up!." -- Lucky Dube
Hi,
"common format"
I had no idea what they meant.....neither did they.....
I was just told to get an answer....
;?
I think they mean something a Microsoft (based) product can read and import.....
regards
Steven Jones Technical Specialist Linux/Vmware Tele 64 4 463 6272 Victoria University Kelburn New Zealand
From: Odhiambo Washington [mailto:odhiambo@gmail.com] Sent: Wednesday, 15 September 2010 9:14 a.m. To: Steven Jones Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Exporting or upgrading mailman lists
On Tue, Sep 14, 2010 at 11:24 PM, Steven Jones <Steven.Jones@vuw.ac.nz<mailto:Steven.Jones@vuw.ac.nz>> wrote: Hi,
- Is there any script or method that can export 1 or all lists to a "common" format?
What do you mean by a common format?
- What's involved in migrating to a new version of Mailman?
Grab the source and extract it, i.e. mailman-2.1.14, then read the file named UPGRADING.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
"If you have nothing good to say about someone, just shut up!." -- Lucky Dube
Steven Jones wrote:
Mailman keeps three kinds of data - archives, list configuration and list membership (including member options).
In an installation with default global archiving settings there is both an HTML archive and a global *nix mbox, both of which can be considered "common formats". The mbox can be used to rebuild the HTML archive. The mbox is the definitive archive containing maximum information.
Again, in most Mailman installations (those with the default MemberAdaptor), the list configuration and membership data are all saved in a single Python pickle (the lists/LISTNAME/config.pck file). If you are interested in moving a list to another Mailman installation of the same or newer or in some cases, older version, this file and the archives are all you need to move.
There are also various scripts included with Mailman to extract list configuration or membership to flat text files.
Various aspects of all this are covered in the FAQ at <http://wiki.list.org/x/AgA3>, particularly articles such as <http://wiki.list.org/x/aYA9>, <http://wiki.list.org/x/oIA9> and the posts linked from <http://wiki.list.org/x/2oA9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Steven Jones writes:
I had no idea what they meant.....neither did they.....
My suggestion is to put your resume in a common format; this company is not long for this world. ;-) More seriously (unless and until my speculation proves correct :-/ ) ...
I think they mean something a Microsoft (based) product can read and import.....
What do they want from the lists? If it's just full name and email address, then "bin/list_members --fullnames $LIST_NAME"[1] from the mailman directory will spew a list of lines of the form "First M. Last <inbox@firm.tld>", which you can then run through "sed -e 's/ </,/' -e 's/>//'" or similar to get a CSV file that any program should be able to read. They also probably should be able to read the raw text output, since that's a standard format. You probably should grep for double quotes and commas in the original output before trusting that sed script, of course.
If they want user config parameters (like "nomail" or "moderated"), that's a little harder.
I don't think the list config parameters (which you get from bin/config_list)
Typically that's all you need to do. ISTR that in the case of 2.1.9 to 2.1.10 or later, there are a couple of parameters in mm_cfg.py which you should confirm are appropriate, and a couple more new ones in Defaults.py that you should consider customizing (by adding them to mm_cfg.py, of course).
IIRC, I looked but didn't need to touch anything.
And, of course, when in doubt, you know where to find us. :-)
Footnotes: [1] Just bin/list_members gives you a usage message. You may be interested in the --output, --preserve, and --unicode options, depending on your needs and the configuration of your lists.
participants (5)
-
Mark Sapiro -
Odhiambo Washington -
Stephen J. Turnbull -
Steven Jones -
Trevor Bekolay