Re: [Mailman-Users] How to change list name

2005-09-03 Thread Zoran Dzelajlija
Mark Sapiro <[EMAIL PROTECTED]> wrote: [...] > The post at > http://mail.python.org/pipermail/mailman-users/2005-August/046316.html > gives more detail on how you might actually do this including > archives, but it does neglect to mention the aliases. Here's a checklist used here: ---

[Mailman-Users] Re: Getting Mailman to work

2005-03-19 Thread Zoran Dzelajlija
Mark Sapiro <[EMAIL PROTECTED]> wrote: > It looks to me like a Postfix configuration problem, i.e. Mailman is > sending the mail as it should and Postfix is not accepting it because > it doesn't like the sender <[EMAIL PROTECTED]>. Shouldn't that be <[EMAIL PROTECTED]> (as per rfc2821, 4.1.3)? Zo

[Mailman-Users] Re: Uncaught runner exception: unknown encoding

2004-09-05 Thread Zoran Dzelajlija
David Relson <[EMAIL PROTECTED]> wrote: > Greetings, > FWIW, I've checked email/Charsets.py and it does have a gb2312 entry If you look carefully, you can see there's a typo in that file, line 109, where it says "gb2132" not "gb2312". If you fix that, you then get Uncaught runner exception: unk

[Mailman-Users] Turning off options in GUI [Re: Announce Only]

2004-05-04 Thread Zoran Dzelajlija
Paul Reilly <[EMAIL PROTECTED]> wrote: > If the feature doesn't work for me via the > web, then I'd like the option of turning it off. This idea could be expanded to an novice/advanced view of the options, where the advanced would show all of the options and categories and the novice view would sh

[Mailman-Users] Re: Add ability for admin to change email addresses inside List database

2004-03-26 Thread Zoran Dzelajlija
Jon Carnes <[EMAIL PROTECTED]> wrote: > It almost trivial to write a command line tool that would change an > email address inside the list database. I apologize for replying to an old thread, but it seems to me that your trivial tool already exists: ;-) clone_member -l list -r old-address new-a

[Mailman-Users] Upgrade heldmsgs?

2004-01-09 Thread Zoran Dzelajlija
Hello! I want to transfer some (not all!) lists from an existing 2.0.13 installation to the latest 2.1. I'm currently having both 2.0 and 2.1 installed, and am trying to transparently migrate lists to 2.1. Most of the stuff is covered in UPGRADE, but I have some unresolved issues. Some of our c