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 318515 - Maildir flags do not get updated
Maildir flags do not get updated
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[maildir]
: 318770 318809 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-10-10 22:04 UTC by Mark Abney
Modified: 2012-02-02 14:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Mark Abney 2005-10-10 22:04:20 UTC 
Please describe the problem:
When reading email in a maildir mailbox, messages get marked as read or deleted
appropriately (ie when read or deleted), but the flags on the message within the
maildir cur directory do not get changed to reflect the messages current status.
This causes a problem when a program like mutt looks at the maildir mailbox and
messages which have already been read or deleted via evolution appear new to
mutt.  Certain events can cause the flags to be updated, like switching to a
different mailbox, expunging messages, etc.

Steps to reproduce:
1. Open a maildir mailbox in evolution and read some new messages and delete
some messages.
2. With another MUA that can read maildir, look at the same mailbox. The
messages that were deleted or read with evolution do not appear deleted or read.
3. 


Actual results:


Expected results:


Does this happen every time?
yes.

Other information:
Comment 1 Mark Abney 2005-10-13 21:36:57 UTC 
*** Bug 318770 has been marked as a duplicate of this bug. ***
Comment 2 Mark Abney 2005-10-13 21:37:57 UTC 
*** Bug 318809 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2011-12-17 17:13:12 UTC 
Hi Mark,
Can you please check again whether this issue still happens in Evolution 3.0.3
or 3.2.2 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.
Comment 4 André Klapper 2012-02-02 14:26:45 UTC 
Closing this bug report as no updated information has been provided.

Please reopen this bug if the problem still occurs with a newer version of Evolution (currently this means: preferably version 3.2.x) and provide the information that was asked for in the previous comment.

Again thank you for reporting this bug and we are sorry it could not be fixed for the version that you originally used when reporting this problem.