On Fri, 2004-06-25 at 16:24 +0200, Pascal DRABIK wrote:
Jeff,tests to try to understand what is happening when the Evolution client is checking for emails on the Exchange server (once every 5 minutes in my own settings). I noticed the following while the client is initiating the checking. The client is sending a "LSUB" message.I think you mean the STATUS command... LSUB doesn't give any info about #messages, it just lists the names of the subscribed folders.Actually the STATUS command is just used once, at the very initial phase (authentication?).
ok, then this means that you only have an INBOX on this imap server? (no other folders?). If so, this makes sense.
Then the client is checking every 5 minutes the server. 2 situation can happen. 1- New emails are recognised as such. Then sequence exchanged between Evolution and the server are like (note the NOOP, FETCH commands):
[snip]
As I said, in one case, the "checking" session starts with the LSUB commands, and in the other it starts with a NOOP command. There is a strong correlation between the LSUB case and the fact that new emails are not recognised and NOOP case and the fact that new emails are recognised . I was expecting to see the same command sequence at least at the beginning.From what I understood from the protocol (RFC3501), I would not expect a checking session started by a "LSUB" command ( I must admit that I do not fully understand its use), but instead by a "NOOP" command.LSUB is not used to check new mail, it's used to probe which mailboxes exist. That information is then used to probe (using the STATUS command) for unread mail counts (not new messages).This is what I understood, but according to the log file, LSUB is used sometimes at the beginning of "checking" sequence.
LSUB is used to probe which mailboxes exist. That information is then
used to probe (using the STATUS command) for unread mail counts (not new
messages) in each of the folders returned to us in the LSUB response(s).
the IMAP server is supposed to tell us about \Recent messages both when
we SELECT a folder (" * 5 RECENT\r\n") and when we requst the FLAGS for
the message ("... FLAGS (\Recent) ...\r\n").
your server is giving us an empty flag set (which means not recent, not
read, not a draft, not deleted, and not answered) for each new message,
hence it is REMOVING the \Recent flag WHICH IT IS NOT SUPPOSED TO DO
hence, it is not a bug in evolution. it is a bug in the server.
Jeff
--
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
fejj ximian com - www.novell.com
Attachment:
smime.p7s
Description: S/MIME cryptographic signature