#720521 claws-mail: Some new messages appear "old" instead

Package:
claws-mail
Source:
claws-mail
Description:
Fast, lightweight and user-friendly GTK based email client
Submitter:
Paul Evans
Date:
2013-08-29 14:57:10 UTC
Severity:
normal
#720521#5
Date:
2013-08-22 22:41:33 UTC
From:
To:
I'm using claws-mail pointed at my IMAP server (dovecot, also from
debian/testing). Most of the time, the "new" and "old" flags behave just
fine.

But occasionally, a message in a thread will not appear as "new",
instead only "old". I know that happens when the folder is refreshed
after new, but this isn't that. It happens to later messages in a
thread, after earlier ones that are still "new". See attached
screenshot.

I don't think there's an pattern to the messages - just occasionally
(maybe 1 in 100 or so? I haven't counted) it will happen.

#720521#12
Date:
2013-08-29 14:28:21 UTC
From:
To:
tags 720521 moreinfo
thanks

  Hi Paul,

On Thu, Aug 22, 2013 at 11:41:33PM +0100, Paul Evans wrote:
[...]

  Assuming there's no processing rule which could be messing the status,
would be interesting to see the network log when this happen, to see which
flags are retrieved from server.

  Is that possible?

  regards,

#720521#17
Date:
2013-08-29 14:34:56 UTC
From:
To:
The only processing rules I have are ones that set the message colour
to blue if it was sent by me - so nothing that ought to affect only a
few messages.

Is there a way I can be recording the network log all the time to a
file? I can then grab the tail-end of that when it next happens, as it
doesn't happen all that reliably.

#720521#22
Date:
2013-08-29 14:54:43 UTC
From:
To:
  Network log tail should be always ready (Tools/Network log), unless you
have restricted the log window to zero lines (see “Network log” in
Configuration/Preferences/Other/Logging).

  It can be tricky to find how many lines you have to put there, because
you are not going to know the session size before it happening, but I guess
some large value can do it.

  Alternatively you can launch “claws-mail --debug > some.log 2>&1” from
a terminal, so you have it all in some.log. Be sure to put some.log in a
drive plenty of free space :)