JC Dill wrote:
IMHO, this is a bug. Mailman should correctly parse email sent to:
"mylist-confirm+8a671672b88489848cd212b368d290cc343af848" mylist-confirm+8a671672b88489848cd212b368d290cc343af848@list.server
since that is a correctly formatted email address header per the example:
To: "Mary Smith: Personal Account" smith@home.example
in RFC 2822:
I agree that it's a bug, but I think the primary bug is in an MUA that is generating a reply to mail
From: smith@home.example
and addresses it
To: "smith@home.example" smith@home.example
However, I have no objection to Mailman "working around" this MUA bug :-) by changing
VERP_CONFIRM_REGEXP =r'^(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$'
in Defaults.py.in
I ask though, does anyone have a better suggestion for a replacement than
VERP_CONFIRM_REGEXP =
r'^(\s*"[^"]*")?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$'
or is that OK?
-- Mark Sapiro msapiro@value.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan