From: Edvard Majakari <edvard.majakari@pampltd.com>
Subject: Splitting into Maildir folder
Date: 03 Jun 2002 11:48:11 +0300 [thread overview]
Message-ID: <871ybog33o.fsf@samuel.pampltd.com> (raw)
Greetings!
Recently I ran into SpamAssassin. Having used that for some time I quickly
became very fond of that piece of software. It seems to identify spam
quite easily, and so I created a procmail script that uses SpamAssassin
according to instructions given.
Now, with procmail, I'm able to use two alternative methods for splitting
mail. I can put all incoming spam into mbox file, or Maildir directory (of
course, /dev/null is possible, but SpamAssassin may sometimes have
positive false results. So I use mbox of Maildir.
Of course, I could just filter all mail via SpamAssassin and make Gnus
identify spam by headers that SpamAssassin inserts, but I don't want to
see first that hey, I've got ten new messages only to find that 9 out of
10 are spam.
The problem is, how do I create a group in Gnus that is actually in mbox
or Maildir format? I'm quite sure Gnus is able to do this, I only don't
know how :)
FWIW, I created two simple zsh functions to first identify new spam
domains and second script to insert those new domains to Postfix's
header_checks file (that is able to handle regexps) so that at least in
theory, I should never receive spam from the same domain twice. I can send
those scripts and/or domain blacklists gathered so far with SpamAssassin
if anybody's interested.
--
# Edvard
By this shall all men know that ye are my disciples, if ye have love one
to another -- John 13:35
next reply other threads:[~2002-06-03 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 8:48 Edvard Majakari [this message]
[not found] ` <vafn0uc90hz.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <87vg8zjrf2.fsf@samuel.pampltd.com>
2002-06-04 10:47 ` Kai Großjohann
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=871ybog33o.fsf@samuel.pampltd.com \
--to=edvard.majakari@pampltd.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 NNTP newsgroup(s).