Re: [Evolution] How to keep multiple Evolution desktops in sync



On Wed, 2009-12-16 at 06:42 -0500, Adam Tauno Williams wrote:
On Wed, 2009-12-16 at 11:00 +0000, Patrick O'Callaghan wrote:
On Tue, 2009-12-15 at 11:10 +0100, Patryk Benderz wrote:
[cut]
You could forward them to an IMAP provider (such as Gmail or Fastmail)
and work from there.
yea, but on the other hand, this would violate my corporate policies,
thus this solution is not for me :(
In that case, the only solution is to run your own server inside the
corporate network.
*However*, on rereading the thread I realize I may have given you false
hope. Even with your own mail server, you cannot guarantee consistency
between multiple concurrent Evo instances. This is because IMAP doesn't
define the result of two or more clients accessing the same mailstore at
the same time. I don't mean you'll lose mail, but things that depend on
message state (such as filters) may behave strangely. You might be able
to get away with configuring all instances not to check for new mail
automatically, i.e. you do it yourself when sitting in front of them,
but even then you'd need to think about Evo not updating state info on
the mailstore without being forced to.
I use Evo at the office, at home and when travelling (as now). I take
care only to have one instance running at a time.

I've operated multiple simultaneous IMAP clients for years with Cyrus
IMAPd and never noticed any issues.  The only thing you can't use are
client-side filters, which seems kind of like a "Duh!", but with Cyrus'
SIEVE support nobody will mess them.

I'm fairly sure that client-side filters are what most people use, so
the point is moot. I know Cyrus supports Sieve and I heartily wish Evo
did too (it's been repeatedly requested over the years) but it doesn't,
so you have to use some out-of-band client to access it.

A Sieve plug-in would be welcomed by many, but note that people
accessing multiple servers are still going to need client-side filtering
until every server in the world supports Sieve, something I don't see as
ever happening.

Returning to the original point, certain operations on folders are not
updated to the server instantly, so you can get apparent inconsistencies
between multiple instances (which in the fullness of time will resolve
themselves as long as everything keeps working).

poc

poc




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