From: Raymond Scholz <ray-2004@zonix.de>
Subject: nnimap+agent+registry -> ghost articles
Date: Wed, 07 Jul 2004 23:10:41 +0200 [thread overview]
Message-ID: <gegg.87hdsjfrqm@hush.zonix.de> (raw)
Hi,
I'm using nnimap with the gnus registry (splitting with parent) and
the agent for caching overviews to increase speed. Most of my mail is
split by maildrop into Maildirs on the IMAP server. Anything else is
put into the IMAP INBOX which will then be split by Gnus using the
registry information. Some articles end up in INBOX since the
registry has no information on their parents. These articles drive
Gnus nuts.
;; registry setup
(gnus-registry-initialize)
(setq gnus-registry-max-entries 20000)
(setq gnus-registry-use-long-group-names t)
(setq gnus-registry-unfollowed-groups
'("delayed"
"drafts"
"queue"
"sent\\.mail"
"sent\\.news"
"^nnrss:"
"^nntp:"
))
;; nnimap + splitting setup
(setq nnimap-split-rule 'nnimap-split-fancy)
(setq nnimap-split-fancy
'(|
(: gnus-registry-split-fancy-with-parent)
"INBOX"))
(setq nnimap-split-inbox '("INBOX"))
(setq nnimap-split-predicate "UNDELETED")
(setq nnimap-split-crosspost nil)
(setq gnus-use-cache t)
Gnus from CVS, just a few minutes ago.
To reproduce the ghost articles I sent myself an email to
rscholz@localhost which ends up in INBOX after hitting `g'.
~/News/agent/nnimap/unnamed/INBOX/.overview contains a line:
4419 test - 02 Raymond Scholz <rscholz@zonix.de> Wed, 07 Jul 2004 22:11:25 +0200 <.877jtfmvbm@hush.zonix.de> 1008 4 Xref: hush.zonix.de INBOX:4409 To: rscholz@localhost Content-Type: text/plain; charset=iso-8859-1
and ~/.gnus.registry.eld a line
("<.877jtfmvbm@hush.zonix.de>" ((mtime 16620 22872 767890)) "nnimap:INBOX")
So far, so good.
Now I hit `g' again. The article in INBOX is passed to the Gnus
splitting process again, which shouldn't hurt. But the article count
in the Group buffer indicates two unread articles in INBOX now.
Entering the group shows the duplicated articles which can both be
displayed.
And ~/News/agent/nnimap/unnamed/INBOX/.overview contains
4419 test - 02 Raymond Scholz <rscholz@zonix.de> Wed, 07 Jul 2004 22:11:25 +0200 <.877jtfmvbm@hush.zonix.de> 1008 4 Xref: hush.zonix.de INBOX:4409 To: rscholz@localhost Content-Type: text/plain; charset=iso-8859-1
4420 test - 02 Raymond Scholz <rscholz@zonix.de> Wed, 07 Jul 2004 22:11:25 +0200 <.877jtfmvbm@hush.zonix.de> 1008 4 Xref: hush.zonix.de INBOX:4409 To: rscholz@localhost Content-Type: text/plain; charset=iso-8859-1
and ~/.gnus.registry.eld ends with
("<.877jtfmvbm@hush.zonix.de>" ((mtime 16620 22872 767890)) "nnimap:INBOX" "nnimap:INBOX")
Subsequent invocations of `gnus-group-get-new-news' add more lines in
the overview file and more entries for the respective message ID in
the registry.
The real pain starts when I delete the article or move it to another
folder. Deletion of ghost articles doesn't work ("Couldn't delete
articles (4420 4421)") and I usually end up with rm -rf
~/News/agent/nnimap/ and a restart of Gnus.
Cheers, Ray
--
Hfr fgebat rapelcgvba!
next reply other threads:[~2004-07-07 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 21:10 Raymond Scholz [this message]
2004-07-16 17:02 ` Ted Zlatanov
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=gegg.87hdsjfrqm@hush.zonix.de \
--to=ray-2004@zonix.de \
--cc=rscholz@zonix.de \
/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).