Bug 164817 - mailbox flags not updated when checking mail
mailbox flags not updated when checking mail
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: evolution-connector (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Matthew Barnes
: Desktop
Depends On:
Blocks: FC6Target 170416 177586 FC6Desktop
  Show dependency treegraph
Reported: 2005-08-01 12:25 EDT by Chester Hosey
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-21 12:25:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chester Hosey 2005-08-01 12:25:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
Evolution does not notice changes made to a displayed folder until another folder is selected for viewing, and then the original is selected again.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open Evolution
2. Open Outlook on another machine
3. Using Outlook, delete a message or mark an unread message as read

Actual Results:  Even after checking for new messages, Evolution shows the deleted message in the index or continues to show the read messages as unread. Display can usually be refreshed by switching back and forth from another folder (Inbox->Deleted Items->Inbox).

Expected Results:  Attributes and messages should be updated while checking for new messages.

Additional info:

I have not tried this between two copies of Evolution running against Exchange or using Evolution + Outlook Web Access, only a copy of Evolution with a copy of Outlook.
Comment 2 Dave Malcolm 2005-08-18 18:29:20 EDT
Thanks for filing this report.

I've looked through the code; Evolution appears to correctly handle
notifications about new/removed messages and status changes in the messages it
receives from the evolution-exchange-storage backend, but does no global
monitoring for change information of this kind.  Your suggestion would involve a
full rescan on Send/Receive, which could work, but I'm uneasy about the
performance implications.

I'm marking this bug as ASSIGNED since it's correctly assigned to me.  However,
it currently has a very low position in my priority queue, and is not likely to
get fixed in forthcoming updates (although I plan to ensure that the problem is
addressed in RHEL 5).

If this issue is important to you, please contact Red Hat Support to get it
reprioritized.  Thanks.
Comment 3 Chester Hosey 2005-08-19 09:04:47 EDT
This is by far the most courteous and professional response I've received from 
any Red Hat employee.

It's not a high priority for me, I just wanted to make the issue known to Red 
Hat. I like bug reports because I imagine that they give the developer the 
opportunity to prioritize, rather than choosing to filter low-priority tasks.

I appreciate your response. I'm tempted to forward it to the support guys as an 
example of everything a reply to a customer should include.
Comment 10 Matthias Clasen 2006-07-06 17:47:37 EDT
Add to FC6Destop tracker
Comment 11 RHEL Product and Program Management 2006-07-21 12:25:09 EDT
Development Management has reviewed and declined this request.  You may appeal this decision by reopening this request.

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