On Wed, 2007-11-14 at 19:16 -0400, Patrick O'Callaghan wrote:
> On Wed, 2007-11-14 at 13:31 -0500, Art Alexion wrote:
> > On Wed, 2007-11-14 at 13:19 -0500, Patrick O'Callaghan wrote:
> > > On Wed, 2007-11-14 at 12:07 -0500, Art Alexion wrote:
> > > > On Wed, 2007-11-14 at 10:36 -0500, Patrick O'Callaghan wrote:
> > > > > On Tue, 2007-11-13 at 11:30 -0500, Art Alexion wrote:
> > > > > > On Mon, 2007-11-12 at 13:34 -0500, Marcus Senna Borges de Barros wrote:
> > > > > > > I using Evo 2.12.0 on Ubuntu Gutsy, and after I copied my email from
> > > > > > > previous versions to the personal folders, the filters only work when
> > > > > > > I select the messages (and also if the filter rule doesn't involve
> > > > > > > moving mail to a folder). No message error is given.
> > > > > > >
> > > > > > > Is there any way to find out what is happening?
> > > > > >
> > > > > > I've been told on this list that this is a known and ongoing problem.
> > > > >
> > > > > IMHO the most common reason for automatic filters not working is that
> > > > > more than one client is accessing the server mailbox concurrently,
> > > > > meaning that messages are not "new" and so are not filtered. See
> > > > >
http://www.go-evolution.org/FAQ#Why_do_my_mail_filters_not_work.3F> > > >
> > > > OK, it is rare, but sometimes possible that I am concurrently accessing
> > > > the account using
> > > > 1. evo 2.6 (Novell) on SLED 10.1
> > > > 2. evo 2.12.1 on xubuntu gutsy
> > > > 3. MS Outlook 2000 SP-3 on XP SP-2.
> > > >
> > > > None the less, this should not be my problem because I have:
> > > > A. The same filters on all of the clients, and
> > > > B. All of the filters move messages to folders on the exchange
> > > > server.
> > > >
> > > > For example, I have an exchange folder called "evolution" where all
> > > > messages from this list are supposed to be diverted to when they arrive.
> > > > That filter is on all of the clients.
> > > >
> > > > So, no matter which client accesses the new message first, it should
> > > > still be diverted to the evolution folder and accessible to the other
> > > > clients with access to that server-based folder.
> > >
> > > No necessarily. Remember that Evo follows IMAP semantics (even for
> > > non-IMAP servers), i.e. it "moves" a message by copying and deleting,
> > > and "deletes" a message by marking it, so until the original folder is
> > > expunged there are two physical copies of the message on the server.
> >
> > OK, but aren't they marked deleted on the server, and therefore, not
> > "read" but unavailable to other clients? In fact that is the way it
> > works when I have Outlook running concurrently. Outlook applies the
> > filter, moves the message, and Evo only sees it in the destination
> > folder, not two copies.
>
> They are marked \Deleted on the server. All I'm saying is that an
> instance of Evo distinct from the one that did the deletion will not
> notice the updated status until it resynchs.