That's true. I've to look for a solution on the network layer - let's say unix service layer - rather than the application. It seems pretty logical to use a local server rather than a client app.
Thanks for the advice. :) Good luck! vm El mié, 06-03-2013 a las 10:31 +0000, Pete Biggs escribió: > > I'm using a 3G modem on a very busy network which is connected via > > satellite to the continental relay. > > The result is a very slow connection (4 to 6 Kbps) and very intermitent > > over daytime with many packet losses. This triggers too many timeouts - > > on every application -. > > > > The problem really is that Evo (and many other mail clients) assume to > some degree that when a net connection is present, it is going to be > reasonably reliable. I can understand your problem, and am sympathetic, > but it is not a "normal" scenario. Consequently I don't think that it > is within Evolution that you are going to find your answer. > > One thing you might like to look at is using the underlying Linux system > with Evo - things like OfflineImap to retrieve your mail and store it > locally and sendmail/postfix/exim to queue and send your mail - > certainly sendmail was developed in the UUCP era so is based around > flaky connections. > > Using applications such as these will offload the network side from Evo > since it will only deal with local data - it will certainly stop the > annoying popups and complaints from Evo about timeout errors. The > backend mail movement processes will then do their job as and when they > can. > > P. > > > _______________________________________________ > evolution-list mailing list > [email protected] > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
