Opened 14 years ago
Last modified 6 years ago
#7422 new bug
Odd email status changes
Reported by: | jonas.kirilla | Owned by: | czeidler |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/Mail | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I think MAIL:read and MAIL:status don't always make the best of friends. Sometimes two different MAIL:status values get written in fast succession, iirc when you close an email with a certain status. First Mail writes a status, which gets clobbered by another one from the mail_daemon
If you set the status of a message from "New" to whatever else, e.g. "Tomorrow", you're still offered the "Leave as New" option.
Mail changes some email from "New" to "Seen" even though I've turned off the feature to "automatically mark email as read".
(Why two such states? "Seen" and "Read". IMO, I've seen it equals I've read it.)
If you have multiple email open and close one with Shift-Alt-W to preserve its status (saving it from the automarker) the app will close ALL open windows, and statuses do get changed.
These are things I could look into, if you like, Clemens, but based on experience from a previous aborted attempt to refactor/layout Mail I'd probably go over it with a chainsaw.
Attachments (2)
Change History (11)
comment:1 by , 14 years ago
comment:2 by , 13 years ago
Oh sorry missed this ticket, maybe because there was a similar ticket that I fixed... Jonas, please go ahead, think changing the MAIL:status attribute is more robust now an should not overwrite none standard attributes.
The difference between seen and read is that you can differentiate between mails which are completely new and mails you have seen but still not read. Seen is like taking a short gimps at the mail and decide to read or reply to it later. This is very handy because if mails are automatically marked as read they vanished directly from the unread query even though they are still important. You have to explicit mark them as important but that should work the other way around: you should mark unimportant/handled mails as read, to not accidentally miss them. Since the mark as read button jumps to the next mail it is even less work than marking important mails as important :-).
comment:3 by , 13 years ago
Using hrev42345 (post-r1a3).
Is it possible that mails are stored without the MAIL:status attribute at the moment? New mail query as well as the deskbar mail menu tell me that I have 857 new messages (MAIL:read is read?), whereas Mail Status (after downloading 800+ mails) tells me there are "No new messages" (MAIL:status is read?). Reading a message doesn't change (or create) its MAIL:status attribute, only "Mark as read" does.
comment:4 by , 13 years ago
This seems to be a regression. That bug was fixed some time back, but I now see it again, too. Maybe with the recent localization, Clemens has slipped it in accidentally?
follow-up: 6 comment:5 by , 13 years ago
you can use DiskProbe to check if the attributes are written... Which app do you me by Mail Status? Deskbar and mail server only using the Mail:read attribute...
comment:6 by , 13 years ago
Replying to czeidler:
you can use DiskProbe to check if the attributes are written...
Edit: MAIL:status is not written (see "r42366_written_MAIL_attributes.png").
Which app do you me by Mail Status? Deskbar and mail server only using the Mail:read attribute...
E-mail preferences -> settings tab -> activate "Show connection status window" -> "Mail status" window (screenshot to illustrate: "Discrepancy Mail status - Deskbar.png")
by , 13 years ago
Attachment: | r42366_written_MAIL_attributes.png added |
---|
MAIL attributes in hrev42366 (MAIL:read but no MAIL:status)
by , 13 years ago
Attachment: | Discrepancy Mail status - Deskbar.png added |
---|
Screenshot to illustrate the discrepancy.
comment:7 by , 13 years ago
comment:8 by , 13 years ago
MAIL:status was only being written when R5_COMPATIBLE
was being defined, which Clemens obviously forgot to do. I've just removed that check, as MAIL:status makes sense, anyway, and will stay where it is.
Care to comment, Clemens?