Mailman 3 July 2002 - Mailman-Developers

Problem with 2.0.12 configure
by Bill Bradford 24 Jul '02

24 Jul '02

root@ohno:/usr/local/src/mailman-2.0.12> sh ./configure --prefix=/usr/local/mailman loading cache ./config.cache checking for --with-python... no checking for python... /usr/local/bin/python checking Python interpreter... /usr/local/bin/python checking Python version... 2.2.1c1 checking for a BSD compatible install... /usr/local/bin/install -c checking whether make sets ${MAKE}... yes checking for true... /usr/bin/true checking for --without-gcc... no checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking whether #! works in shell scripts... yes checking for --with-var-prefix... no checking for --with-username... mailman checking for mailman UID... 10004 checking for --with-groupname... mailman checking for mailman GID... 10004 checking permissions on /usr/local/mailman... okay checking for mail wrapper GID... 1 checking for CGI wrapper GID... 60001 checking for CGI extensions... no ./configure: test: unknown operator == Same result with sh or bash. Any suggestions? Nothing relevant in config.log.. Tracing the script, this is what I get: # attempt to figure out the default hostname and URL from socket import * import string import sys import os def barf(fqdn, www): sys.stdout = sys.stderr print 'host info not found, set \$MAILHOST and/or \$WWWHOST environ vars' print '\$MAILHOST=%s, \$WWWHOST=%s' % (fqdn, www) sys.exit(1) fqdn = os.environ.get('MAILHOST') www = os.environ.get('WWWHOST') aliases = [] if fqdn: aliases.append(fqdn) if www: aliases.append(www) if not fqdn: try: host, aliases, ipaddrs = gethostbyaddr(gethostbyname(gethostname())) except herror: barf(fqdn, www) aliases.insert(0, host) for h in aliases: parts = string.split(h, '.') if 5 > 1: if parts[0] == 'www': www = h elif not fqdn: fqdn = h if www and fqdn: break if fqdn is None: barf(fqdn, www) if www is None: www = fqdn fp = open('conftest.out', 'w') if not www and fqdn: fp.write('%s\n%s\n' % (fqdn, fqdn)) elif www: dhn = string.join(string.split(www, '.')[1:], '.') fp.write('%s\n%s\n' % (dhn, www)) else: fp.write('please.change.me\nwww.please.change.me\n') fp.close() EOF $PYTHON conftest.py if [ "$?" == "1" ] then exit fi ./configure: test: unknown operator == Bill -- bill bradford / mrbill(a)mrbill.net / austin, texas ------------------------------------------------------------------------- I'm reminded of the day my daughter came in, looked over my shoulder at some Perl 4 code, and said, "What is that, swearing?" -- Larry Wall

2 1

[ mailman-Patches-585643 ] Mailman 2.0.13 candidate patch
by noreply＠sourceforge.net 23 Jul '02

23 Jul '02

Patches item #585643, was opened at 2002-07-23 18:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=585643&group_i… Category: None Group: Mailman 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Mailman 2.0.13 candidate patch Initial Comment: Mailman 2.0.12 had compatibility problems with Python 1.5.2. This patch fixes these AFAICT, and a few other small bugs that have cropped up. Note that this is a candidate patch. The actual MM2.0.13 patch may be different. However I would really appreciate folks using Mailman 2.0.12 (especially if you're using Python 1.5.2) to give this patch a try and see if it fixes your problems. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=585643&group_i…

1 0

RE: [Mailman-Developers] [MAILER-DAEMON@mira.linknet.com.au:Undeliverable Mail]
by Dan Kohn 23 Jul '02

23 Jul '02

"user(a)domain.com <user(a)domain.com>" is not legal under RFC 2822. It is must not generate under either current (section 3) or obsolete (section 4) grammar. <mailbox> is defined as "[display-name] angle-addr", <display-name> is a <phrase>, which is "1*word", where <word> is "atom / quoted-string". <atom> is defined in section 3.2.4 *not* to include "@". In other words, you can't use an unquoted "@" in a <display-name> under either current or obsolete grammar. However, you could include the @ as part of a <quoted-string>, defined in section 3.2.5. Thus, the following: user(a)domain.com <user(a)domain.com> <-- illegal "user\(a)domain.com" <user(a)domain.com> <-- legal I'm cc'ing ietf-822(a)imc.org, which has taken the place of comp.mail.headers, for confirmation. - dan -- Dan Kohn <mailto:dan@dankohn.com> <http://www.dankohn.com/> <tel:+1-650-327-2600> -----Original Message----- From: Jay R. Ashworth [mailto:jra@baylink.com] Sent: Saturday, July 20, 2002 09:12 To: mailman-developers(a)python.org Subject: Re: [Mailman-Developers] [MAILER-DAEMON@mira.linknet.com.au:Undeliverable Mail] On Sat, Jul 20, 2002 at 12:13:08PM -0400, Terri Oda wrote: > I've been getting these periodically from one of my list members' servers > and I'm curious... is > To: user(a)domain.com <user(a)domain.com> > really an invalid address? MailMAX is the only server I've ever seen thrown > an error on this. > > I keep meaning to email them and ask what's up, since it seems like a bug to > me, but before I do, does anyone know if this is actually an invalid address > and other servers just deal with it? According to my reading of RFC 2822 3.4, no, it's fine: if a mailbox can be a name-addr, and a name-addr is a display-name followed by an angle-addr, then the display-name should be treated as a comment by any mailre, provided that the angle-addr is syntactically correctly constructed. But this is more properly a topic for comp.mail.headers. (Does that NG still exist? ;-) Cheers, -- jra -- Jay R. Ashworth jra(a)baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") _______________________________________________ Mailman-Developers mailing list Mailman-Developers(a)python.org http://mail.python.org/mailman-21/listinfo/mailman-developers

4 5

Mailman 2.0.12 error
by Kory Wheatley 23 Jul '02

23 Jul '02

This is very critical I get this fixed, I'm running 150 production mailing lists, here's my problem. I keep receiving this below error when messages are sent to my lists. I'm running Red Hat 7.2 mailman 2.0.12. Does anyone know the solution? If I take them out of the qfiles directory and then put a few in at a time then the messages are sent rather than piling up in the qfiles directory and setting there idle. I've had this problem the day after I upgraded to mailman 2.0.12 from mailman 2.0.11, is there a patch fix. qrunner(18056): Traceback (innermost last): qrunner(18056): File "/home/mailman/cron/qrunner", line 283, in ? "/home/mailman/cron/qrunner", line 283, in ? qrunner(18056): kids = main(lock) qrunner(18056): File "/home/mailman/cron/qrunner", line 253, in main qrunner(18056): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(18056): File "/home/mailman/cron/qrunner", line 157, in dispose_message qrunner(18056): mlist.ParseMailCommands(msg) qrunner(18056): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands qrunner(18056): precedence = msg.get('precedence', '').lower() qrunner(18056): AttributeError : 'string' object has no attribute 'lower' qrunner(18059): Traceback (innermost last): qrunner(18059): File "/home/mailman/cron/qrunner", line 283, in ? qrunner(18059): kids = main(lock) qrunner(18059): File "/home/mailman/cron/qrunner", line 253, in main qrunner(18059): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(18059): File "/home/mailman/cron/qrunner", line 157, in dispose_message qrunner(18059): mlist.ParseMailCommands(msg) qrunner(18059): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands qrunner(18059): precedence = msg.get('precedence', '').lower() qrunner(18059): AttributeError : 'string' object has no attribute 'lower' qrunner(18066): Traceback (innermost last): -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

2 1

ASCII Prefixes
by barry＠zope.com 23 Jul '02

23 Jul '02

Here's a tricky issue, one with a high rabbit hole probability (which I'd like to avoid if possible ;). Say you've got a mailing list that accepts both French and English, with French as the default language. The default charset for French is iso-8859-1 and for English us-ascii. Now say you want to add a prefix to your list, say "[MyList]", and you're users like to send messages to the list with funny <wink> non-ascii characters in iso-8859-1. What Mailman 2.1 cvs will do now is encode the prefix using the charset for the list's default language. So you'd likely end up with a Subject: header like Subject: =?iso-8859-1?q?[MyList]_?= =?iso-8859-1?hello_world?= or some such. Encoding the prefix can be considered ugly, but unfortunately we don't really have a way to specify a charset for the subject prefix (or footers, or other added text) apart from the default language's charset. So this is /almost/ the best we can do, even though it's kind of ugly. OTOH, we could use a simple heuristic to try to keep the prefix unencoded in the common case: if the prefix contains only ascii characters, we could choose to leave it in the default us-ascii (or really the None) encoding. If it contains non-ascii characters, we'd have no choice but to encode it. I really don't want to go down the path of providing a gui for different prefixes for each supported language. Eventually, maybe that's what we need to do, but I'd like to avoid that for MM2.1. I think this approach should be good enough, but I'd like to hear comments, especially from Asian language users. -Barry

2 1

[ mailman-Bugs-585484 ] virtual domain lists misdirect autoreply
by noreply＠sourceforge.net 23 Jul '02

23 Jul '02

Bugs item #585484, was opened at 2002-07-23 16:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585484&group_i… Category: bounce detection Group: None Status: Open Resolution: None Priority: 5 Submitted By: Byron T. Watts (btwatts) Assigned to: Nobody/Anonymous (nobody) Summary: virtual domain lists misdirect autoreply Initial Comment: Using mailman with virtual domain hosting. Bounced messages for a particular list are going to the wrong list administrator (not even on the same domain). The particular notices that I'm seeing misdirected, are the <i>useridi> is on vacation messages. I am not certain whether other messages are being similarly misdirected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585484&group_i…

1 0

[ mailman-Bugs-585270 ] qrunner fails with RHL7.2 python 1.5.2
by noreply＠sourceforge.net 23 Jul '02

23 Jul '02

Bugs item #585270, was opened at 2002-07-23 17:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585270&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Stuart Prescott (themill) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner fails with RHL7.2 python 1.5.2 Initial Comment: qrunner from mailman-2.0.12 (downloaded and installed from the src tarball) fails with Python 1.5.2 from RHL7.2 python-1.5.2-38. Error message from $prefix/logs/error is attached as is a patch that does seem to fix the problem and allow Mailman to work. (I'm not a Python programmer .. I noramlly use P**L so I'm not sure exactly what or why... please treat my patch with the greatest skepticism!) >From the mailing lists, there are quite a few ppl having problems with the RHL distributions of Python -- is this a compatability thing (that we can argue about whether it's RHL or Mailman that is at fault a la gcc for years to come?) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585270&group_i…

1 0

[MAILER-DAEMON@mira.linknet.com.au: Undeliverable Mail]
by Terri Oda 23 Jul '02

23 Jul '02

I've been getting these periodically from one of my list members' servers and I'm curious... is To: user(a)domain.com <user(a)domain.com> really an invalid address? MailMAX is the only server I've ever seen thrown an error on this. I keep meaning to email them and ask what's up, since it seems like a bug to me, but before I do, does anyone know if this is actually an invalid address and other servers just deal with it? ----- Forwarded message from MailMAX Error Responder <MAILER-DAEMON(a)mira.linknet.com.au> ----- Delivery-date: Sat, 20 Jul 2002 11:45:31 -0400 From: "MailMAX Error Responder" <MAILER-DAEMON(a)mira.linknet.com.au> Subject: Undeliverable Mail When we said... DATA .. the remote server gave us this error response ... 550 Syntax error in 'To' header: malformed address: <courses(a)linuxchix.org>\n may not follow courses(a)linuxchix.org : failing address is: courses(a)linuxchix.org <courses(a)linuxchix.org> This is a Permanent error, and we will not try to deliver it again. *** This message was automatically generated by the MailMAX Error Responder ***

4 3

[ mailman-Bugs-585229 ] opening holes by changing permissions?
by noreply＠sourceforge.net 23 Jul '02

23 Jul '02

Bugs item #585229, was opened at 2002-07-22 22:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585229&group_i… Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: opening holes by changing permissions? Initial Comment: I was having problems adding a list in Mailman 2.1beta via the web interface, it was giving me an error regarding permissions to the mailman/data/aliases.db file. This is the error I got: ... File "/var/mailman/Mailman/MTA/Postfix.py", line 46, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/mailman/data/aliases (status: 1, Operation not permitted) To fix this I changed the permissions on this file so apache could write to it. chmod a+w aliases.db This did fix the problem of creating and deleting lists via the web interface. Does anyone know if this would open up any security holes? Is there another way to fix the permissions problem that is more logical? Thanks for your help. Paul Marshall ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585229&group_i…

1 0

Mailman 2.0.12 error
by Kory Wheatley 22 Jul '02

22 Jul '02

I keep receiving this error when messages are sent to my lists. I'm running Red Hat 7.2 mailman 2.0.12. Does anyone know the solution? Jul 20 12:02:00 2002 qrunner(18056): Traceback (innermost last): Jul 20 12:02:00 2002 qrunner(18056): File "/home/mailman/cron/qrunner", line 283, in ? Jul 20 12:02:00 2002 qrunner(18056): kids = main(lock) Jul 20 12:02:00 2002 qrunner(18056): File "/home/mailman/cron/qrunner", line 253, in main Jul 20 12:02:00 2002 qrunner(18056): keepqueued = dispose_message(mlist, msg, msgdata) Jul 20 12:02:00 2002 qrunner(18056): File "/home/mailman/cron/qrunner", line 157, in dispose_message Jul 20 12:02:00 2002 qrunner(18056): mlist.ParseMailCommands(msg) Jul 20 12:02:00 2002 qrunner(18056): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands Jul 20 12:02:00 2002 qrunner(18056): precedence = msg.get('precedence', '').lower() Jul 20 12:02:00 2002 qrunner(18056): AttributeError : 'string' object has no attribute 'lower' Jul 20 12:03:00 2002 qrunner(18059): Traceback (innermost last): Jul 20 12:03:00 2002 qrunner(18059): File "/home/mailman/cron/qrunner", line 283, in ? Jul 20 12:03:00 2002 qrunner(18059): kids = main(lock) Jul 20 12:03:00 2002 qrunner(18059): File "/home/mailman/cron/qrunner", line 253, in main Jul 20 12:03:00 2002 qrunner(18059): keepqueued = dispose_message(mlist, msg, msgdata) Jul 20 12:03:00 2002 qrunner(18059): File "/home/mailman/cron/qrunner", line 157, in dispose_message Jul 20 12:03:00 2002 qrunner(18059): mlist.ParseMailCommands(msg) Jul 20 12:03:00 2002 qrunner(18059): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands Jul 20 12:03:00 2002 qrunner(18059): precedence = msg.get('precedence', '').lower() Jul 20 12:03:00 2002 qrunner(18059): AttributeError : 'string' object has no attribute 'lower' Jul 20 12:04:06 2002 qrunner(18066): Traceback (innermost last): Kory Wheatley

1 0