[Mailman-Users] Monthly Reminder Problem
I started this thread some time ago and got to the point where I was able to trace things to Postfix and ultimately found where the message was apparently sent to my ISP. May 5 06:34:41 dap002 postfix/smtpd[3674]: connect from dap002[127.0.0.1] May 5 06:34:41 dap002 postfix/smtpd[3674]: E904B2001: client=dap002[127.0.0.1] May 5 06:34:41 dap002 postfix/cleanup[3677]: E904B2001: message-id=mailman.0.1304591680.3673.mail...@bellsouth.net May 5 06:34:41 dap002 postfix/qmgr[2599]: E904B2001: from=mailman-boun...@bellsouth.net, size=1833, nrcpt=1 (queue active) May 5 06:34:41 dap002 postfix/smtpd[3674]: disconnect from dap002[127.0.0.1] May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 220 isp.att.net - Maillennium ESMTP/MULTIBOX frfwmhc04 #3 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: EHLO home.bellsouth.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-isp.att.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-7BIT May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-8BITMIME May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-DSN May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-HELP May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-NOOP May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-PIPELINING May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-SIZE 26214400 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-VERS V05.40c++ May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 XMVP 2 May 5 06:34:42 dap002 postfix/smtp[3678]: server features: 0x900f size 26214400 May 5 06:34:42 dap002 postfix/smtp[3678]: Using ESMTP PIPELINING, TCP send buffer size is 4096 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: MAIL FROM:mailman-boun...@bellsouth.net SIZE=1833 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: RCPT TO:d...@bellsouth.net ORCPT=rfc822;d...@bellsouth.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: DATA May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 354 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: . May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: QUIT May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok ; id=20110505103442H040014q56e May 5 06:34:42 dap002 postfix/smtp[3678]: E904B2001: to=d...@bellsouth.net, relay=mail.bellsouth.net[204.127.217.17]:25, delay=1, delays=0.05/0.06/0.61/0.3, dsn=2.0.0, status=sent (250 ok ; id=20110505103442H040014q56e) May 5 06:34:42 dap002 postfix/smtp[3678]: name_mask: resource May 5 06:34:42 dap002 postfix/smtp[3678]: name_mask: software May 5 06:34:42 dap002 postfix/qmgr[2599]: E904B2001: removed As you can see, it appears everything is working properly as far as Postfix is concerned. However, my ISP never delivers the email to the recipient. All other mail to/from my mailing lists work and are successfully delivered including welcome messages, etc. This means to me (unless someone can think of something else) that the reason my ISP is not delivering the mail is because it is finding something unique in this particular email that does not exist in all others. There is no bounced message from the ISP so it must be throwing it into the bit bucket for some reason and I am not getting even a hint as to what is wrong. Can someone think of what is unique about these messages from all the others mailman generates? I doubt it is anything in the body so it seems it has to be something in the headers. The only straw I can grasp is perhaps the from address. 'Mailman-bounces' does not exist but is that not the from address of all mailman generated messages? Thanks. signature.asc Description: OpenPGP digital signature -- 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] Monthly Reminder Problem
* Dennis Putnam d...@bellsouth.net: I started this thread some time ago and got to the point where I was able to trace things to Postfix and ultimately found where the message was apparently sent to my ISP. May 5 06:34:41 dap002 postfix/smtpd[3674]: connect from dap002[127.0.0.1] May 5 06:34:41 dap002 postfix/smtpd[3674]: E904B2001: client=dap002[127.0.0.1] May 5 06:34:41 dap002 postfix/cleanup[3677]: E904B2001: message-id=mailman.0.1304591680.3673.mail...@bellsouth.net May 5 06:34:41 dap002 postfix/qmgr[2599]: E904B2001: from=mailman-boun...@bellsouth.net, size=1833, nrcpt=1 (queue active) May 5 06:34:41 dap002 postfix/smtpd[3674]: disconnect from dap002[127.0.0.1] May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 220 isp.att.net - Maillennium ESMTP/MULTIBOX frfwmhc04 #3 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: EHLO home.bellsouth.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-isp.att.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-7BIT May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-8BITMIME May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-DSN May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-HELP May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-NOOP May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-PIPELINING May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-SIZE 26214400 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-VERS V05.40c++ May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 XMVP 2 May 5 06:34:42 dap002 postfix/smtp[3678]: server features: 0x900f size 26214400 May 5 06:34:42 dap002 postfix/smtp[3678]: Using ESMTP PIPELINING, TCP send buffer size is 4096 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: MAIL FROM:mailman-boun...@bellsouth.net SIZE=1833 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: RCPT TO:d...@bellsouth.net ORCPT=rfc822;d...@bellsouth.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: DATA May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 354 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: . May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: QUIT May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok ; id=20110505103442H040014q56e May 5 06:34:42 dap002 postfix/smtp[3678]: E904B2001: to=d...@bellsouth.net, relay=mail.bellsouth.net[204.127.217.17]:25, delay=1, delays=0.05/0.06/0.61/0.3, dsn=2.0.0, status=sent (250 ok ; id=20110505103442H040014q56e) May 5 06:34:42 dap002 postfix/smtp[3678]: name_mask: resource May 5 06:34:42 dap002 postfix/smtp[3678]: name_mask: software May 5 06:34:42 dap002 postfix/qmgr[2599]: E904B2001: removed As you can see, it appears everything is working properly as far as Postfix is concerned. Yes. However, my ISP never delivers the email to the recipient. Ask bellsouth support what happend with the mail id=20110505103442H040014q56e All other mail to/from my mailing lists work and are successfully delivered including welcome messages, etc. This means to me (unless someone can think of something else) that the reason my ISP is not delivering the mail is because it is finding something unique in this particular email that does not exist in all others. Yup. There is no bounced message from the ISP so it must be throwing it into the bit bucket Yup. for some reason and I am not getting even a hint as to what is wrong. Can someone think of what is unique about these messages from all the others mailman generates? No, but you can bcc: this mail to you and then use divide conquer to find out what makes them reject the mail. I doubt it is anything in the body so it seems it has to be something in the headers. So try sending the mail with headers only :) The only straw I can grasp is perhaps the from address. 'Mailman-bounces' does not exist but is that not the from address of all mailman generated messages? It depends -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
Re: [Mailman-Users] .py and .pyc files
On May 4, 2011, at 9:59, LuKreme krem...@kreme.com wrote: So, it looks like mm_cfg.py is the only .py that gets recompiled automatically, right? So how do I recompile SpamDetect.py after making my changes? With further reading into Python, it appears that one of Python's features Is that it automatically recompiles .py files to .pyc files when needed, as soon as it triggers an import of the file, so there is nothing I need to do after changing the source and restarting mailman, it will just work. Is that correct? -- 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] .py and .pyc files
LuKreme wrote: With further reading into Python, it appears that one of Python's features Is that it automatically recompiles .py files to .pyc files when needed, as soon as it triggers an import of the file, so there is nothing I need to do after changing the source and restarting mailman, it will just work. Is that correct? Yes and no. As I indicated in my prior reply at http://mail.python.org/pipermail/mailman-users/2011-May/071536.html, in your specific case the qrunners don't have permission to write the .pyc so it can't be updated. This is not a problem in that Python will always use the more recent .py, but there is innefficiency in that since the .pyc can't be written, the .py will have to be compiled each time it is imported. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
