From: Xavier Maillard <xavier@maillard.im>
To: Bob Proulx <bob@proulx.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: [Rmail] Fighting spam
Date: Tue, 5 Jun 2018 06:37:26 +0200 [thread overview]
Message-ID: <201806050437.w554bQIr018935@localhost.localdomain> (raw)
In-Reply-To: <20180604111209301834037@bob.proulx.com> (message from Bob Proulx on Mon, 4 Jun 2018 11:19:22 -0600)
Hello Bob,
> Date: Mon, 4 Jun 2018 11:19:22 -0600
> From: Bob Proulx <bob@proulx.com>
>
> Xavier Maillard wrote:
> > with latest Rmail development, what is the simplest method to protect
> > myself agaisnt spam ? THere are a few messages that are auto-magicallly
> > labeled with a « spam » keyword but I can't find why it happens :)
> >
> > I need a way ton instruct this protector with other material to get him
> > even better.
>
> IIRC the Rmail rules are able to classify the reading and display of
> both non-spam and spam messages but is not a spam classification
> engine itself. For that you would probably look to using SpamAssassin
> or another spam classification engine such as BogoFilter or other or
> some combination of all of the above. I am currently using a pipeline
> through bogofilter and spamassassin. However even better is to avoid
> receiving the spam in the first place by using a DNSBL such as the Xen
> list from Spamhaus. Best is combined arms tactics using a combination
> of available techniques.
Got it.
I am not getting that much spam these days but having some tools and
techniques to fight it when a spam wave comes by may be useful.
> You didn't say how email is getting delivered to your system.
For a couple of years I was geting to my mail through IMAP servers but
I was not satisfied having my e-mails stored and synced on every devices I was
using. I have now switched back to POP and a sole copy on 1 computer and only 1.
I have defined `rmail-primary-inbox-alist' to '("po:...").
There is no other tool in the workflow (I got rid of
fetchmail/getmail, procmail and the like).
Regards
--
Xavier Maillard
e/j:xavier@maillard.im w:www.maillard.im
m: 06 52 18 63 43
GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B
next prev parent reply other threads:[~2018-06-05 4:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 13:01 [Rmail] Fighting spam Xavier Maillard
2018-05-30 13:51 ` Jude DaShiell
2018-05-30 17:10 ` Xavier Maillard
2018-05-30 17:39 ` Jude DaShiell
2018-06-01 0:38 ` Eric Brown
[not found] ` <mailman.808.1527688307.1292.help-gnu-emacs@gnu.org>
2018-05-31 15:02 ` James K. Lowden
2018-05-31 18:48 ` Emanuel Berg
2018-05-31 20:01 ` Xavier Maillard
[not found] ` <mailman.879.1527796902.1292.help-gnu-emacs@gnu.org>
2018-05-31 21:29 ` Emanuel Berg
2018-06-01 6:40 ` Xavier Maillard
[not found] ` <mailman.903.1527835215.1292.help-gnu-emacs@gnu.org>
2018-06-01 10:12 ` Emanuel Berg
2018-06-01 0:47 ` Eric Brown
2018-06-04 17:19 ` Bob Proulx
2018-06-05 4:37 ` Xavier Maillard [this message]
2018-06-06 5:35 ` Bob Proulx
2018-06-08 4:42 ` Xavier Maillard
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=201806050437.w554bQIr018935@localhost.localdomain \
--to=xavier@maillard.im \
--cc=bob@proulx.com \
--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).