Too many quota warning messages in evolution

[Bastian]

Binary package hint: evolution

When I used 85% of the quota on my IMAP, Evolution popped up a quota warning
window every time it synchronised (which is every 1 min for me). New warning
windows are opened even if the previous ones are still there, which I all had
to click away one by one. I have not found any configuration option to disable
the quota warning or set another threshold. I had to delete messages to not use
more than 85% of my quota to make Evolution usable again. Thus, I suggest:

1. Make it possible to set the quota warning threshold.
2. Make it possible to disable the quota warning altogether.
3. Do not open a new warning window if there is still one open for the same
mailbox.

I originally reported this bug to upstream evolution here:
http://bugzilla.gnome.org/show_bug.cgi?id=349542
They said this is Redhat extension, but I am experiencing this under Ubuntu (Edgy).

Bastian

[Sebastien Bacher (seb128)]

Thank you for your bug. We don't change evolution to do that, either that's an upstream bug or something you installed. What IMAP server do you use?

[Sebastien Bacher (seb128)]

do you use exchange? looks like http://bugzilla.gnome.org/show_bug.cgi?id=412609 upstream

[Bastian (bastian-absoluterend)]

This happes with a SLOX (Suse Linux Open Exchange) server. I don't see any configuration options wrt. quota warnings there. As mentioned, I first reported this upstream and was told that it is a RedHat extension. I also asked the admins of the SLOX server, but they said this must be client-side. Of course, if you know that it's definately upstream or server-side, I will re-open the upstream bug report (because even if it is server-side, Evolution should spare the user the hassle IMO).

[Bastian (bastian-absoluterend)]

Just for clarification: I meant I see no configuration options for quota warnings on SLOX as a user, as I don't have admin access there.

[Sebastien Bacher (seb128)]

Looks like http://bugzilla.gnome.org/show_bug.cgi?id=399418 upstream

[Sebastien Bacher (seb128)]

Do you still get the issue in the current version?

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Closing the bug since no further information has been provided.