Ivan Sanders wrote: > >I'm a new Mailman admin, with 11 lists to look after. The area I want to >tie down is bounce processing. What I'm looking for, is for every message >which doesn't make it to it's destination (ie mailbox full) for an advice >message to come back to the administrator (which means I need Bounce >Processing to be turned on), but for the user to NOT be marked inactive..
These are conflicting goals for Mailman bounce processing. Mailman only forwards the DSN to the admin when it is the DSN that triggers a disable and bounce_notify_owner_on_disable is Yes. If you want to see every DSN, whether or not it triggers a disable, you have to set aliases or whatever in your MTA so that messages to the [EMAIL PROTECTED] address get delivered to 'owner' either in addition to or instead of 'bounces'. -- 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://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
