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: Fancy splitting and spam detection
Date: Mon, 24 Aug 2015 21:30:55 +0200	[thread overview]
Message-ID: <87lhd0lc0g.fsf@nl106-137-147.student.uu.se> (raw)
In-Reply-To: <87h9nooqvp.fsf@free.fr>

Julien Cubizolles <j.cubizolles@free.fr> writes:

> Thanks for this example, but I see that you don't
> use the spam-split fancy split, which is the one
> misbehaving in my setup.

Yeah, I don't use that so I can't help you as there
are so many things that can go wrong, almost the only
things you can trust are those you yourself are using
year in, year out. And sometimes you can't trust even
them which is when I apply severe punishment.

-- 
underground experts united
http://user.it.uu.se/~embe8573



  reply	other threads:[~2015-08-24 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  7:38 Julien Cubizolles
2015-08-21 19:15 ` Emanuel Berg
2015-08-24 11:41   ` Julien Cubizolles
2015-08-24 19:30     ` Emanuel Berg [this message]
2015-08-26 20:58 ` Julien Cubizolles

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=87lhd0lc0g.fsf@nl106-137-147.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).