From: Greg Troxel <gdt@work.lexort.com>
To: Michal <rabbit50@tenbit.pl>
Cc: gnus-ding mailing list <ding@lists.math.uh.edu>
Subject: Re: no such article question
Date: Sun, 06 Jul 2008 10:21:19 -0400 [thread overview]
Message-ID: <smuod5bhz4w.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <lziqvkuv76.fsf@tenbit.pl> (Michal's message of "Sat, 05 Jul 2008 18:55:41 +0200")
Michal <rabbit50@tenbit.pl> writes:
> My nnimap INBOX contains some articles which I can neither access nor
> delete. For example, when I want to delete such article, I get the
> following message in *Mssages*:
> No such article 7814 in INBOX: nil
> No such article (may have expired or been canceled)
>
> I am guessing that this situation is because I access my INBOX both
> from work and from home ( in both the places I use gnus). Gnus
> probably caches article header somehow. Can You tell me how can I get
> rid of these headers. Some synchronization between gnus and imap
> server needed?
I have a different problem, which is that on one imap server, but not
the other, articles in INBOX show up again after being deleted. I work
around this by 'rm -rf ~/News/agent'. Both setups are NetBSD/i386
4_STABLE with recent dovecot 1.0.x, emacs 22.1, and gnus trunk. I
also access both servers with Apple Mail.app, iphone, and thunderbird.
So, I think your problem might be that the local gnus has a cache about
metadata for the article and is showing it, but really you've deleted
it, so when you select it fetching fails.
I think that caching information about imap is basically too dnagerous,
at least without somehow validating it. I've tried to turn it off, but
haven't managed to:
(setq gnus-secondary-select-methods
'((nnimap "[redacted]"
(nnimap-address "[redacted]")
(nnimap-port 993)
(nnimap-stream ssl)
(nnimap-authenticator login)
(nnir-search-engine imap)
(gnus-agent-cache nil)
)))
next prev parent reply other threads:[~2008-07-06 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 16:55 Michal
2008-07-06 6:32 ` Ralf Angeli
2008-07-06 14:21 ` Greg Troxel [this message]
2008-07-06 15:18 ` Michal
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=smuod5bhz4w.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--cc=ding@lists.math.uh.edu \
--cc=rabbit50@tenbit.pl \
/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).