Re: [Evolution] evolution-list Digest, Vol 113, Issue 20

[Guy Stalnaker <guy stalnaker wisc edu>]

Patrick and Andre,

One might think, as an IT professional for 25 years, that I'd remember (!!) to add versions, etc. to posts like mine.

Debian Testing, Evolution 3.12.9, KDE desktop (not Gnome). This is an Office365 account using EWS (not IMAP; EWS support is the reason I'm trying Evolution; Microsoft throttles IMAP with Office365 making it absolutely maddening to use). I check this Office365
 account primarily with Microsoft OWA (which I use for Calendar only and not email if I can help it), HTCOneM8 smart phone using the HTC email client, a Samsung Tab3/8 using MailDroid.

The error that prompted my email to the list occurred in Evolution during the time I walked to the Union to grab a cup of coffee and I was not checking my mail with wither HTC or Samsung device, but I can figure the only way a message can become "unavailable"
 is if another client does something with it. 

I will follow Patrick's suggestion about a corrupted local database.

Thanks.

On Fri, 2014-12-19 at 17:37 +0000, evolution-list-request gnome org wrote:

Message: 8
Date: Fri, 19 Dec 2014 17:36:41 +0000
From: Patrick O'Callaghan <poc usb ve>
To: evolution-list gnome org
Subject: Re: [Evolution] Error while Unknown background operation.
Message-ID: <1419010601 1637 49 camel usb ve>
Content-Type: text/plain; charset="UTF-8"

On Fri, 2014-12-19 at 16:40 +0000, Guy Stalnaker wrote:
> "Cannot get message with message ID 48286: No such message available."
> 
> This error has occurred every day I have used Evolution. I cannot remove it except by restarting Evolution. Seems to be in some sort of loop. The "Cancel the current mail operation" button on the button bar flickers and clicking it does
 nothing. The Close button on the error message does nothing.
> 
> I suspect this is related to the fact that I check my mail with multiple clients. Is there some setting I can use to affect this behavior?

Is this an IMAP or a POP account? You might have a slightly corrupted
local database. Try shutting down Evo ("evolution --force-shutdown") and
running:

        cd ~/.cache/.evolution/mail/
        for i in `find . -name folders.db`
                do
                echo "Rebuilding Table $i"
                sqlite3 $i "vacuum;"
        done
        
poc