From: Enrico Schumann <es@enricoschumann.net>
To: info-gnus-english@gnu.org
Subject: Re: newbie spam filtering with gnus
Date: Thu, 02 Apr 2015 20:53:56 +0200 [thread overview]
Message-ID: <874moypdiz.fsf@enricoschumann.net> (raw)
In-Reply-To: <87zj6r8npr.fsf@debian.uxu> (Emanuel Berg's message of "Thu, 02 Apr 2015 00:53:36 +0200")
On Thu, 02 Apr 2015, Emanuel Berg <embe8573@student.uu.se> writes:
> Enrico Schumann <es@enricoschumann.net> writes:
>
>> 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:
>
> I also use POP and I don't get that many spams: those
> I get I am able to KILL which is helpful as they do
> come back [1].
>
> Are you saying POP compared to IMAP is more
> susceptible to spam? Those are protocols that deal
> with the client fetch of mail from the server.
>
> IMAP is more advanced, and so more complicated, but
> I always thought them to be mere protocols - defining
> the message syntax as well as the order and meaning of
> exchanges (e.g., handshakes and so on) in different
> situations, with no implications as to anti-spam.
>
> Or do you mean that particular methods, e.g.
> SpamAssassin which you mention, only works with POP?
>
> If you get a lot of spam, perhaps it is easier and
> more efficient to just get a new e-mail address which
> is a bit unintuitive and which you never submit to web
> services or publish verbatim on pages or in mails?
>
> For example, I always mention my address as
>
> embe8573 AT&T student DOS uu DOS se
>
> I don't know if that is clever but considering I have
> a home page with that handle and that all addresses
> are constructed according to that pattern, and besides
> the amount of communication and the width of my public
> interface, I'd say something must be working as again,
> I don't get much spam.
>
> [1] http://user.it.uu.se/~embe8573/conf/emacs-init/gnus/lamer.el
The original question was: what is an easy way to handle spam
messages in Gnus?
I pointed the OP to one relatively-easy way, which does not
require much configuration in Gnus, as described in the manual.
I specifically mentioned POP because the OP said he used POP, and
the configuration may differ for an IMAP setup.
--
Enrico Schumann
Lucerne, Switzerland
http://enricoschumann.net
prev parent reply other threads:[~2015-04-02 18:53 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
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 [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=874moypdiz.fsf@enricoschumann.net \
--to=es@enricoschumann.net \
--cc=info-gnus-english@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 NNTP newsgroup(s).