Svend Sorensen wrote: > >I see. Mailman still lists the *-admin aliases when creating a list, >so this behavior is somewhat confusing. If *-admin is depreciated, >can all the *-admin aliases be removed?
See the Note in the details for the admin->Bounce processing->bounce_unrecognized_goes_to_list_owner Option for why this alias is still created. The question is why are users mailing this address (or are they)? If you have pre 2.1 users who are mailing to that address because they think it reaches a human, you can leave things as they are and be sure bounce_unrecognized_goes_to_list_owner is set to Yes, and these messages will reach the list owner, albeit indirectly. Alternatively, you can change the alias to something like LIST-admin: "|path_to/mail/mailman owner LIST to send such messages mail directly to the owner(s). If you're not concerned about receiving mail sent to this address, you can safely delete the alias. Nothing in mailman itself other than creation of the alias for historical reasons refers to the LIST-admin address. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
