From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: Is *anyone* else loosing expiry marks in nnimap buffers?
Date: Wed, 02 Jul 2003 16:24:24 -0400 [thread overview]
Message-ID: <u8zznjwhe2v.fsf@verizon.net> (raw)
In-Reply-To: <sdk7b0yaa7.fsf@wanderer.hardakers.net> (Wes Hardaker's message of "Wed, 02 Jul 2003 12:54:24 -0700")
>>>>> On Wed, 02 Jul 2003 12:54:24 -0700, Wes Hardaker <wes@hardakers.net> said:
>>>>> On Wed, 02 Jul 2003 11:18:47 -0400, David S Goldberg
>>>>> <david.goldberg6@verizon.net> said:
David> But are the messages actually there on the server? I've found two
David> problems that might be related to what you're seeing. The easiest to
David> deal with is when the agent overview gets out of sync and reports the
David> existence of messages that are gone.
> I suspect that actually might be the problem. I'll try regenerating
> the .overview file next time. I actually thought this problem had
> been fixed as well (in fact, a long time ago I reported that the
> .overview files got to be huge because duplicate information was being
> entered into them, but that may have been a separate bug because that
> was fixed by Lars)
I still get warnings during expiry that my overview either has
information about a non-existing message or is missing info about an
existing one and the recommendation to run gnus-agent-regenerate. So
the bug may not be fixed, but there's code added to detect it.
David> The more difficult problem is when messages expired from the
David> server don't get expired from the agent. This might have been
David> fixed, though. About a month or two ago I got fed up, deleted
David> my entire agent hierarchy and started afresh and I haven't had
David> that problem since.
> Thats the thing. I thought it was supposed to have been fixed too.
I think this may be fixed since I've been free of it for so long (used
to happen pretty regularly). However, the fix may only be good for
dealing with new messages. If you have messages in your agent that
were downloaded before the fix was committed they may not be dealt
with. I've had that issue with several bugs I reported in the agent.
I went nuts trying to figure out why the fix worked for Kevin but not
for me. As soon as I would delete my agent directory and let the
agent rebuild it, the positive effects of the fix would be realized.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2003-07-02 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 17:14 Wes Hardaker
2003-07-02 7:40 ` Niklas Morberg
2003-07-02 20:08 ` Nevin Kapur
2003-07-02 15:18 ` David S Goldberg
2003-07-02 19:54 ` Wes Hardaker
2003-07-02 20:24 ` David S Goldberg [this message]
2003-07-03 7:32 ` Niklas Morberg
2003-07-03 13:54 ` David S Goldberg
2003-07-03 14:00 ` Wes Hardaker
2003-07-03 14:43 ` Simon Josefsson
2003-07-03 13:59 ` Wes Hardaker
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=u8zznjwhe2v.fsf@verizon.net \
--to=david.goldberg6@verizon.net \
/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).