Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Spam despite spam header
Date: Wed, 11 Dec 2013 23:40:57 +0100	[thread overview]
Message-ID: <87vbyvggdp.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: <mailman.8964.1386793377.10748.info-gnus-english@gnu.org>

asjo@koldfront.dk (Adam Sjøgren) writes:

>> 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?

I'd like them to be deleted. But I can do that manually
once in a while if it comes to that. To have the spam
separated from instead of *in* mail.misc is a huge
improvement.

> If the mailserver deleted the email, you would be
> quite angry in case it misdetected non-spam as
> spam...

Yeah, but I don't think I'll look into the "spam"
group/directory to doublecheck anyway, so is there a
difference in practice?

>> (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

Isn't that a regexp special char for "start of line"?

> 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.

OK, I'll test that.

>> 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.

Come to think of it, I guess I could keep them.

>> 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.

Ha ha ha, Spam: NO :) Yes, that makes sense.

-- 
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united:  http://user.it.uu.se/~embe8573
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2013-12-11 22:40 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
     [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 [this message]
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=87vbyvggdp.fsf@nl106-137-194.student.uu.se \
    --to=embe8573@student.uu.se \
    --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).