Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Debugging nnmail-split-fancy
Date: Thu, 14 Feb 2019 08:49:41 +0000	[thread overview]
Message-ID: <m2o97eg3fe.fsf@nwalsh.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Hello world,

I use nnmail-split-fancy to route incoming mail to any of a few dozen
(or more) folders. Very occasionally, and with no discernable pattern,
I find a message in the wrong folder. (I have no idea how often this
actually happens, but I only notice very occasionally.)

So, for example, I find a message in “acmecorp.sales” that’s clearly
part of a thread that I’ve been reading in “acmecorp.mac-users” (in
this case). I type “B q” and Gnus (v5.13 btw) says:

  This message would go to archive.2019-02, acmecorp.mac-users

Yeah. Except, it didn’t. It want to “acmecorp.sales”.

Any clue how to debug this?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | If you want to build a ship, don't drum
http://nwalsh.com/            | up the men to gather wood, divide the
                              | work and give orders. Instead, teach
                              | them to yearn for the vast and endless
                              | sea.--A. de Saint-Exupery

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2019-02-14  8:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  8:49 Norman Walsh [this message]
2019-02-14 15:26 ` Gijs Hillenius
2019-02-14 18:16 ` Andreas Schwab
2019-02-19 17:08   ` Norman Walsh
  -- strict thread matches above, loose matches on Subject: below --
1997-07-22  5:56 debugging nnmail-split-fancy Steinar Bang
1997-07-22  6:49 ` Steinar Bang
1997-07-23 17:58   ` Lars Magne Ingebrigtsen
1997-07-23 23:51   ` Mark Eichin

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=m2o97eg3fe.fsf@nwalsh.com \
    --to=ndw@nwalsh.com \
    --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).