Earl Hood <[EMAIL PROTECTED]> writes:
> > Ah yes, didn't occur to me when you said "hiding sender addresses" that only
> > the address in the header was being talked about. People like me who
> > reiterate their email addresses in their .sigs will be exposing them. And I
> > just checked and mail-archive is indexed by AltaVista, so there certainly is
> > a danger from the SPAM-bots that trawl the web picking up all strings
> > matching an email address regexp.
>
> One reason addresses in message bodies are not mangled, as you mentioned,
> is that they could mangle data that should be be mangled. Mainly
> message-ids referenced in bodies that could be hyperlinked.
Ah yes. Didn't occur to me that the regexp for a message ID and an email
address is basically the same (unless you say that an email address is that
regexp when it's not preceded by "Message-Id: ").
> Another reason is copyright law. If the sender wants to avoid
> address harvesting, then they should avoid including his/her address
> in the body, or mangle it himself.
Don't see how B flows from A, but...
> > Hmmm, of course there'd still be opportunities to expose addresses, like
> > when quoting source files that include people's addresses in comments and so
> > on.
>
> People should take care about this, regardless.
Yes, they _should_, but they may not. And if I accidentally quote your
address in somewhere in a message, it gets exposed to SPAMmers through no
fault of your own.
> > I guess my ideal mailing list archiver would mangle everything that fit an
> > email address regexp. Of course, the regexp might accidentally match
>
> See comments above why mangling is not done in bodies.
I'm not copyright expert, of course, but I'd be real surprised if the law
was written such that it's okay to mangle an email message header but not
its body.
In any case, sounds like restricting archive access to list members is the
right way to do it. Then you don't have to do any mangling.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
