From: Jason Molenda <jason-swarelist@molenda.com>
To: overseers@sources.redhat.com
Subject: New version of mhonarc installed
Date: Wed, 19 Feb 2003 06:55:00 -0000 [thread overview]
Message-ID: <20030218225518.A13897@molenda.com> (raw)
FYI, I upgraded mhonarc to 2.6.0. It has one new feature that may
be of interest -- it can be configured to munge e-mail addresses
in the body of messages. Until now, mhonarc would only munge e-mail
addresses in the headers. I'm uninterested in enabling the
body-email-message-munging because it seems too likely to fail, but
I figured I'd mention it.
There was also a discussion on the mhonarc mailing list over the
past couple weeks about address munging schemes. Most involve
protecting the archives with well-known passwords that humans can
trivially figure out, but that would hose the search engines so
that's not so cool. One person had an interesting suggestion:
http://www.mhonarc.org/archive/html/mhonarc-users/2003-02/msg00040.html
Which uses some clever HTTP trickery that the spam harvesters probably
can't get right now. But they could eventually figure it out..
(Incidentally, the date index at that web archive is pretty nice looking.)
J
next reply other threads:[~2003-02-19 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 6:55 Jason Molenda [this message]
2003-02-19 15:00 ` Christopher Faylor
2003-02-20 0:58 ` Jason Molenda
2003-02-20 1:26 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030218225518.A13897@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=overseers@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).