Re: [Mailman-Developers] Postfix.py extension for virtual_domain management
Hi Mike,
I've also wished mailman handled Virtual lists better. PostfixVirtual.py Works great, and I also tried removeing the name change restriction in General.py:
vi /usr/lib/mailman/Mailman/Gui/General.py /real_name # Lets try this just for fun... if property == 'real_name_NOT' and \
I did some quick testing and found most of the obvious references to com.foo.test became test without any problems. Though the URLs and some other text still refers to it by the "correct" name.
Anyway you mentioned in your post that you had customized mailman in other ways. Do you feel like publishing them as well?
Thanks,
Clif
hi clif,
[clif's posting is refereing to
http://mail.python.org/pipermail/mailman-developers/2005-January/017673.html
]
I've also wished mailman handled Virtual lists better. PostfixVirtual.py Works great, and I also tried removeing the
that is indeed good to hear. however, i do not like the idea of customized bits of extra-code here and there, as new versions of mailman might handle things differently in the future. this would mean that admins on mailman-customized sites had to adapt the scripts whenever a major change has occured in the mailman source code tree. and mostly you only realize the major change in code by some sort of list failure. this is not acceptable on productive sites. what i would like to fancy, is that the PostfixVirtual.py code would be perceived by the Postfix-coders on this list... and PostfixVirtual.py is just a suggestion how virtual lists could be handled...
name change restriction in General.py:
vi /usr/lib/mailman/Mailman/Gui/General.py /real_name # Lets try this just for fun... if property == 'real_name_NOT' and
I did some quick testing and found most of the obvious references to com.foo.test became test without any problems. Though the URLs and some other text still refers to it by the "correct" name.
i do not think that a very good idea, unless you make sure, that all locations, the listname is used at also gets updated (filenames, directories, archives, URLs for the WWW-interface, etc.). furthermore, if renaming was posssible, there should also be a garantuee, that there is no other list on the site, bearing the same name as the one the list is to be renamed to.
i do think that there is a proper reason, why list renaming is (so far) prohibited.
however, list renaming would be a very fine feature!!!
Anyway you mentioned in your post that you had customized mailman in other ways. Do you feel like publishing them as well?
i have studied my former posting very thoroughly, but cannot guess what you are pointing at...
have a good time, mike
-- network administration, ecology centre, kiel university, germany Mike Gabriel, olshausenstr 75, 24118 kiel, germany
fon-work: +49 431 880-1186 fon-home: +49 431 6474196 mail: mgabriel@ecology.uni-kiel.de www: http://www.ecology.uni-kiel.de, http://zope.ecology.uni-kiel.de
Hi Mike,
I was refering to what you said here:
"...it in my very own special mailman setup." Maybe I missunderstood but it sounded like "special" here implied non-typical customizations. No?
Yes good points, I think thats why we're here, to talk about the possibility of better virtual list support in mailman, hopefully to avoid the pitfalls you mention.
Have fun,
ClifOn Sun, 6 Mar 2005, Mike Gabriel wrote:
hi clif,
[clif's posting is refereing to
http://mail.python.org/pipermail/mailman-developers/2005-January/017673.html
]
I've also wished mailman handled Virtual lists better. PostfixVirtual.py Works great, and I also tried removeing the
that is indeed good to hear. however, i do not like the idea of customized bits of extra-code here and there, as new versions of mailman might handle things differently in the future. this would mean that admins on mailman-customized sites had to adapt the scripts whenever a major change has occured in the mailman source code tree. and mostly you only realize the major change in code by some sort of list failure. this is not acceptable on productive sites. what i would like to fancy, is that the PostfixVirtual.py code would be perceived by the Postfix-coders on this list... and PostfixVirtual.py is just a suggestion how virtual lists could be handled...
name change restriction in General.py:
vi /usr/lib/mailman/Mailman/Gui/General.py /real_name # Lets try this just for fun... if property == 'real_name_NOT' and
I did some quick testing and found most of the obvious references to com.foo.test became test without any problems. Though the URLs and some other text still refers to it by the "correct" name.i do not think that a very good idea, unless you make sure, that all locations, the listname is used at also gets updated (filenames, directories, archives, URLs for the WWW-interface, etc.). furthermore, if renaming was posssible, there should also be a garantuee, that there is no other list on the site, bearing the same name as the one the list is to be renamed to.
i do think that there is a proper reason, why list renaming is (so far) prohibited.
however, list renaming would be a very fine feature!!!
Anyway you mentioned in your post that you had customized mailman in other ways. Do you feel like publishing them as well?
i have studied my former posting very thoroughly, but cannot guess what you are pointing at...
have a good time, mike
-- network administration, ecology centre, kiel university, germany Mike Gabriel, olshausenstr 75, 24118 kiel, germany
fon-work: +49 431 880-1186 fon-home: +49 431 6474196 mail: mgabriel@ecology.uni-kiel.de www: http://www.ecology.uni-kiel.de, http://zope.ecology.uni-kiel.de
hi there,
with mailman 2.1.5 a change in the host_name field (changing the default virtual domain to the one the list should be addressable under) does not appear in the postfix'aliases files.
for now i have set up a CRON job, that runs bin/genaliases every hour, to make sure, host_name changes in the webfrontend appear (belatedly) in the aliases files...
is this behaviour intentional???
salut, mike
-- network administration, ecology centre, kiel university, germany Mike Gabriel, olshausenstr 75, 24118 kiel, germany
fon-work: +49 431 880-1186 fon-home: +49 431 6474196 mail: mgabriel@ecology.uni-kiel.de www: http://www.ecology.uni-kiel.de, http://zope.ecology.uni-kiel.de
participants (2)
-
clif -
Mike Gabriel