From: Enrico Schumann <es@enricoschumann.net>
To: Steven Arntson <steven@stevenarntson.com>
Cc: info-gnus-english@gnu.org
Subject: Re: newbie spam filtering with gnus
Date: Thu, 02 Apr 2015 20:48:34 +0200 [thread overview]
Message-ID: <878ueapdrx.fsf@enricoschumann.net> (raw)
In-Reply-To: <87pp7msc3b.fsf@stevenarntson.com> (Steven Arntson's message of "Thu, 02 Apr 2015 09:56:40 -0700")
On Thu, 02 Apr 2015, Steven Arntson <steven@stevenarntson.com> writes:
> Enrico Schumann <es@enricoschumann.net> writes:
>
>> On Wed, 01 Apr 2015, Steven Arntson <steven@stevenarntson.com> writes:
>>> Is there any sort of simple "starter kit" for newcomers getting going on
>>> filtering out spam?
>>>
>>> Thank you for any advice aimed at a not-very-technical person!
>>> -steven
>>>
>>
>> When I used POP some years ago, what worked out of the box for me was
>> using SpamAssassin as an external programme (spamc) during splitting, as
>> described in the manual:
>>
>> http://www.gnu.org/software/emacs/manual/html_node/gnus/SpamAssassin.html
>>
>> To quote from the relevant section:
>>
>> ,----
>> | [A] solution is to call the external tools during splitting. Example
>> | fancy split method:
>> |
>> | (setq nnmail-split-fancy '(| (: kevin-spamassassin)
>> | ...))
>> |
>> | (defun kevin-spamassassin ()
>> | (save-excursion
>> | (save-restriction
>> | (widen)
>> | (if (eq 1 (call-process-region (point-min) (point-max)
>> | "spamc" nil nil nil "-c"))
>> | "spam"))))
>> `----
>>
>>
>>
>> Kind regards,
>> Enrico
>
> Thank you for this---I've read, or tried to, the page you've referenced,
> though it's far over my head. I put the code above into my .gnus.el
> file. However, I really am in the dark! For instance, is the `...' in
> the second line of that code an ellipsis telling me to put my own items
> in there, or is it active code that should be preserved? Do I really use
> "kevin-spamassassin" or am I to change that to something that has to do
> with my own system? At present, the code isn't doing anything as far as
> I can tell.
[Caveat: I cannot test what I describe below since I do not use this
setup any more.]
First, make sure that SpamAssassin is installed on your system. For
instance, open a terminal and type 'spamc -V', and it should tell you
the installed version.
Then, in your .gnus.el, add something like this:
(setq nnmail-split-methods 'nnmail-split-fancy
nnmail-split-fancy '(| (: kevin-spamassassin)
"catchall.inbox"))
In which "catchall.inbox" is the group to which all non-spam mails go.
Also add the function kevin-spamassassin, as given in the manual (and
above). The "spam" in the last line of the function is the group to
which spam emails go.
Good luck.
[And you may rename 'kevin-spamassassin' as you wish, as long as you
also use that name with 'nnmail-split-fancy'.]
--
Enrico Schumann
Lucerne, Switzerland
http://enricoschumann.net
next prev parent reply other threads:[~2015-04-02 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 2:31 Steven Arntson
2015-04-01 13:38 ` Enrico Schumann
2015-04-02 16:56 ` Steven Arntson
2015-04-02 18:48 ` Enrico Schumann [this message]
2015-04-02 21:54 ` Steven Arntson
2015-04-03 10:08 ` Enrico Schumann
2015-04-03 19:51 ` Steven Arntson
2015-04-04 5:59 ` Enrico Schumann
2015-04-04 16:55 ` Steven Arntson
2015-04-04 17:08 ` Steven Arntson
2015-04-04 20:20 ` Enrico Schumann
[not found] ` <mailman.3137.1427899913.31049.info-gnus-english@gnu.org>
2015-04-01 22:53 ` Emanuel Berg
2015-04-02 18:53 ` Enrico Schumann
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=878ueapdrx.fsf@enricoschumann.net \
--to=es@enricoschumann.net \
--cc=info-gnus-english@gnu.org \
--cc=steven@stevenarntson.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).