* Mark Sapiro <[email protected]> wrote: > Stefan Förster wrote: >> generated by [email protected] >> mailbox is full: retry timeout exceeded >> >> Is there any way to rewrite those addresses or to help Mailman >> identify those bounces correctly? >> >> And yes, this a pretty stupid thing to do on their ISPs part... > > > Mailman has a whole host of heuristic recognizers for non-compliant DSNs, > but it doesn't try to guess if a non-member bouncing address might be a > munged version of a member address.
Because it's a pretty stupid thing to do - at least the fact that addresses are not rewritten twice. > The 'best' solution for recognizing original recipients of bounced > messages is Mailman's VERP like capability. This puts the original > recipient's address in the envelope sender address so the envelope in this > case is from [email protected]. > When the bounce is returned to that address, the MTA delivers it to the > list-bounces address and Mailman recognizes the original recipient as > [email protected] from the envelope recipient of the DSN. > > The cost of this approach is that Mailman has to send an individual > message to the outgoing MTA for each recipient. Bummer. There is no way to implement that, our mailing list server is already suffering from too much traffic, it's quite old hardware, after all. Thanks anyways Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #283: whoami - Whoami ist nur was für Leute mit Alzheimer! (Begründung von Microsoft Deutschland für das Entfernen des Befehls aus Windows NT) ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
