Re: [Evolution] Race condition?

It just sounds like the message was moved and deleted.

But for whatever reason the other cliens aren't honouring the deleted flag, or it hasn't been sent yet.

On Wed, 2005-03-09 at 12:49 -0400, Patrick O'Callaghan wrote:
On Wed, 2005-03-09 at 11:04 -0500, Jeffrey Stedfast wrote:
> On Wed, 2005-03-09 at 11:27 -0400, Patrick O'Callaghan wrote:
> > When a new message arrives it often shows up in my Inbox and then
> > quickly disappears after being grabbed by an input filter and refiled
> > somewhere else.
> > 
> > This is confusing to say the least, but may also be related to a
> > phenomenon several people have remarked on: the same message often
> > appears both in Inbox and in another folder. I mean the *exact same
> > message*, not a duplicate.
> what's that supposed to mean? if it's in 2 folders, how is it not a
> duplicate?

What I mean is that it's not a case of the same message being sent twice
to a mailing list, or once to a list and once to my address. It was sent
once, was delivered once by the mail server, and is now present in two
places, I'm guessing because Evo copied it and didn't delete the

> >  I use a Cyrus IMAP server and both "copies"
> > of the message refer to a single physical file on Cyrus' database (Cyrus
> > uses Unix links to make the message appear in several folders).
> that's an implementation detail that has nothing to do with evolution...
> as far as evolutin is concerned, the 2 messages are not the same object.

Fair enough.

> >  This is
> > not a rare ocurrence; it happens to me regularly several times a day,
> > and only with Evo (I sometimes use Thunderbird, also with filters, and
> > it never exhibits this behaviour).
> sounds like your filters aren't setup properly. maybe you forgot a stop
> processing?

No, I didn't forget. The filters simply have "Move to folder" followed
immediately by "Stop processing".

> > Is this a synchronization problem between several components of Evo? Can
> > someone fix it?
> > 
> not a synch problem at all.

But nevertheless a problem. It's happened to me with every version of
Evo since the 1.0 series.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]