D G Teed wrote: > >Unless postfix has a bug where some emails are not being logged, there seems >to be a problem with mailman. I'm not looking for delivery - just any >reference >to the expected attempts to deliver.
This is in the log message in Mailman's smtp log. E.g., something like May 01 22:43:36 2007 (1570) <[EMAIL PROTECTED]> smtp for 198 recips, completed in 1.390 seconds In this case, Mailman attempted delivery to the MTA for Message-Id: <[EMAIL PROTECTED]> for 198 recipients. >I do however see an error in /var/log/mailman which matches the time of >this mass mailing: > >Apr 30 15:43:40 2007 (1877) Uncaught runner exception: No terminating >boundary and no trailing empty line >Apr 30 15:43:40 2007 (1877) Traceback (most recent call last): > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop > msg, msgdata = self._switchboard.dequeue(filebase) > File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 151, in dequeue > msg = email.message_from_string(msg, Message.Message) > File "/usr/lib/mailman/pythonlib/email/__init__.py", line 52, in >message_from_string > return Parser(_class, strict=strict).parsestr(s) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 75, in parsestr > return self.parse(StringIO(text), headersonly=headersonly) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 64, in parse > self._parsebody(root, fp, firstbodyline) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 240, in _parsebody > msgobj = self.parsestr(part) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 75, in parsestr > return self.parse(StringIO(text), headersonly=headersonly) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 64, in parse > self._parsebody(root, fp, firstbodyline) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 265, in _parsebody > msg = self.parse(fp) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 64, in parse > self._parsebody(root, fp, firstbodyline) > File "/usr/lib/mailman/pythonlib/email/Parser.py", line 206, in _parsebody > raise Errors.BoundaryError( >BoundaryError: No terminating boundary and no trailing empty line > >Apr 30 15:43:40 2007 (1877) Ignoring unparseable message: >1177958619.246433+b72521b62f4a6aa7dc74c339613c4ef7e9c3eba7 This has nothing to do with delivery. This is an incoming message, almost certainly spam, with defective MIME structure that was discarded in its entirety. >The mailman smtp log does not >show >the entry for the 1800 something messages which were delivered OK. Are you using SMTPDirect? Do you have any overrides in mm_cfg.py for DELIVERY_MODULE, SMTP_LOG_EVERY_MESSAGE or SMTP_LOG_EACH_FAILURE. Are there any log messages in 'smtp' (similar to my example above)? >My hunch, is that there is some bad data in our mailing list subscription >which wasn't caught anywhere and has created this issue. We are given >data from the Alumni Affairs department to inject into the mailing list. >It may contain odd things. I've seen a '#' and single quote appear in >the mail subscriptions. This could be true. Try bin/list_members -i <listname> and/or bin/list_members <listname> | grep '[EMAIL PROTECTED]' to narrow down the opportunities. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
