Re: [Evolution] I/O operation timing out

On Mon, 2013-10-28 at 11:00 -0400, Adam Tauno Williams wrote:
On Mon, 2013-10-21 at 18:58 -0400, Eric Beversluis wrote:
I now have Evo 3.8.5 on Fedora 19. So everything's up to date in Kansas
City. The problem persists. I'm doing 'send/receive' on three accounts,
all the same domain, all hosted at I've done some traceroutes
and my impression is that most if not all of the jumps take longer when
the attempt times out. This presumably would mean that it's not a
problem at the end. So I repeat my earlier query: Is there
some way to tell Evolution to wait longer before it times out? I've
already set net.ipv4.tcp_syn_retries to 7, which is supposed to give
about 90 seconds (per
But I'm getting the timeout error after about 45 seconds and 60 seconds.
And it's still intermittent--sometimes stuff downloads right away;
sometimes only one or two accounts download and then it times out.

Is this for an IMAP or POP account?

If you run "CAMEL_VERBOSE_DEBUG=1 evolution" do you see anything about
the timeout?  

I'm not an expert but noodling around in the camel code in EDS I do not
see anything that looks like a socket timeout; so I'd guess whatever the
default is what the default is.

I have one thing to add about this situation.  I'm using evo 3.8.5 and
have 12 pop accounts.  I have both a cable connection and a DSL
connection at my location.  I can simply change the cable between the
router and the modem, make one change in the router settings, and I am
connected to either the cable or DSL.

While connected to the DSL connection, everything works well.  However,
when connected to the cable, I get a notice that the connection has
timed out on random accounts.  That is, if I do a Send/Receive, one or
more accounts will time out.  Not  the same ones, different accounts
each time.  This leads me to think it is not in evolution, but in the
internet connection provided by the cable company.

One other thing that may or may not be related.  I cannot configure my
router remotely when it is connected to the cable, but can when
connected to the DSL.  This occurs on different routers so it is not in
my system.  My cable ISP insists they do not block any ports and,
obviously, my firewall is not involved as everything works while
connected to DSL.

This internet stuff is so much fun!


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