From: Lloyd Zusman <ljz@asfast.com>
Subject: nnimap-request-list operates differently right after startup
Date: Wed, 27 Feb 2002 21:17:46 -0500 [thread overview]
Message-ID: <m2lmdemjsl.fsf@asfast.com> (raw)
I've been seeing a problem in recent Oort versions (maybe over the past
4-6 weeks), where nnimap-request-list sees newly arrived messages if
it's invoked immediately after startup, but where it then refuses to see
any more new messages if it's re-invoked subsequent times. This begins
to occur after the messages which were originally present at startup
have been read, and then nnimap-request-list is re-invoked after new
messages have arrived in my INBOX; i.e., these new messages are not
seen.
Below are two nnimap-debug logs which illustrate the problem. Notice
that in the log that's generated right when Gnus is starting up, the
result of the nnimap-find-minmax-uid call is the appropriate minmax
list. However, note that in the second invocation, after that first
message had been read, the result of nnimap-find-minmax-uid is now nil,
even though there are indeed new messages in my INBOX at the time of the
second invocation.
If I then exit XEmacs and Gnus, and then restart, I will then see the
INBOX messages that were previously missed (i.e., the
nnimap-find-minmax-uid call will then return the proper minmax
information).
I'm running XEmacs 21.4.6 under RedHat Linux 7.2, and my INBOX is on a
remote host that's running a very recent version of Courier.
Any ideas?
Thanks in advance.
nnimap-debug log right when Gnus is starting up
-----------------------------------------------
======================================================================
1 -> nnimap-server-opened: server="myimap"
1 <- nnimap-server-opened: nil
======================================================================
1 -> nnimap-open-server: server="myimap" defs=((nnimap-address "imap.myserver.com") (imap-log t) (nnimap-nov-is-evil t))
| 2 -> nnimap-server-opened: server="myimap"
| 2 <- nnimap-server-opened: nil
| 2 -> nnimap-open-connection: server="myimap"
| | 3 -> nnimap-possibly-change-server: server="myimap"
| | 3 <- nnimap-possibly-change-server: " *nnimap* myimap"
| 2 <- nnimap-open-connection: (("myimap" " *nnimap* myimap"))
1 <- nnimap-open-server: (("myimap" " *nnimap* myimap"))
======================================================================
1 -> nnimap-request-scan: group=nil server="myimap"
| 2 -> nnimap-split-articles: group=nil server="myimap"
| | 3 -> nnimap-possibly-change-server: server="myimap"
| | 3 <- nnimap-possibly-change-server: " *nnimap* myimap"
| | 3 -> nnimap-split-find-inbox: server="myimap"
| | 3 <- nnimap-split-find-inbox: nil
| 2 <- nnimap-split-articles: t
1 <- nnimap-request-scan: t
======================================================================
1 -> nnimap-request-list: server="myimap"
| 2 -> nnimap-possibly-change-server: server="myimap"
| 2 <- nnimap-possibly-change-server: " *nnimap* myimap"
| 2 -> nnimap-before-find-minmax-bugworkaround:
| 2 <- nnimap-before-find-minmax-bugworkaround: nil
| 2 -> nnimap-pattern-to-list-arguments: pattern=("INBOX")
| 2 <- nnimap-pattern-to-list-arguments: ((nil . "INBOX"))
| 2 -> nnimap-find-minmax-uid: group="INBOX" examine=examine
| 2 <- nnimap-find-minmax-uid: (1 314860 314860)
1 <- nnimap-request-list: t
======================================================================
1 -> nnimap-server-opened: server="myimap"
1 <- nnimap-server-opened: (open run)
======================================================================
1 -> nnimap-request-newgroups: date="Wed, 27 Feb 2002 20:54:51 -0500" server="myimap"
| 2 -> nnimap-possibly-change-server: server="myimap"
| 2 <- nnimap-possibly-change-server: " *nnimap* myimap"
| 2 -> nnimap-before-find-minmax-bugworkaround:
| 2 <- nnimap-before-find-minmax-bugworkaround: nil
| 2 -> nnimap-pattern-to-list-arguments: pattern=("INBOX")
| 2 <- nnimap-pattern-to-list-arguments: ((nil . "INBOX"))
1 <- nnimap-request-newgroups: t
nnimap-log after all original messages were read and new ones have arrived
--------------------------------------------------------------------------
======================================================================
1 -> nnimap-server-opened: server="myimap"
1 <- nnimap-server-opened: (open run)
======================================================================
1 -> nnimap-request-scan: group=nil server="myimap"
| 2 -> nnimap-split-articles: group=nil server="myimap"
| | 3 -> nnimap-possibly-change-server: server="myimap"
| | 3 <- nnimap-possibly-change-server: " *nnimap* myimap"
| | 3 -> nnimap-split-find-inbox: server="myimap"
| | 3 <- nnimap-split-find-inbox: nil
| 2 <- nnimap-split-articles: t
1 <- nnimap-request-scan: t
======================================================================
1 -> nnimap-request-list: server="myimap"
| 2 -> nnimap-possibly-change-server: server="myimap"
| 2 <- nnimap-possibly-change-server: " *nnimap* myimap"
| 2 -> nnimap-before-find-minmax-bugworkaround:
| 2 <- nnimap-before-find-minmax-bugworkaround: nil
| 2 -> nnimap-pattern-to-list-arguments: pattern=("INBOX")
| 2 <- nnimap-pattern-to-list-arguments: ((nil . "INBOX"))
| 2 -> nnimap-find-minmax-uid: group="INBOX" examine=examine
| 2 <- nnimap-find-minmax-uid: (0 nil nil)
1 <- nnimap-request-list: t
--
Lloyd Zusman
ljz@asfast.com
next reply other threads:[~2002-02-28 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 2:17 Lloyd Zusman [this message]
2002-02-28 2:22 ` Lloyd Zusman
2002-02-28 2:22 ` Lloyd Zusman
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 2:17 Lloyd Zusman
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=m2lmdemjsl.fsf@asfast.com \
--to=ljz@asfast.com \
/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).