Re: [Evolution] SOLVED (probably) Re: "Error while performing operation. Cannot get message with message ID ..."

[Volker Wysk <post volker-wysk de>]

Am Samstag, den 03.08.2019, 14:02 +0100 schrieb Patrick O'Callaghan:
> On Sat, 2019-08-03 at 14:23 +0200, Volker Wysk wrote:
> > Am Samstag, den 03.08.2019, 12:01 +0100 schrieb Patrick
> > O'Callaghan:
> > > On Sat, 2019-08-03 at 07:58 +0200, Volker Wysk wrote:
> > > > This means (probably) that evolution 3.32.1 doesn't properly
> > > > cope
> > > > with
> > > > folders which are used/accessed by two or more IMAP clients
> > > > simultaneously. A message ID can be valid in one moment and
> > > > invalid
> > > > in
> > > > the next, because a different agent has done something. That's
> > > > not
> > > > an
> > > > error, it should just be ignored (as far as I can tell).
> > >
> > > How is Evolution supposed to know it's not an error? If you have
> > > two
> > > different and uncoordinated email clients manipulating the same
> > > server
> > > mailbox, each of them can only report on what it sees.
> >
> > I don't know. But it should be taken into consideration that this
> > can
> > happen and is not an error.
>
> The server reported a message as being present, but then can't
> deliver
> it. How is this different from an actual server-side error and how is
> the client supposed to know?

It may be a server-side error. But when the server can't deliver the
message, because meanwhile some other agent did something to it
(deleted it, for instance, or moved it somewhere), then it's not. 

I'm afraid that the client can't know. The server would have to
remember that there was a message with that ID, which has now expired.
Then it could tell the client "ID expired" instead of "ID invalid".


> > > If you want to use getmail to fetch mail and put it on your local
> > > IMAP
> > > server, then I suggest you point Evolution to the *local* server.
> >
> > That's what I'm doing, with the other account.
>
> I fail to see what you gain from not doing it with this account as
> well. What is the point?

I have two mail accounts configured in evolution. The first one
connects to my own Dovecot IMAP server, which is fed my mail as it
arrives in the IMAP server of my provider. The second one connects to
my provider's IMAP server directly.

I've configured the second one, when my own (downstream) Dovecot server
wasn't operational yet. So I could access my mail on the upstream IMAP
server of my provider. I also used it for testing.

Now I don't need it any longer. As I've written, I disabled it now, and
the problem went away. I could as well delete it completely. 

Bye
Volker