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 350346 - New messages only appear in inbox when evolution is started for the first time
New messages only appear in inbox when evolution is started for the first time
Status: RESOLVED DUPLICATE of bug 349413
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other other
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-08-07 23:00 UTC by ralph.sokel
Modified: 2006-08-17 06:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description ralph.sokel 2006-08-07 23:00:41 UTC
Distribution: Unknown
Package: Evolution Exchange
Severity: major
Version: GNOME2.12.0 2.6.0
Gnome-Distributor: SUSE
Synopsis: New messages only appear in inbox when evolution is started for the first time
Bugzilla-Product: Evolution Exchange
Bugzilla-Component: Connector
Bugzilla-Version: 2.6.0
Description:
Description of Problem:
Start evolution and all folders on the exchange server are updated.
Subsequently the inbox is not updated when new messages arrive.

Steps to reproduce the problem:
1. start evolution
2. send new message
3. 

Actual Results:

message appears in imap inbox but not in the exchange inbox

Expected Results:


How often does this happen?

always

Additional Information:




------- Bug created by bug-buddy at 2006-08-07 23:00 -------

Comment 1 Sushma Rai 2006-08-16 05:02:05 UTC
Can you please test this with 2.6.3?
Comment 2 ralph.sokel 2006-08-16 18:17:49 UTC
I have been following a bug report thread involving inbox updates and cpu usage problems which seem to have been resolved by 2.6.3. In that case you can mark this ticket as a duplicate and close it.
Comment 3 Sushma Rai 2006-08-17 06:33:01 UTC
Duplicate of 349413

*** This bug has been marked as a duplicate of 349413 ***