[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#252975: marked as done (Read messages are set unread / wrong count & save of unread mails)

Your message dated Wed, 26 Apr 2006 13:12:46 -0400
with message-id <444FAA0E.7090201@vif.ca>
and subject line Bug#252975: IMAP?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
package: kmail 
version: 3.2.2-2

Greetings,

I've some trouble with kmail (from sarge 1.6.2)  regarding the number of 
unread messages in some Folder where list-mails were put to. When I start 
KMail it tells me, that the number of unread messages is two (for instance). 
When I open the folder the message-count went up to 32, but much of the 
unread mails have I read yesterday. I exited KMail whithout any errors or 
explicit killing.
The error (seem to?) appears, when I switched off compression for every folder 
after upgrading from KMail (KDE version 3.1.4).

Keep smiling
yanosz

--- End Message ---
--- Begin Message --- 
Jan Luehr a écrit :


Hello,

Am Mittwoch, 26. April 2006 11:35 schrieb Filipus Klutiero:

Hi Jan,
does this happen with an IMAP account? If so, does #253978 look like a
duplicate of this bug?
well, I don't know - to be honest, I'm know using etch and I don't know, under what circumstances I filed this bug almost two years ago. Since I'ven't noticed this issue in the last monts of using sarge (up to march 2006) - and already forgot, that I filed this report. 
Sorry about that.

Keep smiling
yanosz
Thanks for the followup. Since #253978 is most likely about the same issue and you can't provide information about this bug anymore, I believe it's best to close it.
--- End Message ---
Reply to: