[Mailman-Users] Reactivate delivery confirmation tokens

James Cloos cloos at jhcloos.com
Fri Jul 19 20:18:08 CEST 2013

>>>>> "MS" == Mark Sapiro <mark at msapiro.net> writes:

MS> I understood that, but what else happens? What response do you get from
MS> the web server when you go to the mailman/confirm/$LISTNAME/$TOKEN uri?

Sorry; I thought that was clear.  Replies to the confirm mail generate
an invalid token reply; surfing to the token uri returns an invalid
token page.

MS> Do other confirmations, e.g. subscription requests, work?

Yes.  As I wrote, all confirmation tokens generated by active requests
always work, whether change-of-email-address, subscribe or unsubscribe.

A few sites over the years only supported email or only supported http,
but the tokens never generated invalid errors unless they came as part
of a please-reply-to-reactivate mail.

In other words, tokens generated by the cgi or by sending a subscribe or
unsubscribe mail work, but tokens generated by class Bouncer are always

Is the cookie expiring before the mail is sent?

I see the comment in Bouncer.py about trying to avoid that, but that
would explain things.

James Cloos <cloos at jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

More information about the Mailman-Users mailing list