Bug 445345 - mail-notification counting deleted messages
Summary: mail-notification counting deleted messages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mail-notification
Version: 9
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Dmitry Butskoy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-06 11:44 UTC by Jonathan Kamens
Modified: 2008-06-10 03:12 UTC (History)
3 users (show)

Fixed In Version: 5.4-1.fc9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-10 03:12:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
trace of mail-notification -i (sanitized) (13.68 KB, text/plain)
2008-05-08 03:18 UTC, Jonathan Kamens
no flags Details

Description Jonathan Kamens 2008-05-06 11:44:36 UTC
In some recent update, mail-notification started treating deleted messages in an
IMAP inbox as new, but only some of the time.  For example:

1. The two newest messages in my inbox are read and deleted.  There are no
unread messages.
2. I receive a new message in my inbox.
3. Mail-notification now reports that I have three unread messages -- the new
one, and the two deleted ones.
4. When I read the unread message, mail-notification goes back to saying that I
have no unread messages, i.e., suddenly the deleted messages don't count again.

I have mail-notification-5.3-1.fc9.i386.

This is annoying behavior.

Comment 1 Dmitry Butskoy 2008-05-06 13:31:40 UTC
I've sent it upstream...

Comment 2 Dmitry Butskoy 2008-05-06 16:35:11 UTC
Is the example above repeatable?

Try to drop (temporary) mail-notification from the panel, then run it manually
from the cmdline with the `-i' option: "mail-notification -i". This should
provide IMAP session transcript, which I'll send upstream for further debug...

Comment 3 Jonathan Kamens 2008-05-08 03:18:41 UTC
Created attachment 304827 [details]
trace of mail-notification -i (sanitized)

Made sure there were no unread messages in either of my IMAP accounts.	Killed
mail-notification.  Ran mail-notification -i.  Sent myself a test message. 
Mail-notification reported 1 unread.  Read it.	Mail-notification went back to
no unread.  Sent myself a second test message.	Mail-notification reported 2
unread.  Read it.  Went back to no unread.  Sent myself a third test message. 
Mail-notification reported 3 unread.  Read it.	Went back to no unread.

Trace is attached.  Usernames, passwords, host names and domain names have been
sanitized.

Comment 4 Jean-Yves Lefort 2008-05-08 16:57:32 UTC
Thanks for the log. I have spotted the regression (MN now improperly considers
messages which are RECENT but not UNSEEN as new). It will be fixed in 5.4.

Comment 5 Bug Zapper 2008-05-14 10:42:53 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Jonathan Kamens 2008-06-03 19:22:11 UTC
Somebody please rebuild the RPM with mail-notification 5.4, which has been released.


Comment 7 Dmitry Butskoy 2008-06-04 19:05:46 UTC
Try just built from:
http://kojipkgs.fedoraproject.org/packages/mail-notification/5.4/1.fc9/

Comment 8 Fedora Update System 2008-06-04 19:15:52 UTC
mail-notification-5.4-1.fc9 has been submitted as an update for Fedora 9

Comment 9 Fedora Update System 2008-06-06 07:50:24 UTC
mail-notification-5.4-1.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update mail-notification'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-5027

Comment 10 Fedora Update System 2008-06-10 03:12:04 UTC
mail-notification-5.4-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.