From: Steinar Bang <sb@metis.no>
Subject: Re: score rule for stopping fdjg.com spam
Date: 19 Aug 1999 12:29:30 +0200 [thread overview]
Message-ID: <wh4shwgj1x.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Stainless Steel Rat's message of "17 Aug 1999 16:03:58 -0400"
>>>>> Stainless Steel Rat <ratinox@peorth.gweep.net>:
> What I do is split known mailing lists first, then a list of known
> spam domains (all of which appear to be out of business these days
> :), mail from daemon and cron, mail addressed specifically to me,
> and finally everything else into the spam bucket. These days more
> spam slips through into my regular mail folder, but moving it with
> `B m' is easy.
I have the same approach.
But with `B m', note the rendering annoyance that prompted the start
of the thread with the Subject
article selected when doing B m
However, I was thinking of USENET, rather than mail for this
particular score rule.
prev parent reply other threads:[~1999-08-19 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-17 13:04 Steinar Bang
1999-08-17 20:03 ` Stainless Steel Rat
1999-08-19 10:29 ` Steinar Bang [this message]
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=wh4shwgj1x.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).