GNOME Bugzilla – Bug 482171
IMAP warnings are presented without folder context
Last modified: 2012-12-04 13:49:15 UTC
Please describe the problem: IMAP warnings received from the server are displayed without any context as to which folder they relate to. I use an IMAP account at my university, and some people have shared folders to all users that are above the quota warning level of 90%. Consequently, whenever I check my email, I receive quota warnings for their shared folders, even though my own account is well under quota. For example, I see: Alert from IMAP server username@imap.uni.ac.uk: Mailbox is at 95% of quota Even though my own account is at 77% of quota. Steps to reproduce: 1. Create an account on a server with shared folders that are over the quota warning threshold. NB: Reporting site is running on Sun JES, but nothing in the RFC indicates that these warnings are unwarranted. 2. Check mail. Actual results: Alert from IMAP server ojc4@imap.kent.ac.uk: Mailbox is at 95% of quota Expected results: Nothing besides the mail check. Alternatively, Evolution could label warnings with the folder they relate to. Alternatively, Evolution could queue the warnings for the end of the mail check and display them all in a table. Does this happen every time? Yes. Other information:
evolution only displays the information it gets from the server. the question is if the server is possible to provide that information in the string.
Indeed. Unfortunately, I deleted the relevant packet capture and the 95% mailbox has been fixed on the server so I can't create another one. However, the quota message was in response to the query of that particular mailbox. It should be possible to tie the two together.
Created attachment 204108 [details] [review] eds patch for evolution-data-server; Here you are. It basically shows quota alerts only from the first folder it gets the info in (it's after bug #357175), but I consider it rather a benefit, thus the message is not repeated as many times as folders are from that affected account.
Created commit 96c5278 in eds master (3.3.4+)
*** Bug 272329 has been marked as a duplicate of this bug. ***