Mailman 3 April 2002 - Mailman-Developers

Re: [Mailman-Developers] Silly mailman question
by J C Lawrence 06 Apr '02

06 Apr '02

On Fri, 5 Apr 2002 12:11:25 -0500 Jay R Ashworth <jra(a)baylink.com> wrote: > The problem is that they're already in a database (filePro for Unix on > SCO 5, on a machine behind a Linux 7.1 firewall), and they want to be > able to selectwhom to mail on an adhoc basis. Sounds like a job for 2.1 and the new membership roster abstraction model. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Re: [Mailman-Developers] Problem in 2.1b1's contrib/qmail-to-mailman.py
by Marc MERLIN 05 Apr '02

05 Apr '02

On Fri, Apr 05, 2002 at 11:50:35AM -0800, Bill Wagner wrote: > > Then again, it'd be better if qmail could just be taught to > > automatically recognize Mailman lists, but again, I don't know enough > > about qmail to write the appropriate recipes. > > Are there no developers running qmail? I know most run postfix, but I > figured that qmail's a large enough player that someone would be working > on it. I think one contributed factor is that at least some of us do not bear much love for DJB, his stupid license (or lack thereof) and his general thickheadedness. http://www.linuxmafia.com/~rick/faq/#djb if you're curious. Since you had postfix and exim, life is too short to have to bother with qmail or DJB software if there are reasonable alternatives out there IMO If you're going to flame me, do it in private please :-) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

1 0

Re: [Mailman-Developers] SF bug report #223533
by Dan Mick 05 Apr '02

05 Apr '02

> I'd like to get some feedback on bug #223533: > > http://sourceforge.net/tracker/index.php?func=detail&aid=223533&group_id=10… d=100103 > > It's fairly old <blush> but it's complaining that there is no way to > tell the difference between a list posting and an administrative > message via the List-* headers. What's an "administrative message"?

1 0

Re: [Mailman-Developers] Almost there (was Problem in 2.1b1's contrib/qmail-to-mailman.py)
by barry＠zope.com 05 Apr '02

05 Apr '02

>>>>> "BW" == Bill Wagner <bwagner(a)potpie.org> writes: BW> mailmanctl is running and the cronjob's in place so I don't BW> know the next step. I'm presuming that all messages go into BW> the shunt dir first before being delivered, (is this BW> incorrect?) but what would cause them to not be flushed? qfiles/shunt is where messages go when Mailman is behaving snooty, i.e. there are bugs. You'll always get tracebacks in logs/error when this happens. Messages never get unshunted automatically, the standard rhythm is you <wink> fix the bugs and then run bin/unshunt to throw them back into whatever queue they were in when the bugs occurred. What's in logs/error? -Barry

1 2

mm-handler redux
by Ron Jarrell 05 Apr '02

05 Apr '02

Ok. Diff against cvs again. Handles the VERP tokens just fine. If I wasn't *still* here fiddling at 7am it'd probably be a tad more elegant, but it work. Index: mm-handler =================================================================== RCS file: /cvsroot/mailman/mailman/contrib/mm-handler,v retrieving revision 1.1 diff -r1.1 mm-handler 1c1 < #!/opt/bin/perl --- > #!/usr/local/bin/perl 5d4 < 7,11c6,17 < ## testlist: "|/opt/pkgs/mailman/mail/wrapper post testlist" < ## testlist-admin: "|/opt/pkgs/mailman/mail/wrapper mailowner testlist" < ## testlist-request: "|/opt/pkgs/mailman/mail/wrapper mailcmd testlist" < ## owner-testlist: testlist-admin < ## testlist-owner: testlist-admin --- > ## > ##testlist: "|/home/mailman/mail/mailman post testlist" > ##testlist-admin: "|/home/mailman/mail/mailman admin testlist" > ##testlist-bounces: "|/home/mailman/mail/mailman bounces testlist" > ##testlist-confirm: "|/home/mailman/mail/mailman confirm testlist" > ##testlist-join: "|/home/mailman/mail/mailman join testlist" > ##testlist-leave: "|/home/mailman/mail/mailman leave testlist" > ##testlist-owner: "|/home/mailman/mail/mailman owner testlist" > ##testlist-request: "|/home/mailman/mail/mailman request testlist" > ##testlist-subscribe: "|/home/mailman/mail/mailman subscribe testlist" > ##testlist-unsubscribe: "|/home/mailman/mail/mailman unsubscribe testlist" > ##owner-testlist: testlist-owner 14,15c20,21 < $MMWRAPPER = "/opt/pkgs/mailman/mail/wrapper"; < $MMLISTDIR = "/var/mailman/lists"; --- > $MMWRAPPER = "/home/mailman/mail/mailman"; > $MMLISTDIR = "/home/mailman/lists"; 122a129,130 > my @validfields = qw(admin bounces confirm join leave owner request > subscribe unsubscribe); 124,126c132 < if ($addr =~ /(.*)-admin$/ < || $addr =~ /(.*)-owner$/ < || $addr =~ /^owner-(.*)$/) { --- > if ($addr =~ /(.*)-(.*)\+.*$/) { 128,129c134,136 < $cmd = "mailowner"; < } elsif ($addr =~ /(.*)-request$/) { --- > $cmd = "$2"; > } else { > $addr =~ /(.*)-(.*)$/; 131c138,144 < $cmd = "mailcmd"; --- > $cmd = $2; > } > if (grep /^$cmd$/, @validfields) { > if ($list eq "owner") { > $list = $cmd; > $cmd = "owner"; > } 190c203 < if (! -f "$MMLISTDIR/$list/config.db") { --- > if (! -f "$MMLISTDIR/$list/config.pck") { 192c205 < if (! -f "$MMLISTDIR/$list/config.db") { --- > if (! -f "$MMLISTDIR/$list/config.pck") {

2 1

Re: [Mailman-Developers] Problem in 2.1b1's contrib/qmail-to-mailman.py
by barry＠zope.com 05 Apr '02

05 Apr '02

>>>>> "BW" == Bill Wagner <bwagner(a)potpie.org> writes: BW> That patch basically just changes it to point to mail/mailman BW> now, right? Check cvs because I also just caught up on a few changes that Ben Gertzfield contributed. >> From what I can tell, it's still not going to work. I know you >> said that BW> qmailsupport's basically left up to the community, so I just BW> want to get as much info out there as I can (as I don't know a BW> damn thing about python) so maybe someone who does and uses BW> qmail can try and fix this. BW> At any rate, when changed to point to mail/mailman, the BW> deferral message says that mailcmd is an illegal command. Is BW> this something that's been left over from 2.0.x and has been BW> depreciated for another equivalent in 2.1? I might not know BW> any python, but I'm not afraid to hack code :) It would help to see the exact error message. If mailcmd is exiting with an error code 2, it's probably the classic wrong-gid problem: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.004.htp If it's something else, then check cvs and see if the latest updates fix the problem. BW> And on a similar line of questioning, in 2.0.x, there was an BW> option available called MTA_ALIASES_STYLE which I'd typically BW> set to 'qmail' in my Mailman/mm_cfg.py. It'd tell you what to BW> do in order to create the .qmail-* files for the list but it BW> doesn't seem to exist in 2.1 either? Am I right in this BW> orjust smoking crack? Correct, this isn't useful anymore. For someone who is knowledgeable about qmail, the thing to do is to take Mailman/MTA/Manual.py and port the output to qmail and wrap it all in a file appropriate for Mailman/MTA/Qmail.py. This would allow you to set this in your mm_cfg.py file: MTA = 'Qmail' Then again, it'd be better if qmail could just be taught to automatically recognize Mailman lists, but again, I don't know enough about qmail to write the appropriate recipes. -Barry

1 0

Re: [Mailman-Developers] Problem in 2.1b1's contrib/qmail-to-mailman.py
by barry＠zope.com 05 Apr '02

05 Apr '02

>>>>> "BW" == Bill Wagner <bwagner(a)potpie.org> writes: BW> First off, I'm sorry if this isn't the appropriate forum, but BW> I felt it more appropriate than mailman-users. This one's fine! BW> I'm running a Mandrake 8.0 box with qmail and have 2.0.9 BW> running fine but am testing 2.1b1 and have run into a problem. BW> When passing mail through qmail-to-mailman.py, lines 87 and 88 BW> point to $prefix/mail/wrapper. I've done plenty of test BW> installs of 2.1b1, but in none ofthem is there ever a BW> $prefix/mail/wrapper. There's a mail/mailman, but that'snot BW> what qmail-to-mailman.py looks for. I did a test and modified BW> it to point tomail/mailman, but that results in a deferral BW> like: I don't use qmail so it's up to the community to keep the qmail documentation and contribs up-to-date. BW> So I was wondering if this is a known issue and if anyone BW> might have an idea of a quick workaround. Is mail/wrapper now BW> obsolete? Yes, mail/wrapper is obsolete; it's been renamed mail/mailman to avoid unnecessary conflicts with MD's wrapper program. A dumb replace yields the following patch (committed to cvs, though if the whole file needs updating, please send contributions). -Barry Index: qmail-to-mailman.py =================================================================== RCS file: /cvsroot/mailman/mailman/contrib/qmail-to-mailman.py,v retrieving revision 2.1 retrieving revision 2.2 diff -u -r2.1 -r2.2 --- qmail-to-mailman.py 7 Sep 2001 23:18:47 -0000 2.1 +++ qmail-to-mailman.py 5 Apr 2002 18:53:01 -0000 2.2 @@ -84,8 +84,8 @@ local = re.sub(i[0],"",local) if os.path.exists(local): - os.execv(MailmanHome + "/mail/wrapper", - (MailmanHome + "/mail/wrapper", type, local)) + os.execv(MailmanHome + "/mail/mailman", + (MailmanHome + "/mail/mailman", type, local)) else: bounce() sys.exit(111)

1 0

README.POSTFIX patch
by Jon Parise 05 Apr '02

05 Apr '02

It looks like README.POSTFIX is missing a word in here. See the attached patch. -- Jon Parise (jon(a)csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member

2 1

Problem in 2.1b1's contrib/qmail-to-mailman.py
by Bill Wagner 05 Apr '02

05 Apr '02

Good morning, First off, I'm sorry if this isn't the appropriate forum, but I felt it more appropriate than mailman-users. I'm running a Mandrake 8.0 box with qmail and have 2.0.9 running fine but am testing 2.1b1 and have run into a problem. When passing mail through qmail-to-mailman.py, lines 87 and 88 point to $prefix/mail/wrapper. I've done plenty of test installs of 2.1b1, but in none ofthem is there ever a $prefix/mail/wrapper. There's a mail/mailman, but that'snot what qmail-to-mailman.py looks for. I did a test and modified it to point tomail/mailman, but that results in a deferral like: Apr 5 09:46:25 oscar qmail: 1018028785.696995 delivery 1125: deferral: Illegal_command:_mailcmd/ So I was wondering if this is a known issue and if anyone might have an idea of a quick workaround. Is mail/wrapper now obsolete? Thanks, Bill -- Did you hear that, Marge? She called me a baboon! The stupidest, ugliest, smelliest ape of them all! -- Homer Simpson Lisa's Substitute

1 0

mailman filter for SpamAssassin support
by James Henstridge 05 Apr '02

05 Apr '02

I uploaded a patch to the SF bug tracker today that adds support for doing SpamAssassin (http://spamassassin.taint.org/) checks to the mailman message pipeline: http://sourceforge.net/tracker/?func=detail&aid=534577&group_id=103&atid=30… This will contact the spamd daemon to score the message. If the message gets scored above one threshold, it gets discarded (this defaults to 10, but can be customised in the mm_cfg.py file). If the message scores above another lower threshold, it gets held for moderation (this defaults to 5). I wrote this to try and reduce the number of messages held for moderation. I wrote it for mailman 2.0.x (as that is what I am using at the moment), but it should be fairly easy to update for 2.1. It might be worth using on the python.org mailing lists ... James. (I am not on the mailing list, so please don't remove me from the CC list on replies). -- Email: james(a)daa.com.au WWW: http://www.daa.com.au/~james/

4 4