On Thu, Nov 3, 2016 at 4:07 PM, Patrick O'Callaghan wrote:
> I suggest you report it to Bugzilla. That's the preferred way to track
> ongoing bugs. Post the bug number here in case anyone else wants to
> follow it.
>
Still didn't have time to create the bug report, but just wanted
On Thu, 2016-11-03 at 15:14 +0400, Emre Erenoglu wrote:
> OK, but I still have the issue :) Guess need to debug :)
I suggest you report it to Bugzilla. That's the preferred way to track
ongoing bugs. Post the bug number here in case anyone else wants to
follow it.
poc
On Thursday, November 3, 2016, Milan Crha wrote:
> I thought of the server having set very low timeout for inactive
> connections. There is such setting on the server.
>
I do not think so, there are thousands of Outlooks connecting to these
servers, I did not hear any issue
On Thu, 2016-11-03 at 13:35 +0400, Emre Erenoglu wrote:
> I do not think connection timeout is set a ms level, I'm sure it's
> some seconds on server and the error is not really due to a real
> timeout. My timeout setting in account is 20 secs, but the error is
> immediate, it's not due to some
On Thursday, November 3, 2016, Milan Crha wrote:
> It means just it, the server disconnected (terminated connection) in an
> unexpected way. I cannot tell from which part this comes, can be as low
> as gnutls or glib-networking. You can run evolution with debugging on:
>
>$
On Wed, 2016-11-02 at 18:30 +0400, Emre Erenoglu wrote:
> I'm on 3.22.2
Hi,
to be released the next Monday...
> and I'm very frequently getting this error stating "No
> response: Connection terminated unexpectedly"
It means just it, the server disconnected (terminated connection) in an
Hi,
I'm on 3.22.2 and I'm very frequently getting this error stating "No
response: Connection terminated unexpectedly", when sending messages or
receiving stuff through EWS, but a subsequent try works without issues.
So where can be the issue? A socket timeout too short? some inter-process