From: "Andrew K. Bressen" <google@mirror.to>
Subject: Re: moving spam
Date: Wed, 01 Oct 2003 20:19:03 -0400 [thread overview]
Message-ID: <pan.2003.10.02.00.18.51.305579@mirror.to> (raw)
In-Reply-To: <m2fzimpdv7.fsf@maui.hanak.hu>
> It works perfectly. I even have a simple elisp function that moves a mail
> to the spam folder, marks it as expirable and puts its sender on the SA
> blacklist.
You might want to be careful about that last part;
that virus run a month or two ago (sobig? don't remember which one)
grabbed address books and used them as fake
from lines. I actually got a copy that had the return
address of someone I knew, even though the machine it
came from had nothing to do with either of us
so far as we could tell.
I also got bounces telling me some infected pc tried
to send a copy with my address as the originator to
Mitch Kapor, among other folks. Sigh.
parent reply other threads:[~2003-10-02 0:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m2fzimpdv7.fsf@maui.hanak.hu>]
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=pan.2003.10.02.00.18.51.305579@mirror.to \
--to=google@mirror.to \
/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 NNTP newsgroup(s).