Here at work, we've found that mailman's "-request" alias has stomped
another already-existing function (under our previous list, we used that
for administrative requests, and on this particular list, that's not
negotiable -- it needs to duplicate the function of xxx-owner).
However, we're using automatic aliases. Is there some way to quell or
suppress the creation (or re-creation) of that particular alias (for one
list only), without having to go to manual aliases?
That is to say, if I hand-edited both $mailman/data/aliases and aliases.db
(by rebuilding it from the new aliases file) -- would mailman revert it on
me the next time I created a list?
-Dan Mahoney
--
"Let me tell you something about regrowing your dead wife Lucy, Harry.
It's probably illegal, potentially dangerous, and definitely crazy."
-Harry nods-
Vincent Spano, as Boris in "Creator".
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
------------------------------------------------------
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
