[Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr
noreply@sourceforge.net
noreply@sourceforge.net
Thu, 02 May 2002 20:18:11 -0700
Bugs item #517192, was opened at 2002-02-13 21:20
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103
Category: mail delivery
Group: 2.0.x
Status: Open
Resolution: Out of Date
Priority: 5
Submitted By: CrackMonkey (monkeymaster)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.0.8 borks on dot in local part of addr
Initial Comment:
In a mail address's local part (the part to the left of
the at sign), it is perfectly valid to have periods.
However, mailman stops reading the address right at the
@, so that "mr.bad@pigdog.org" is shown as "mr.bad".
this is disastrous for lists where only subscribers are
allowed to post, since the system doesn't allow for
exceptions that lack an @ and a FQDN.
Either allowing exceptions to be of a more forgiving
format, or fixing the broken regex that truncates the
mail addresses would solve my problem. I'm getting
tired of moderating a legitimate user's posts,
especially since the system won't even send the
warnings to the correct address.
----------------------------------------------------------------------
Comment By: Dan Mick (dmick)
Date: 2002-05-03 03:18
Message:
Logged In: YES
user_id=10725
I can echo that Python 2.2 doesn't have the parseaddr
problem. monkeymaster, can you try Barry's two-line
experiment and see if that works or fails?
----------------------------------------------------------------------
Comment By: CrackMonkey (monkeymaster)
Date: 2002-04-29 22:21
Message:
Logged In: YES
user_id=76237
This happens even when I use python 2.2
----------------------------------------------------------------------
Comment By: Barry Warsaw (bwarsaw)
Date: 2002-04-27 16:34
Message:
Logged In: YES
user_id=12800
This is really a bug with earlier versions of Python, I
believe. MM2.0.x uses the standard library function
rfc822.parseaddr() to break and address into its realname +
email constituent parts. Here are some examples:
% python
Python 2.2.1 (#1, Apr 22 2002, 17:14:12)
[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2
Type "help", "copyright", "credits" or "license" for more
information.
>>> from rfc822 import parseaddr
>>> parseaddr('Mr. Bad <mr.bad@pigdog.org>')
('Mr. Bad', 'mr.bad@pigdog.org')
% python2.1
Python 2.1.3 (#1, Apr 22 2002, 18:17:38)
[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> from rfc822 import parseaddr
>>> parseaddr('Mr. Bad <mr.bad@pigdog.org>')
('', 'Mr.Bad')
So this is clearly broken in Python 2.1.3, and works in
Python 2.2.1. I'll look at backporting the fix to Python
2.1 in case there's ever a 2.1.4. But if you're using an
earlier version of Python, this will still be broken.
Consider upgrading to Python 2.2.1.
----------------------------------------------------------------------
Comment By: CrackMonkey (monkeymaster)
Date: 2002-04-26 19:54
Message:
Logged In: YES
user_id=76237
The bug turns out not to be when there is a period in the
address, but in the plain text name. The mail address in
question is:
Mr. Bad <mr.bad@pigdog.org>
I realized this when I saw people who had different text
names from their e-mail addresses, as in:
Jr. Pickle <picklejr@someplace.foo>
This would show up as the mythical address "jr.pickle" in
mailman, and things would b0rk.
----------------------------------------------------------------------
Comment By: Barry Warsaw (bwarsaw)
Date: 2002-03-14 19:18
Message:
Logged In: YES
user_id=12800
Either I need more information, or this problem is fixed in
MM2.1. Quite often I uses test addresses like
"barry.warsaw@<wherever>" and I've had no problems with it.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103