From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: nnmail-cache-ignore-groups question
Date: Thu, 15 Apr 2004 15:43:15 +0900 [thread overview]
Message-ID: <b9yk70hivwc.fsf@jpl.org> (raw)
In-Reply-To: <7csmf5c0yj.fsf@nature.tsukuba.ac.jp>
>>>>> In <7csmf5c0yj.fsf@nature.tsukuba.ac.jp> Hiroshi Fujishima wrote:
>> I also got to have confidence that it should be fixed.
>> Fujishima-san, how about the Gnus CVS head?
> Thanks! I tried the Gnus CVS head. But it still exists Gnus-Warning
> field. I watched ~/.nnmail-cache file and I notice if recoreded
> message is Gcc-ed, the 2nd field does not exist. Is this bug?
Oops! I completely misunderstood. I've reverted that bogus
change. The problem occurs only by setting
nnmail-cache-accepted-message-ids as non-nil (see the "Fancy
Mail Splitting" info node), and isn't related to the kind of
mail back end.
>>>>> In <7cfzb8qkqn.fsf@nature.tsukuba.ac.jp> Hiroshi Fujishima wrote:
> (setq nnmail-cache-ignore-groups "^nnfolder\\+archive:backup$")
You need to exclude the method name in the regexp as:
(setq nnmail-cache-ignore-groups "^backup$")
The value can be replaced with "\\`backup\\'".
However, users who have set the gcc-self group parameter as t
cannot use such a way in order to avoid Gnus-Warnings, because
the archive group name will change variously.
In addition, I noticed there is another problem. If
nnmail-cache-accepted-message-ids is non-nil, a strange
Message-ID is stored in the nnmail-message-id-cache-file
whenever I begin to write a mail. It is produced when the
nndraft back end makes a draft file for the nndraft:drafts
group. I'm not actually in trouble since I haven't set
nnmail-cache-accepted-message-ids as non-nil, though.
--
Katsumi Yamaoka <yamaoka@jpl.org>
prev parent reply other threads:[~2004-04-15 6:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 9:40 Hiroshi Fujishima
2004-04-13 11:26 ` Katsumi Yamaoka
2004-04-14 6:59 ` Kai Grossjohann
2004-04-14 7:25 ` Katsumi Yamaoka
2004-04-15 4:35 ` Hiroshi Fujishima
2004-04-15 6:43 ` Katsumi Yamaoka [this message]
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=b9yk70hivwc.fsf@jpl.org \
--to=yamaoka@jpl.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).