Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Totally incorrect splitting
Date: Tue, 10 Dec 2013 18:07:32 +0100	[thread overview]
Message-ID: <upzc7gbcy6qz.fsf@dod.no> (raw)
In-Reply-To: <m2bo0ou0rs.fsf@nwalsh.com>

>>>>> Norman Walsh <ndw@nwalsh.com>:

> I'm not sure how to debug this. I'm running Ma Gnus 0.8 (maybe I
> should upgrade?) on GNU Emacs 24.3.1. I'm using fancy splitting.

With what backend?

> Occasionally, messages go in completely incorrect groups.

> Curiously, when I run 'B q' on them, they list the correct groups as
> the targets.

> I've got enough groups and enough email that I find this a bit
> frightening.

FWIW I dealt with heaps of mailing lists by getting the mailing lists
subscribed to gmane.

(Granted with closed(ish) working group mailing lists, that is not an
option...)




  reply	other threads:[~2013-12-10 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 16:30 Norman Walsh
2013-12-10 17:07 ` Steinar Bang [this message]
2013-12-10 18:02   ` Norman Walsh
2013-12-13 14:22     ` Ted Zlatanov
2013-12-13 19:07       ` Norman Walsh
2014-01-30 14:58       ` Norman Walsh
2014-02-01 10:06         ` Ted Zlatanov

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=upzc7gbcy6qz.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.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).