From: Antonio Carzaniga <antonio.carzaniga@usi.ch>
To: <info-gnus-english@gnu.org>
Subject: tracking message ids with nnmaildir?
Date: Thu, 24 Dec 2015 12:19:40 +0100 [thread overview]
Message-ID: <87twn8um9f.fsf@usi.ch> (raw)
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.
I have trouble tracking message ids for messages stored in Maildir
groups (e.g., to automatically split follow-up messages to the same
group). In particular, neither the nnmail cache nor the registry would
pick up the ids of messages spooled to a Maildir group through Gcc.
In trying to figure this out, I noticed that nnmaildir does not track
message ids at all, whereas all other mail back ends track every message
they accept through nnmail-cache-insert, which is where the registry
hooks into. This looks like a bug, no? Am I missing something? How
can I track messages automatically spooled to Maildir groups?
Thanks a lot for your help!
-Antonio
reply other threads:[~2015-12-24 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87twn8um9f.fsf@usi.ch \
--to=antonio.carzaniga@usi.ch \
--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).