[Mailman-Users] Gmail RFC 2822
I am not sure the best place to solve this problem but I will start with this list since the problem is impacting a heavy traffic mailman listserv. Google recently started enforcing only a single From: header in RFC2822 causing bounces to members of a very heavy traffic list. A single person with bad mail client configuration is getting all of the Google Apps recipients removed from a list frequently. Postfix log entry: May 15 8:49:57 list01 postfix/smtp[27955]: 35C865058D2: to=< jsm...@example.com>, relay=aspmx.l.google.com[74.125.137.27]:25, delay=3.1, delays=0.07/2.3/0.03/0.61, dsn=5.7.1, status=bounced (host aspmx.l.google.com[74.125.137.27] said: 550-5.7.1 [126.24.19.8 11] Our system has detected that this message is not 550-5.7.1 RFC 2822 compliant. To reduce the amount of spam sent to Gmail, this 550-5.7.1 message has been blocked. Please review 550 5.7.1 RFC 2822 specifications for more information. f47si18577759yhf.187 - gsmtp (in reply to end of DATA command)) http://webapps.stackexchange.com/questions/42771/emails-sent-to-gmail-domain-suddenly-not-rfc-2822-compliant-possible-to-bypass My question is can Mailman strip out the duplicate From: headers leaving the first one? I have searched for a Postfix solution with no luck. I guess I could work up a procmail solution for all inbound mail but really didn't want to add that layer of complexity if it could be handled by Postfix or Mailman. Thanks, Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mail going out to only 1 member
On Wed, Oct 17, 2012 at 11:48 AM, Mark Sapiro wrote: > Dave Jones wrote: > > >I have a list named "supt" with 252 members that received an email that > >only went out to 1 recipient. > [...] > >Postfix maillog > >=== > >Oct 10 10:36:12 lists postfix/qmgr[11957]: B1E055055B7: > >from=, size=95926, nrcpt=1 > (queue > >active) > >Oct 10 10:36:12 lists postfix/local[14994]: B1E055055B7: to=< > >s...@lists.mydomain.com>, relay=local, delay=0.13, delays=0.02/0/0/0.12, > >dsn=2.0.0, status=sent (delivered to command: > /usr/lib/mailman/mail/mailman > >post supt) > > > >Mailman smtp log > > > >Oct 10 10:36:15 2012 (15296) < > >mailman.550.1349883373.15294.s...@lists.mydomain.com> smtp to supt for 1 > >recips, completed in 0.022 seconds > > > ># list_members supt | wc -l > >252 > > > What does > > list_members -r -n enabled supt | wc -l > > show? If it shows more than 1, is there anything in the list's > Non-digest options -> regular_exclude_lists? > > It could be the case that in the above logs, the post was held, > discarded or rejected and the one smtp message was a notification. > What's in Mailman's vette log for this time? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > > # list_members -r -n enabled supt | wc -l 252 The regular_exclude_lists field is blank. The vette log has nothing at this time period. It skips from Oct 10 10:26:50 to 10:42.20. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mail going out to only 1 member
I have a list named "supt" with 252 members that received an email that only went out to 1 recipient. After looking at the mailman smtp logs, I am seeing a number of lists that are only sending to a single recipient but have dozens to hundreds of members. Nothing is showing up in the "post" log for these problem lists. How do I troubleshoot this deeper? I still have many lists that seem to be working properly and actually have entries in the post log. Postfix maillog === Oct 10 10:36:12 lists postfix/qmgr[11957]: B1E055055B7: from=, size=95926, nrcpt=1 (queue active) Oct 10 10:36:12 lists postfix/local[14994]: B1E055055B7: to=< s...@lists.mydomain.com>, relay=local, delay=0.13, delays=0.02/0/0/0.12, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post supt) Mailman smtp log Oct 10 10:36:15 2012 (15296) < mailman.550.1349883373.15294.s...@lists.mydomain.com> smtp to supt for 1 recips, completed in 0.022 seconds # list_members supt | wc -l 252 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] clone_member hangs
I am having the same problem as this thread: http://mail.python.org/pipermail/mailman-users/2008-April/061087.html I have run the 'ls -U' command and know the problem list but I am not able to find any mailman lock files on my server and the above link does not mention the location of the lock files (or at least a link that might is broken). I am running CentOS 5.6 and the problem didn't exist a couple of months ago when I was on CentOS 5.5 and a previous version of mailman. The list it's hanging on was created a few days ago so unfortunately multiple things have changed to complicate the troubleshooting of the root cause. # rpm -q mailman mailman-2.1.9-6.el5_6.1 Thanks, Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
