Leave choice on obfuscation method to sysadmin

[Alster]

As far as I know, currently the way pipermail
obfuscates email addresses is hardcoded to "user at
domain.com". This is really easy to harvest.

It may be a better idea to leave the method of
obfuscation to the mailman (sys)admin (not list admin).
This will result in increased diversity of obfuscation
methods on the several pipermail setups and thus to
decreased harvesting.

[http://sourceforge.net/tracker/index.php?func=detail&aid=1059637&group_id=103&atid=100103]

[Khali-users (khali-users)]

I would second this request. The current obfuscation scheme
is next to useless. I understand that it would make little
sense hardcoding a more complex obfuscation scheme, as it
could easily be reverse-engineered. However, if the
obfuscation method was left to the administrator, there
would be virtually as many different obfuscation schemes as
sites, so reverse-engineering would be much more difficult,
if impossible.

As a side note, I wonder why there is no option in mailman
to plain discard the e-mail addresses from the Archive. This
should be even more simple to implement, and sufficient at
least for my own needs.

[Fabián Rodríguez (magicfab)]

I agree this should be addressed as more and more bots &
agents harvest public lists for this information. Even
private lists that are not tuning 2.1.6 may be vulnerable to
this harvesting method.

I'd like to suggest to use a random obfuscation method *for
each message* .

[Fabián Rodríguez (magicfab)]

This would also affect messages that are already archived or
the existing methods for archival of messages. See this in
the Mailman FAQ:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.034.htp

Some docs on making your lists less vulnerable to harvesting:
http://www.list.org/mailman-member/node40.html

Other related threads:
http://mail.python.org/pipermail/mailman-developers/2004-February/016569.html
http://zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanProblems