After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 274407 - IMAP4rev1: moved message pops up as new
IMAP4rev1: moved message pops up as new
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.2.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Jeffrey Stedfast
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-04-05 13:21 UTC by bugreports
Modified: 2005-05-23 17:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bugreports 2005-04-05 13:21:52 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

moving an already read message to a different folder sets the message
status to 'NEW' again.

(server courier imap debian-sarge)

Steps to reproduce the problem:
1. send yourself a message
2. read that message and then move it to a different folder
3. enter that folder (select it)

Actual Results:
message pops up as unread

Expected Results:
message status is kept (read)

How often does this happen? 

note however that this only happens with new messages that were just read.
reading the message + then changing the folder is enough as a workaround

Additional Information:

in prefs I have selected mark message read after 0 seconds
Comment 1 Jeffrey Stedfast 2005-04-05 15:29:35 UTC
there is no NEW status in IMAP. There are only:

\Recent \Seen \Answered \Deleted \Draft \Flagged

which one is it?
Comment 2 bugreports 2005-04-05 15:36:13 UTC
I am not talking about the IMAP protocol but the mail status in
evolution, which is be "unread" or "read"... with "new" I am referring
to "unread" mail. sorry for that mislabeling
Comment 3 Jeffrey Stedfast 2005-05-23 15:56:12 UTC
ok, looks like we just need to sync the flags before sending the COPY command to
the server. should be an easy fix
Comment 4 Jeffrey Stedfast 2005-05-23 17:17:48 UTC
fixed in CVS