From: notbob <notbob@nothome.com>
To: info-gnus-english@gnu.org
Subject: Re: Is there a simple way to set up spam filtering?
Date: 3 Jan 2016 16:49:12 GMT [thread overview]
Message-ID: <det1o8Fcrg3U1@mid.individual.net> (raw)
In-Reply-To: <mailman.1601.1451839085.843.info-gnus-english@gnu.org>
On 2016-01-03, Sivaram Neelakantan <shanks.n@gmail.com> wrote:
> Seriously, the docs chapter on spam is hard. Too hard to even set it
> up. And that's not even coming to the fancy splitting part.
I'm not sure why anyone still wants to use the CLI to read emails.
Ima CLI and emacs junkie, but still use Seamonkey to read incoming
email cuz of all the graphics (mpg, gifs, etc) friends include in
emails to me. Seamonkey --and prolly a lotta other gui email
clients-- do all the spam filtering you mention.
nb
next parent reply other threads:[~2016-01-03 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1601.1451839085.843.info-gnus-english@gnu.org>
2016-01-03 16:49 ` notbob [this message]
2016-01-03 7:44 Sivaram Neelakantan
2016-01-03 18:04 ` Teemu Likonen
2016-01-30 18:34 ` Saša Janiška
2016-01-30 19:16 ` Teemu Likonen
2016-01-30 20:23 ` Saša Janiška
2016-01-30 21:00 ` Teemu Likonen
2017-04-03 7:39 ` Saša Janiška
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=det1o8Fcrg3U1@mid.individual.net \
--to=notbob@nothome.com \
--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).