Barry Finkel wrote: >I have a Mailman 2.1.9 Uncaught bounce notification: > > From: <> > To: [EMAIL PROTECTED] > Subject: Returned mail: unreachable recipients:[EMAIL PROTECTED] > > The original message was received at Thu Nov 8 14:58:21 2007 > > Likely reason for failure: 550 5.1.1 <[EMAIL PROTECTED]>... User unknown > >Why was this not caught as a standard 550 rejection? Is it because the >initial mail received a 250 return code
No. It is because the DSN is not an RFC 1894/RFC 3464 compliant DSN and it is not one of the many non-compliant formats that Mailman 2.1.9 recognizes. I am right now in the process of trying to wrap up the 2.1.10 beta release and the last thing on my list is adding recognition for more non-standard DSNs (I have a collection). Please send me off list the complete DSN from the uncaught bounce notification, and I'll try to get it in the set that 2.1.10 recognizes. BTW, I realize that it is trivial for a human to look at one of these (at least the ones that are in a language the human reads - they aren't all in English) and determine that it is a notice of a permanent failure and what the failed address is, but there are still things (such as recognizing DSNs and spam) that humans are much better than software at doing. -- 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
