[Mailman-Developers] Bug? Refused subscription confirmation

Mark Sapiro msapiro at value.net
Thu Mar 16 18:34:19 CET 2006


Giuliano Gavazzi wrote:

>To: "mylist-confirm+8a671672b88489848cd212b368d290cc343af848"
>	<mylist-confirm+8a671672b88489848cd212b368d290cc343af848 at list.server>


This is the problem. You have VERP_CONFIRMATIONS = Yes so the
confirmation is From: and the user's reply should be To:

mylist-confirm+8a671672b88489848cd212b368d290cc343af848 at list.server

but the user's MUA has replied To: as above.

VERP_CONFIRM_REGEXP doesn't expect this and parses the cookie as

8a671672b88489848cd212b368d290cc343af848"
<mylist-confirm+8a671672b88489848cd212b368d290cc343af848

which doesn't work. Then there's been an error, so the confirm command
in the body is not processed.

Solutions:

The user can use a different MUA

The user can manually edit the To: to remove the "real name"

You can change VERP_CONFIRM_REGEXP in mm_cfg.py to parse this one
without breaking normal ones. Possibly something like

VERP_CONFIRM_REGEXP = \
r'^(\s*"[^"]*")?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$'

will work

>Note that the confirmation string is correct but that the  
>confirmation string also appears in evictions.


It has a time still in the future, so this is normal.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan



More information about the Mailman-Developers mailing list