[Mailman-Developers] a stupid but useful backup script for Mailman
Hello, every day at 11:00 I run this script on my Mailman lists, and receive a nicely formatted email showing who un/subscribed to what list, what did the list owners do (or try to do), and so on. And of course it stores gzipped copies of the list of subscribers and of the configurations in my /var/state/mailman/ folder. I've updated it a bit since I wrote it (version 0.13 was dated year 2000). Here's version 0.14 if it can be of any interest to anyone. It's quick and dirty, but I've been using it for more than two years without a glitch. -- Fil mailman_save_lists.sh Description: Bourne shell script ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Create mailing list on the web error
On Tuesday, January 14, 2003, at 03:49 PM, Bryan Fullerton wrote: Unfortunately, for some reason bin/check_perms doesn't check permissions on the aliases* files in the data directory - this should be fixed (I'll look at a patch in a bit). Just looking at this, there's a comment in checkperms() in Mailman/MTA/Postfix.py as follows: # Make sure the corresponding .db files are owned by the Mailman user. # We don't need to check the group ownership of the file, since # check_perms checks this itself. Was this from an earlier version of 2.1 which checked permissions on */*.db? I don't see anything in check_perms which checks group permissions of data/aliases.db. Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS
Howdy, Nobody seems to be answering questions in mailman-users (is Barry away?), so I'll try this one here. There's a setting in Defaults.py which seems to be just what my customers are looking for to limit the headers being shown in their plain digests - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS. However, this setting appears nowhere in the actual Mailman code except Defaults.py. Was it supposed to be included somewhere? They're rather unhappy that their plain digests are showing things like Precedence and various MIME headers for each message. Thanks, Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS
> "BF" == Bryan Fullerton <[EMAIL PROTECTED]> writes: BF> Nobody seems to be answering questions in mailman-users (is BF> Barry away?), so I'll try this one here. I've been swamped with Zope work, a upcoming studio project, and getting ready for the Spam conference. Trust me, I'm taking all these messages with me on my laptop. 6:30 hours each way on the train should give me plenty of time to catch up. :) BTW, if anybody else is going to be at the Spam conference, let me know. I'd love to have a chat about Mailman, spam and other stuffis. I'll be getting in Thursday night. -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS
On Tuesday, January 14, 2003, at 04:25 PM, Barry A. Warsaw wrote: I've been swamped with Zope work, a upcoming studio project, and getting ready for the Spam conference. Trust me, I'm taking all these messages with me on my laptop. 6:30 hours each way on the train should give me plenty of time to catch up. :) Excellent, I'll keep sending mail and filing bug reports. ;) Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Create mailing list on the web error
On Monday, January 13, 2003, at 05:32 PM, Kory Wheatley wrote: I received the below error when I tried to create a mailing list from the Mailman web interface page. It did add the list into the alias file, but it failed to run "postalias" probably because of permission issue's I'm guessing. I have my alias file in /var/mailman/mailman/data/aliases and the permissions are rw-rw mailman mailman aliases. Unfortunately, for some reason bin/check_perms doesn't check permissions on the aliases* files in the data directory - this should be fixed (I'll look at a patch in a bit). I suspect that the problem is similar to one I had - your aliases.db file is probably not group writable (or isn't owned by the mailman group). Because all the web scripts run setgid as the mailman group, all files accessed by the web need to be group writable as that group. Here are the permissions on mine (which I just tested): -rw-rw 1 root mailman 33256 Jan 14 15:44 aliases -rw-rw-r-- 1 mailman mailman 57344 Jan 14 15:44 aliases.db Thanks, Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS
On Tuesday 14 January 2003 4:25 pm, Barry A. Warsaw wrote: > > "BF" == Bryan Fullerton <[EMAIL PROTECTED]> writes: > > BF> Nobody seems to be answering questions in mailman-users (is > BF> Barry away?), so I'll try this one here. > > I've been swamped with Zope work, a upcoming studio project, and > getting ready for the Spam conference. Trust me, I'm taking all these > messages with me on my laptop. 6:30 hours each way on the train > should give me plenty of time to catch up. :) > > BTW, if anybody else is going to be at the Spam conference, let me > know. I'd love to have a chat about Mailman, spam and other stuffis. > I'll be getting in Thursday night. I'd love to see mailman get some spam recognition and some thresholds that we can set to deliberately get rid of the most obvious stuff. ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler
Patches item #645513, was opened at 2002-11-28 18:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 -- Comment By: Ed Lau (edlau) Date: 2003-01-14 19:26 Message: Logged In: YES user_id=675094 Everything works as documented for me right now. Might also need to include a step to make ~alias/.qmail--bounce-default. -- Comment By: Colin Palmer (tzs) Date: 2003-01-08 12:09 Message: Logged In: YES user_id=658762 Yes, python throws an exception if they (or any other config options) are undefined. Set them to 'None' if you don't want logging to happen. -- Comment By: Ed Lau (edlau) Date: 2003-01-08 01:49 Message: Logged In: YES user_id=675094 using the version released 2003-01-07 17:27, with DO_QMAIL_VERP = 0, any post to a list gets posted to all members properly, but also gets shunted. This happened because I didn't have QMAIL_LOG_EVERY_MESSAGE, QMAIL_LOG_SUCCESS, or QMAIL_LOG_FAILURE defined. Is the Email shunted, yet posted event supposed to happen? I'll be testing out VERP later on -- Comment By: Colin Palmer (tzs) Date: 2003-01-07 12:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. -- Comment By: Ed Lau (edlau) Date: 2002-12-24 16:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
