Mailman 3 December 2003 - Mailman-Developers

(no subject)
by Somuchfun Dec. 13, 2003

Dec. 13, 2003

Hello, Is there a way to restrict mailman lists to a certain amount of users? What I am missing is a way to restrict each list to a maximum amount of members on a site basis. Any ideas? Thanks!

2 1

next version of Mailman
by Len Jacobs Dec. 13, 2003

Dec. 13, 2003

Is there any definite schedule for the delivery of the 2.1.4 version of Mailman? Another December upgrade possible?

2 1

Mailman Integration
by Ben Hall Dec. 13, 2003

Dec. 13, 2003

Hi all, We've got some scripts adding a couple of features for our local installation of Mailman (v2.1.2). The scripts are using Mailman modules and classes (mostly MailList) directly as opposed to just calling mailman/bin scripts. I'm wondering how much might we expect the interfaces of these classes to change between releases of Mailman. Or more generally, how 'supported' is this means of integrating with Mailman? Thanks, Ben Hall

2 1

Moderation flag change via script
by Greg Harris Dec. 13, 2003

Dec. 13, 2003

Hello all, I am writing this to the devel group since the general list said it was not highly technical. I am currently running mailman-2.1.2 from a RedHat 7.3 RPM, on RedHat 7.3 with Postfix 2.1. I am creating scripts to automatically create umbrella lists from other lists using sync_members. However, I need a way to unset the moderation flag for users for some imported lists, and leave it at moderated for other lists. The problem I am having, is that I see no way to change the moderation flag of a user from the command line on a particular list. I don't really care if I need to run a separate script after the sync_members or not, just that I am able to set the flag from some sort of script. Thanks, Greg Harris --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.547 / Virus Database: 340 - Release Date: 12/2/2003

2 1

Mailman Virtualhosting
by Sung Kim Dec. 12, 2003

Dec. 12, 2003

Hi, I figured that the list name should be unique across the entire site, even though the site has hundreds of virtual domains: The primary problem with all this is that list names must be unique across the entire site. For example, say you run mysite1.com and mysite2.com and these are virtually hosted. You cannot have two lists, called mylist(a)mysite1.com and mylist(a)mysite2.com. The only choice you have is to run two completely separate Mailman installations, each hosting just one of those domains. This sucks for ISPs? hosting tens or hundreds (or more!) virtual domains. (http://zope.org/Members/bwarsaw/MailmanDesignNotes/VirtualHosting) If this is true, do we have a plan to develop the *real* virtual hosting function in Mailman: mylist(a)mysite1.com mylist(a)mysite2.com while mysite1 and mysite2 are actually the same machine. -- Sung Kim

1 0

Improvements MM 2.1.3
by Rodolfo Pilas Dec. 9, 2003

Dec. 9, 2003

I have just installed Mailman 2.1.3 and see the following problems: 1) Explanation with the refuse message. When a moderator refuse a message and write an explanation to the sender all works ok. However if the moderator send a copy of the message to all moderators, the others do not receive the explanation, they receive the message only. Perhaps the same message sent to sender (with the explanation) would have to be sent to the moderators team. 2) Name and addres at subscriber list view The subscriber list view list addresses only. It would be very usefull to list the address followed by the NAME of each subscriber. Of course, MM is the best mailserver. You have made an excellent work! -- Rodolfo Pilas Quien los puso a estos tipos donde estan, rodolfo(a)pilas.net Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, Yahoo ID: ysidorito Quien les paga para que hagan lo que haran ICQ: 17461636 -=# Apocalipsis Now % Cuarteto de Nos #=- GnuPG Public Key: gpg --keyserver www.keyserver.net --recv-key 57153363 Key Fingerprint => DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363

1 0

RE: Moderation flag change via script
by Greg Harris Dec. 5, 2003

Dec. 5, 2003

Google strikes again. I was searching for the wrong key words. Once I found the correct syntax, I found a script to do exactly what I wanted. Using the search text of "withlist moderate", I found this link: http://mail.python.org/pipermail/mailman-developers/2002-February/010563.htm l with a script for setting mod flags inside. Thanks to Dan Mick for this post. Thanks, Greg Harris -----Original Message----- From: Greg Harris [mailto:gharris@mail.nixa.k12.mo.us] Sent: Friday, December 05, 2003 12:05 PM To: 'mailman-developers(a)python.org' Subject: Moderation flag change via script Hello all, I am writing this to the devel group since the general list said it was not highly technical. I am currently running mailman-2.1.2 from a RedHat 7.3 RPM, on RedHat 7.3 with Postfix 2.1. I am creating scripts to automatically create umbrella lists from other lists using sync_members. However, I need a way to unset the moderation flag for users for some imported lists, and leave it at moderated for other lists. The problem I am having, is that I see no way to change the moderation flag of a user from the command line on a particular list. I don't really care if I need to run a separate script after the sync_members or not, just that I am able to set the flag from some sort of script. Thanks, Greg Harris --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.547 / Virus Database: 340 - Release Date: 12/2/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.547 / Virus Database: 340 - Release Date: 12/2/2003

1 0

Mailman Preprocessor Available - seeking feedback
by darwin＠desktopengineer.com Dec. 5, 2003

Dec. 5, 2003

Hello, Below is the description of a preprocessor script I wrote for mailman. I was looking to emulate the Topica.com features of "<list>-subscribe", "<list>-unsubscribe" and "<list>-post-<password>" in an efficient and extensible manner. I am seeking feedback on the script and I have two areas that are troubling right now: *) I still get a succesful completion AND an error message back from mailman when sending to "<list>-unsubscribe" (yet I don't get one when sending to "<list>-unsubscribe" which *should* process exactly the same way. I know I coiuld re-write the entire message - but I am wondering if there is a way to make unsubscribe work the same way as subscribe and post - by doing replacements to the inbound message. *) I am wondering if there is a way to alter all the messages sent out by mailman to match my configuration. There are some in "Templates" - but others seem hardcoded. Right now I am tied to Mailman 2.0.13 due to needing to stay compliant with the RedHat 2.1AS distribution. The script can be found at http://desktopengineer.com/mmpreproc Thanks for any time anyone can take to send feedback, D. # This script pre-processes mail commands to mailman to faciliate announcement lists and easy subscribe and unsubscribe. # It modifies the list behavior as follows: # *) unsubscribes only made through the alias <list>-subscribe(a)domain.com and automatically sets users password to their email # *) unsubscribes only made through the alias <list>-unsubscribe(a)domain.com and automatically unsubscribes with no confirm, email=password is assumed # *) posting to the list can only be done through a special alias that includes a password component such as <list>-post-<password>@domain.com. # The list can be configured for moderation and only allow a specific list of emails to be automatically approved. Since it is recommended # that you delete the <list>@domain.com alias, using this method prevents the need to moderate messages that try to use the standard posting # alias - even if you do not allow auto approval of posts to specific email addresses. # *) This script accomplishes its objectives by having the mail message piped to it and then it pipes the message into the standard mailman wrapper for # processing. This is more efficient than re-mailing back to the same system. In addition, since the program simply does regex substitutions to # inbound message headers, the posting password alias can work easily with complex messages that include mime sections because the entire message does not # need to pass through mail again and therefore be disassembled, reassembled and then emailed correctly. # *) Many other modifications could be made for preprocessing mailman commands and posts - the script design is modular and dynamic - it pulls apart the # mail aliases components (seperate by "-" character) and decides what to do with the message based on these components. # Install # *) Tested with mailman 2.0.13 (Redhat 2.1AS Version) # *) Ensure you have Mail:Mailer (mailtools) installed if you wish to have error notification or debug emails sent, or rewrite the email section # to suite your system. # *) Copy mmprepoc.pl to <mailmanroot>/mail (e.g. "cp mmpreproc.pl /path/to/mailman/mail") # *) Change ownership to the mailman user (e.g. "chown mailman mmpreproc.pl") # *) Change security to be executable (e.g. "chmod 755 mmpreproc.pl") # *) For sendmail create a link in the /etc/smrsh directory (e.g. "ln -s /path/to/mailman/mail/mmpreproc.pl") # *) Set $mailmanpath - this should be the directory with all your mailman subdirectories (including "bin") in it. # *) Set $blockrequests - if set to "1" this script blocks all <list>-request(a)domain.com messages except replys to # subscription confirmations. # *) Set $emaildiscards, $emailerrors, $emaildebug and $emailnotifyaddress if you wish to use email notification. # Configure Mailman (note your lists cannot have a "-" character in their name): # *) add the list alias <listname>-subscribe: "|/path/to/mailman/mail/mmpreproc.pl" # *) add the list alias <listname>-unsubscribe: "|/path/to/mailman/mail/mmpreproc.pl" # Configure Mailman: If using the post-password alias feature # *) add the list alias <listname>-post-<password>: "|/path/to/mailman/mail/subprocessor" # *) remove the list alias <list> or send it to null so that you don't have to moderate messages sent there. # *) in mail man set posting to the list to be only allowed from members of the list and setup any auto-approval email # addresses. It won't matter that users can see your auto approved email when receiving messages because they cannot # tell that you used a special alias to send the message rather than <list>@domain.com

3 4

Possible Web interface bug.
by Chris Johnson Dec. 3, 2003

Dec. 3, 2003

Hi, Sorry to bother the list with this. I'm on mailman-users but my posts are mysteriously vanishing into the entropic ether. I'm running RH7.3, Mailman 2.1-8. I've looked at the bug list but haven't found anything like this. Posts are held for various reasons, in my case size issues, too big. I go to the Web interface at http://host/mailman/admindb/listname for any list. None of the actions, i.e. Defer, Accept, Reject or Discard, seem to work. There are no errors given. When I Submit All the same status page comes back in its original form. The held message is still there and never has any action applied as far as I can tell. Are there any bugs relating to this? If not can any body tell me what I'm doing wrong? Help would be greatly appreciated as there is a increasing held backlog I can't free up. Thank you. ------------------------------------------------------------------------------- Chris Johnson |Internet: johnson(a)nmr.mgh.harvard.edu Systems Administrator |Web: http://www.nmr.mgh.harvard.edu/~johnson NMR Center |Voice: 617.726.0949 Mass. General Hospital |FAX: 617.726.7422 149 (2301) 13th Street |"Life is chaos. Chaos is life. Control is an Charlestown, MA., 02129 USA | illusion." Trance Gemini -------------------------------------------------------------------------------

1 0

Mailman Preprocessor Available - seeking feedback
by Darwin Sanoy Dec. 1, 2003

Dec. 1, 2003

Hello, Below is the description of a preprocessor script I wrote for mailman. I was looking to emulate the Topica.com features of "<list>-subscribe", "<list>-unsubscribe" and "<list>-post-<password>" in an efficient and extensible manner. I am seeking feedback on the script and I have two areas that are troubling right now: *) I still get a succesful completion AND an error message back from mailman when sending to "<list>-unsubscribe" (yet I don't get one when sending to "<list>-unsubscribe" which *should* process exactly the same way. I know I coiuld re-write the entire message - but I am wondering if there is a way to make unsubscribe work the same way as subscribe and post - by doing replacements to the inbound message. *) I am wondering if there is a way to alter all the messages sent out by mailman to match my configuration. There are some in "Templates" - but others seem hardcoded. Right now I am tied to Mailman 2.0.13 due to needing to stay compliant with the RedHat 2.1AS distribution. The script can be found at http://desktopengineer.com/mmpreproc Thanks for any time anyone can take to send feedback, D. # This script pre-processes mail commands to mailman to faciliate announcement lists and easy subscribe and unsubscribe. # It modifies the list behavior as follows: # *) unsubscribes only made through the alias <list>-subscribe(a)domain.com and automatically sets users password to their email # *) unsubscribes only made through the alias <list>-unsubscribe(a)domain.com and automatically unsubscribes with no confirm, email=password is assumed # *) posting to the list can only be done through a special alias that includes a password component such as <list>-post-<password>@domain.com. # The list can be configured for moderation and only allow a specific list of emails to be automatically approved. Since it is recommended # that you delete the <list>@domain.com alias, using this method prevents the need to moderate messages that try to use the standard posting # alias - even if you do not allow auto approval of posts to specific email addresses. # *) This script accomplishes its objectives by having the mail message piped to it and then it pipes the message into the standard mailman wrapper for # processing. This is more efficient than re-mailing back to the same system. In addition, since the program simply does regex substitutions to # inbound message headers, the posting password alias can work easily with complex messages that include mime sections because the entire message does not # need to pass through mail again and therefore be disassembled, reassembled and then emailed correctly. # *) Many other modifications could be made for preprocessing mailman commands and posts - the script design is modular and dynamic - it pulls apart the # mail aliases components (seperate by "-" character) and decides what to do with the message based on these components. # Install # *) Tested with mailman 2.0.13 (Redhat 2.1AS Version) # *) Ensure you have Mail:Mailer (mailtools) installed if you wish to have error notification or debug emails sent, or rewrite the email section # to suite your system. # *) Copy mmprepoc.pl to <mailmanroot>/mail (e.g. "cp mmpreproc.pl /path/to/mailman/mail") # *) Change ownership to the mailman user (e.g. "chown mailman mmpreproc.pl") # *) Change security to be executable (e.g. "chmod 755 mmpreproc.pl") # *) For sendmail create a link in the /etc/smrsh directory (e.g. "ln -s /path/to/mailman/mail/mmpreproc.pl") # *) Set $mailmanpath - this should be the directory with all your mailman subdirectories (including "bin") in it. # *) Set $blockrequests - if set to "1" this script blocks all <list>-request(a)domain.com messages except replys to # subscription confirmations. # *) Set $emaildiscards, $emailerrors, $emaildebug and $emailnotifyaddress if you wish to use email notification. # Configure Mailman (note your lists cannot have a "-" character in their name): # *) add the list alias <listname>-subscribe: "|/path/to/mailman/mail/mmpreproc.pl" # *) add the list alias <listname>-unsubscribe: "|/path/to/mailman/mail/mmpreproc.pl" # Configure Mailman: If using the post-password alias feature # *) add the list alias <listname>-post-<password>: "|/path/to/mailman/mail/subprocessor" # *) remove the list alias <list> or send it to null so that you don't have to moderate messages sent there. # *) in mail man set posting to the list to be only allowed from members of the list and setup any auto-approval email # addresses. It won't matter that users can see your auto approved email when receiving messages because they cannot # tell that you used a special alias to send the message rather than <list>@domain.com

1 0