[Mailman-Developers] Proposed: remove address-obfuscation code from Mailman 3

[Barry Warsaw]

On Aug 31, 2009, at 3:00 PM, Dale Newfield wrote:

> Barry Warsaw wrote:
>> Let's say I just joined the XEmacs development mailing list after a  
>> long absence.  I find a message in the archive from two years ago  
>> that is relevant to an issue I'm having.  I'd like to follow up to  
>> that message using my normal mail toolchain, but I found the  
>> archive page through Google.  I should be able to click on a link  
>> on that page, enter my email address (perhaps through some  
>> validation dance, or subject to a request governor) and then the  
>> message -- as it was originally copied to the list membership --  
>> would show up in my inbox, exactly as if I were a list member at  
>> the time.
>> Now I can hit 'reply' and inject myself seamlessly into that 2 year  
>> old thread.
>
> As long as the mailing list name/address hasn't migrated/changed in  
> the interim...

Good point.

> ...perhaps the original message munged to ensure current accuracy of  
> the to/cc/reply-to fields?

Not sure I understand; can you elaborate?

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20090831/e18a4fe8/attachment.pgp>