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 272329 - imap alerts give no clue as to source
imap alerts give no clue as to source
Status: RESOLVED DUPLICATE of bug 482171
Product: evolution
Classification: Applications
Component: Mailer
2.2.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
aklapper[errormessages] evolution[imap]
Depends on:
Blocks: 502515
 
 
Reported: 2005-02-08 06:47 UTC by Not Zed
Modified: 2012-12-04 13:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Not Zed 2005-02-08 06:47:20 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen? 


Additional Information:

e.g. ALERT [blah blah] from a given imap server, when i try to append to a
folder with no permissions, I get a box showing:

 Cannot create message - no write permission or out of disk space.

Then i get an exception saying 'append failed: unknown reason' (io.e. the
error message is also lost).
Comment 1 Matthew Barnes 2008-03-11 00:21:45 UTC 
Bumping version to a stable release.
Comment 2 Milan Crha 2012-12-04 13:49:15 UTC 
This got fixed for IMAP provider at bug #482171, same as the error is propagated to UI properly. It's harder with IMAP+, where the error is forgotten in an imapx_parser_thread(), which receives the error into its local_error variable and panic + stops itself on any error, but also doesn't bring the error to the job, thus it's lost.

There are opened bug reports for IMAP+ already, like bug #630149, and it was also unknown in times of filling this bug report, thus I'm closing this as a duplicate of the other bug, because it contains a fix.

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