[Mailman-Users] Error Creating List - additional info

Jeff Bernier jbernier at risd.edu
Mon Mar 23 18:02:48 CET 2009


Thank you Mark for your help explaining this. Great stuff!
 
Jeff

>>> Mark Sapiro <mark at msapiro.net> 3/23/2009 12:48 PM >>>
Jeff,

I see the problem. you have two lists named "dm" and "dm-admin", but
LISTNAME-admin is one of the aliases created for every LISTNAME.

Thus, you get

dm-admin:       "|/usr/share/mailman/mail/mailman admin dm"

as the -admin address for the "dm" list and you get

dm-admin:             "|/usr/share/mailman/mail/mailman post dm-admin"

as the posting address for the "dm-admin" list and these are duplicate
aliases.

As long as the aliases are in the order that they are, there is no
problem (except for the postfix warning) because the second replaces
the first and dm-admin works to post to the dm-admin list and there
should never be any mail to the -admin address of the "dm" list anyway
as that is a deprecated address.

If you had a list named "dm-bounces" or "dm-confirm" or "dm-request" or
"dm-owner", etc. that would be a problem.

In general, you should avoid list names that end in -admin, -bounces,
-confirm, -join, -leave, -owner, -request, -subscribe and -unsubscribe
for this reason.

To be safe in this case, you could remove the line

dm-admin:       "|/usr/share/mailman/mail/mailman admin dm"

from the "dm" list aliases. That will get ride of the warning and will
ensure that the alias that's effective will be the "dm-admin" posting
address, but if you ever run bin/genaliases, it will come back.

In the future, consider naming a list like this xx-admins to avoid this
kind of conflict.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan



More information about the Mailman-Users mailing list