From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: nnmail-cache-ignore-groups question
Date: Tue, 13 Apr 2004 20:26:43 +0900 [thread overview]
Message-ID: <b9yad1gyv7w.fsf@jpl.org> (raw)
In-Reply-To: <7cfzb8qkqn.fsf@nature.tsukuba.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 1802 bytes --]
>>>>> In <7cfzb8qkqn.fsf@nature.tsukuba.ac.jp> Hiroshi Fujishima wrote:
> Hi,
> I am using Gnus with follwing setting.
> gnus-select-method's value is (nnml "")
> gnus-message-archive-method's value is "archive" <- which is default value
> gnus-message-archive-group's value is "backup"
> If I post a message to mailing list, the message which is delivered
> grom mailing list server has Gnus-Warning: field as below. Because,
> the posted message Gcc-ed in nnfolder+archive:backup.
> Gnus-Warning: This is a duplicate of message <7cptad9pid.fsf@nature.tsukuba.ac.jp>
It is because those message-ids have been stored in the
nnmail-message-id-cache-file. I think it is useless to cache
ids for archive articles. If it is true, the problem will be
able to be solved by some way (currently I don't have a concrete
idea).
> Since I don't like Gnus records Gcc-ed message in
> nnfolder+archive:backup, I refer info as below.
> (info "(gnus)Fancy Mail Splitting")
>| Also see the variable `nnmail-cache-ignore-groups' if you don't want
>| certain groups to be recorded in the cache. For example, if all
>| outgoing messages are written to an "outgoing" group, you could set
>| `nnmail-cache-ignore-groups' to match that group name. Otherwise,
>| answers to all your messages would end up in the "outgoing" group.
> So I add next configuration, but Gnus still recording message in
> nnfolder+archive:backup. why?
> (setq nnmail-cache-ignore-groups "^nnfolder\\+archive:backup$")
Because nnfolder is not your primary mail back end which is not
examined by nnmail-cache-ignore-groups. See nnmail-cache-insert.
Isn't it a bug? I don't understand why it puts non-primary mail
back ends out. Although I have no confidence, I made a patch for
it. I appreciate someone examining it closely.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 844 bytes --]
--- nnmail.el~ 2004-03-05 10:50:21 +0000
+++ nnmail.el 2004-04-13 11:25:16 +0000
@@ -1570,15 +1570,16 @@
(save-excursion
(set-buffer nnmail-cache-buffer)
(goto-char (point-max))
- (if (and grp (not (string= "" grp))
- (gnus-methods-equal-p gnus-command-method
- (nnmail-cache-primary-mail-backend)))
+ (if (and grp (not (string= "" grp)))
(let ((regexp (if (consp nnmail-cache-ignore-groups)
(mapconcat 'identity nnmail-cache-ignore-groups
"\\|")
nnmail-cache-ignore-groups)))
(unless (and regexp (string-match regexp grp))
- (insert id "\t" grp "\n")))
+ (if (gnus-methods-equal-p gnus-command-method
+ (nnmail-cache-primary-mail-backend))
+ (insert id "\t" grp "\n")
+ (insert id "\n"))))
(insert id "\n"))))))
(defun nnmail-cache-primary-mail-backend ()
next prev parent reply other threads:[~2004-04-13 11:26 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 [this message]
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
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=b9yad1gyv7w.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).