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

[Barry Warsaw]

On Aug 31, 2009, at 1:15 PM, C Nulk wrote:

> I am pretty sure allowing the raw email addresses to be available is
> going to go over like a lead balloon here.  Anything (however minor)  
> to
> help protect the users/clients email addresses is helpful despite what
> others think.  It is fine if someone considers the obfuscation that
> Mailman uses is trivial, however, anything I can do to make it  
> harder or
> more computationally time-invested to get the email address is better
> than giving it away.  Sure bots are out there but if what I do helps
> slow down someones system to make them look at it (and hopefully get  
> rid
> of the bot), then great.   But at least give me the choice to be  
> able to
> do it.

Agreed.

> I happened to like Barry's (?) earlier comment about the "send me this
> message" link.  Or maybe "send my message to the original poster" link
> where you can click on the link, compose your message, and send it
> through Mailman all without the original sender's address.  Mailman or
> whatever process can figure out the original sender and pass on the  
> your
> message.  Yes, I know it is more work that is why we have computers :)

The difficult part about the latter is that I hate web interfaces for  
reading/composing email (Gmail included).  I want to use my mail  
reader for that!

> As for using robots.txt, hmm, it is not the legitimate search  
> engines I
> care about, it is the search engines/crawlers that do not respect my
> robots.txt file that I care about.  If I had an effective way to
> consistently identify those non-legitimate crawlers, I would add  
> what I
> needed to drop them into my firewall as I recognized them.

Agreed.
-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/67ab203d/attachment-0001.pgp>