El día Tuesday, March 01, 2011 a las 09:43:34AM -0430, Patrick O'Callaghan
escribió:
> On Tue, 2011-03-01 at 23:55 +1100, Bart Steanes wrote:
> > After a network dropout (while using evolution on the train for example) re
> > syncing seems to fail much.
> >
> > For example I have not successfully sync'd in the last 12hours although I've
> > tried several times including for the last hour using the office ADSL
> > connection (which has 99.99% uptime, and 100% during the test period).
> >
> > What usually happens is that evolution gets to some random low % complete
> > (eg 31% currently, progressing at around 3% per minute), then stops, and
> > acts like it's finished without actually finding any new email.
>
> Hve you tried restarting Evo? That usually seems to fix this sort of
> thing.
I encounter the same problem with Evo && OutLook server, especially
while moving in UMTS (WAN) networks or even between WLAN's in our
building. The problem is that Evo helds permanent connections to the
servers:
$ netstat -an | fgrep EST | fgrep ...
tcp4 0 0 192.168.13.128.39397 xxx.174.29.60.3268 ESTABLISHED
tcp4 0 0 192.168.13.128.55806 xxx.174.29.60.3268 ESTABLISHED
tcp4 0 0 192.168.13.128.18739 xxx.174.1.144.443 ESTABLISHED
and does not use somekind of polling, like with POP or IMAP. Seems to be
a design problem (or feature :-))
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <[email protected]> - w http://www.unixarea.de/
_______________________________________________
evolution-list mailing list
[email protected]
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list
