From: Bastien <bzg@altern.org>
To: Don Saklad <dsaklad@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: For nonprogrammers maybe dyslexic, maybe ADD, how can spamassassin headers be filtered so that all or most of the spam messages, rather than mixed in with email, all or most go to a separate email file that can be checked for any false positives?
Date: Sat, 08 Mar 2008 12:37:55 +0000 [thread overview]
Message-ID: <87r6el5r30.fsf@bzg.ath.cx> (raw)
In-Reply-To: <E1JXxtN-0002k5-Pi@fencepost.gnu.org> (Don Saklad's message of "Sat, 08 Mar 2008 07:11:09 -0500")
Don Saklad <dsaklad@gnu.org> writes:
> For nonprogrammers maybe dyslexic, or maybe ADD, how can spamassassin
> headers be filtered so that all or most of the spam messages, rather
> than mixed in with email, all or most go to a separate email file that
> can be checked for any false positives?... RMAIL in EMACS
> and from time to time mutt are used for email
This list is about Emacs and I don't know mutt.
For storing Rmail message in a folder, look at
`rmail-automatic-folder-directives'.
C-h v rmail-automatic-folder-directives REG
For using spam filters with Rmail, put this in your configuration:
(require 'rmail-spam-filter)
(setq rmail-use-spam-filter t)
Then you need to set `rsf-definitions-alist':
M-x customize-variable RET rsf-definitions-alist RET
Edit it to deal with spamassassin headers.
PS: when asking such questions it is a good idea to show what you
tried and what was the problem. Otherwise people might think you
didn't even try (which I don't think.)
--
Bastien
next prev parent reply other threads:[~2008-03-08 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 12:11 For nonprogrammers maybe dyslexic, maybe ADD, how can spamassassin headers be filtered so that all or most of the spam messages, rather than mixed in with email, all or most go to a separate email file that can be checked for any false positives? Don Saklad
2008-03-08 12:37 ` Bastien [this message]
2008-03-10 15:04 ` Joel J. Adamson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r6el5r30.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=dsaklad@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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).