Re: [Evolution] Gmail: "Error storing folder ."

[Patrick O'Callaghan <poc usb ve>]

On Mon, 2008-11-03 at 09:10 -0500, Art Alexion wrote:
> On Fri, 2008-10-31 at 16:00 -0400, Patrick O'Callaghan wrote:
> > On Fri, 2008-10-31 at 11:07 -0430, Patrick O'Callaghan wrote:
> > > On Fri, 2008-10-31 at 11:44 +0100, Milan Crha wrote:
> > > > On Fri, 2008-10-10 at 11:10 -0430, Patrick O'Callaghan wrote:
> > > > > I get the above message several times a day when using Gmail via IMAP. I
> > > > > basically have Evo running all the time, but when this happens I quit
> > > > > and restart, and everything works again.
> > > >
> > > >         Hi,
> > > > what's the detailed description of the error message? (When you click
> > > > the icon of the message in the status bar, it opens the error window.)
> > > > Maybe something on evo's console too?
> > >
> > > Next time it happens I'll post the answer.
> >
> > OK, here it is. This just happened to me:
> >
> > 5 concurrent alert boxes (in the lower border), showing:
> > 1) Sending message (100% complete)
> > 2) Checking new mail (...)
> > 3) Retrieving message xxxxxxx (...)
> > 4) Storing folder 'Lists/Evo' (...)
> > 5) Filtering new message(s) (50% complete)
> >
> > No amount of clicking on any of these boxes has any effect. The top
> > menus however are active (i.e. they appear when clicked on). This state
> > has persisted for at least 90 minutes with no change.
> >
> > Selecting File->Quit grays out the Evo window, but nothing else happens.
> > Left it for 10 minutes to make sure. Only --force-shutdown has any
> > effect.
> >
> > The console shows several messages complaining that the folder
> > 'Lists/Evo' does not exist (which of course it does).
> >
> > On shutting down and restarting Evo, it reconnects to the various
> > servers with no problem.
> >
> > Evo 2.22.3.1 on Fedora 9 with all updates. KDE 4.1.2.
>
> The original error is likely a gmail problem.  I get the same error,
> about as often, with kmail.

Yes, it probably is Gmail in this case (I said as much in my BZ report).
However I've also seen it with a non-Gmail IMAP server.

More to the point: hanging the user interface indefinitely (literally
for hours) is not the way Evo should deal with this, especially as
manually killing and restarting solves the problem immediately in many
cases -- in fact in every single case so far when it's Gmail, not so
much for the other server. Evo should at the very least time out and
tell the user what's happening, preferably with an option to close and
reopen the connection within Evo itself.

Does Kmail behave this way? It's been a long time since I've used it.

poc