[Mailman-Developers] Bug? Refused subscription confirmation
lists05 at equinephotoart.com
Fri Mar 17 06:06:44 CET 2006
Mark Sapiro wrote:
> 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
> which doesn't work. Then there's been an error, so the confirm command
> in the body is not processed.
> The user can use a different MUA
That's a work-around rather than a solution. This problem needlessly
makes it harder for both list owners and subscribers to use Mailman
> The user can manually edit the To: to remove the "real name"
IMHO, this is a bug. Mailman should correctly parse email sent to:
<mylist-confirm+8a671672b88489848cd212b368d290cc343af848 at list.server>
since that is a correctly formatted email address header per the example:
To: "Mary Smith: Personal Account" <smith at home.example>
in RFC 2822:
More information about the Mailman-Developers