From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: nnimap, marks and agent leftovers
Date: Wed, 25 May 2011 19:39:18 +0200 [thread overview]
Message-ID: <87oc2qznll.fsf@dod.no> (raw)
In-Reply-To: <87d3j7xbob.fsf@nemi.mork.no>
>>>>> Bjørn Mork <bjorn@mork.no>:
> I have learned that nnimap and agent don't mix. It makes all sorts of
> weird things happening, and sometimes hides mail to the degree that I
> haven't yet found a way to display it using Gnus with agent.
What happens, are:
- Sometimes the wrong article is cached
- Sometimes a piece of NOV data is cached instead of the article
Unfortunately I haven't been able to reproduce _when_ this happens.
I've tried debugging the agent caching in nnimap with the new nnimap
backend (the attempts are somewhere in this group).
> So I don't use agent for my nnimap servers anymore.
Note: all of these issues appeared when agent met the new nnimap backend
(which I love for its speed)
I think maybe the agent should be a candidate for a full rewrite....?
Not something I can step up to volunteer for myself, unfortunately.
[snip!]
> used agent on these servers! Looks like Gnus found the ancient data
> under ~/News/agent/nnimap/ and used it, even though the servers were
> not agentized (they are not listed in ~/News/agent/lib/servers).
This has always been the case, I think. Not something that appeared with
the new nnimap backend.
> So my advice is: Don't just disabe agent on nnimap servers, but be sure
> to delete/move all data from ~/News/agent/nnimap/ as well!
Quite possibly.
Note that when the agent caches the wrong stuff, deleting the wrongly
cached article under ~/News/agent/nnimap/ is enough to fix the issue
with strange behaviour.
Having to do so at all, is kind of annoying, though...
prev parent reply other threads:[~2011-05-25 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 11:27 Bjørn Mork
2011-05-25 11:39 ` Bjørn Mork
2011-05-25 17:39 ` Steinar Bang [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=87oc2qznll.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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).