From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: Spam despite spam header
Date: Wed, 11 Dec 2013 21:22:33 +0100 [thread overview]
Message-ID: <877gbbt9x2.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87d2l3i46v.fsf@nl106-137-194.student.uu.se>
Emanuel Berg <embe8573@student.uu.se> writes:
>> Well, some system running SpamAssassin inserted those, not the
>> spammers ;-)
> Of course, but it doesn't do much good if the headers are only
> inserted and that will be that, does it?
What else do you propose should(/suppose would) happen?
If the mailserver deleted the email, you would be quite angry in case it
misdetected non-spam as spam...
> You mean like this?
> (setq nnmail-split-methods
> '(("spam" "^X-Spam-Flag: YES")
> ("mail.misc" "") ))
I use fancy splitting, but yes, that looks about right comparing to the
documentation. The examples do not start with ^, so you may want to try
without it, if it doesn't work; see next paragraph.
You can test where an existing email would be split to by pressing B q
when looking at it.
And you can get Gnus to put it where the splitting rules say by pressing
B r.
> I hope I won't get them in a directory called "spam", now!
Why? Wouldn't the point be to separate them out from the non-spam email?
Where would you like them to go? Remember that spam classification isn't
perfect.
> I tested sending a mail to myself with "X-Spam-Flag: YES" as a header,
> but it was delivered to mail.misc, and the header had been removed.
> Perhaps SpamAssassin thought that wasn't spam, and I got overruled.
Yeah, otherwise spammers would just set "X-Spam-Flag: NO" - so usually
mail servers that run SpamAssassin will remove any of those headers,
before adding what the mail server itself thinks.
Best regards,
Adam
--
"[...] but beyond that the Fry household had as much Adam Sjøgren
interest or understanding of sport as a potato has of asjo@koldfront.dk
Riemann's zeta function."
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2013-12-11 20:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:13 Emanuel Berg
2013-12-11 18:11 ` Adam Sjøgren
[not found] ` <mailman.8951.1386785526.10748.info-gnus-english@gnu.org>
2013-12-11 19:21 ` Emanuel Berg
2013-12-11 20:04 ` Dmitrii Kashin
2013-12-11 20:26 ` Adam Sjøgren
2013-12-12 7:14 ` Dmitrii Kashin
2013-12-12 9:22 ` Peter Münster
2013-12-12 15:27 ` Dmitrii Kashin
2013-12-23 17:03 ` Adam Sjøgren
[not found] ` <mailman.10164.1387818251.10748.info-gnus-english@gnu.org>
2013-12-24 19:58 ` Emanuel Berg
[not found] ` <mailman.8965.1386793822.10748.info-gnus-english@gnu.org>
2013-12-11 22:42 ` Emanuel Berg
2013-12-11 20:22 ` Adam Sjøgren [this message]
[not found] ` <mailman.8961.1386792309.10748.info-gnus-english@gnu.org>
2013-12-11 22:33 ` Emanuel Berg
2013-12-12 7:27 ` Dmitrii Kashin
[not found] ` <mailman.8994.1386833301.10748.info-gnus-english@gnu.org>
2013-12-12 20:03 ` Emanuel Berg
[not found] ` <mailman.8964.1386793377.10748.info-gnus-english@gnu.org>
2013-12-11 22:40 ` Emanuel Berg
2013-12-12 23:35 ` Emanuel Berg
2013-12-13 9:13 ` Adam Sjøgren
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=877gbbt9x2.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).