Richard Damon wrote: >I think another issue is that if the user replies with an HTML formatted >message, I don't think the processor will necessarily be able to parse >it.
This should not be an issue. The format of the message body, e.g. non-MIME plain text, MIME text/plain, MIME text/html, MIME multipart and even its content is irrelevant. If VERP_CONFIRMATIONS is No which is the default, the confirmation request is From: listname-requ...@example.com with Subject: confirm CONFIRMATION_TOKEN Whatever the content of the reply, the user's MUA should address it To: listname-requ...@example.com with the same subject possibly preceded by Re: or similar as in Subject: Re: confirm CONFIRMATION_TOKEN The request processor is clever enough to remove the first 'word' from the subject if it's not a recognized command, and it also decodes RFC 2047 encoded subjects so the confirmation should succeed unless the subject gets more that one word prepended to it. If VERP_CONFIRMATIONS is set to Yes in mm_cfg.py, the confirmation request is From: listname-confirm+confirmation_to...@example.com with Subject: Your confirmation is required to join the LISTNAME mailing list or its i18n translation and any reply To: listname-confirm+confirmation_to...@example.com will succeed. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
