From: "Bjørn Mork" <bjorn@mork.no>
To: ding@gnus.org
Subject: Re: nnimap, marks and agent leftovers
Date: Wed, 25 May 2011 13:39:27 +0200 [thread overview]
Message-ID: <874o4jxb4g.fsf@nemi.mork.no> (raw)
In-Reply-To: <87d3j7xbob.fsf@nemi.mork.no>
Bjørn Mork <bjorn@mork.no> writes:
> When opening
> the connections again, I noticed a large number of new mails in all
> groups and immediately thought that all my marks had disappeared. But
> that was not what happend. The marks had been reset to the last time I
> 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).
Sorry, as usual I jumped too quickly to a conclusion. Looks like
whatever flags Gnus were using never were pushed to the servers.
Reopening the connections just weren't enough for Gnus to refresh its
local copy. But after restarting Gnus, everything were back to normal.
Pfew!
Bjørn
next prev parent reply other threads:[~2011-05-25 11: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 [this message]
2011-05-25 17:39 ` Steinar Bang
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=874o4jxb4g.fsf@nemi.mork.no \
--to=bjorn@mork.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).