Re: [Evolution] EWS: No response: Connection terminated unexpectedly
On Thu, Nov 3, 2016 at 4:07 PM, Patrick O'Callaghanwrote: > 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 to note that I disabled the "send using outbox" in settings. Now I face the issue much less, although sometimes the send dialog complains that it can't succeed, which I click retry and it's OK. Emre ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] EWS: No response: Connection terminated unexpectedly
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 ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] EWS: No response: Connection terminated unexpectedly
On Thursday, November 3, 2016, Milan Crhawrote: > 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 from anybody else. > With automatic updates I meant "Check for new messages every X > minutes", which will keep the connection busy, but from what you wrote > OK, X= 10 minutes in my setup. It also checked for all folders. (otherwise sent mail folder is not up to date when I click it) > it sounds like it's not the problem. The "Listen for server change > notifications" only keeps open a connection and sits on it, with no > activity from the evolution-ews side. OK, but I still have the issue :) Guess need to debug :) -- Br, Emre ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] EWS: No response: Connection terminated unexpectedly
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 activity, which opens a connection, > gets some data but cant' finish. Hi, I thought of the server having set very low timeout for inactive connections. There is such setting on the server. > I also have "listen for server change notifications". Could you give > a hint on how I can modify the automatic updates? (or simultaneous > kept open connections to EWS server?) With automatic updates I meant "Check for new messages every X minutes", which will keep the connection busy, but from what you wrote it sounds like it's not the problem. The "Listen for server change notifications" only keeps open a connection and sits on it, with no activity from the evolution-ews side. Bye, Milan ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] EWS: No response: Connection terminated unexpectedly
On Thursday, November 3, 2016, Milan Crhawrote: > 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: > >$ EWS_DEBUG=2 evolution > > OK, I'll try. > I do not see this error with my EWS server. It can be that the server > has lower connection timeout set, as you said, for which you might > lower also the automatic updates for that account in the evolution, to 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 activity, which opens a connection, gets some data but cant' finish. I also have "listen for server change notifications". Could you give a hint on how I can modify the automatic updates? (or simultaneous kept open connections to EWS server?) Thanks, Emre -- Br, Emre ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] EWS: No response: Connection terminated unexpectedly
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 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: $ EWS_DEBUG=2 evolution but I doubt it'll shed more light on it. The subsequent calls work, because the evolution-ews reconnects to the server, using a fresh connection. I do not see this error with my EWS server. It can be that the server has lower connection timeout set, as you said, for which you might lower also the automatic updates for that account in the evolution, to have the connection refreshed more frequently. Bye, Milan ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] EWS: No response: Connection terminated unexpectedly
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 communication issue? Anybody facing this? Thanks, Emre -- Br, Emre ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list