Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: Debugging split errors
Date: Fri, 12 Jul 2019 16:14:18 -0500	[thread overview]
Message-ID: <m2sgrbvtud.fsf@nwalsh.com> (raw)

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

Hi,

I think I may have mentioned issues with splitting once before. I
recently created a new group and setup several nnmail-split-fancy
rules for it:

  (setq nnmail-split-fancy
    …
             (from "Confluence-Admin@.*acmecorp\\.com" "acmecorp.noreply")
             (from "noreply@acmecorp\\.com" "acmecorp.noreply")
             (from "donotreply-jenkins@acmecorp\\.com" "acmecorp.noreply")
             (from "donotreply@acmecorp\\.com" "acmecorp.noreply")
             (from "bugtrack@acmecorp\\.com" "acmecorp.noreply")
     …)

Those are the *only* rules for that group. And yet several times a
week, perhaps a day, messages get misfiled in that group. When I go
to the misfiled message and ask where this message would be filed (“B
q”), I get back the answers I expect.

Are there any debugging or trace flags I can turn on to get some
feedback about what happened? Are there any caches I should blow away
to see if that fixes the problem? It’s more than inconvenient because
I’ve failed to notice a couple of messages from my boss
(unsurprisingly, I’m not in the habit of reading this group!).

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Simplicity is always a virtue.--Edward
http://nwalsh.com/            | Abbey

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

             reply	other threads:[~2019-07-12 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 21:14 Norman Walsh [this message]
2019-07-13 13:13 ` Lars Ingebrigtsen
2019-07-13 13:24   ` Lars Ingebrigtsen
2019-07-13 17:15     ` Eric S Fraga

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=m2sgrbvtud.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).