Re: [Evolution] trouble using Evolution with Exchange

On Thu, Mar 10, 2016 at 5:13 AM, Milan Crha <mcrha redhat com> wrote:

please do not use CAMEL_DEBUG=all, it's useless, too chatty. You have a
problem with EWS, then use EWS_DEBUG=2 only.

I then leave evolution idle for a few minutes. I compose a reply to a
message in Inbox. I try to send it. It doesn't get sent.

The sending part reuses connection from the receiving part, but doesn't
reconnect (thus multiple tries of the send do not work either). The
failed send disconnected the account, then the Send/Receive press
reconnected it.

That sounds like it would generate the behavior I'm seeing.

I would just run evolution with the EWS debugging on. Let it idle for
some time, then compose the message and before trying to send, mark the
place in the log. Then send the message. Whatever is below this mark is
related to the failed/closed-by-the-server connection.

I think I've got a reasonably short log file showing the problem.
There's a line in the log

(evolution:4206): camel-ews-provider-WARNING **:
camel_ews_folder_update_thread: Authentication failed

followed by blocks

< HTTP/1.1 401 Unauthorized
< Soup-Debug-Timestamp: 1457704216
< Soup-Debug: ESoapMessage 33 (0x7f2b40005130)
< Connection: Keep-Alive
< Content-Length: 0
< Date: Fri, 11 Mar 2016 13:50:15 GMT
< Server: Microsoft-IIS/7.5
< WWW-Authenticate: Negotiate
< WWW-Authenticate: NTLM
< WWW-Authenticate: Basic realm=""
< X-Powered-By: ASP.NET
< Connection: close

< HTTP/1.1 1 Cancelled
< Soup-Debug-Timestamp: 1457704216
< Soup-Debug: ESoapMessage 2 (0x5632b9e73dc0)
< Connection: Keep-Alive
< Transfer-Encoding: chunked
< Date: Fri, 11 Mar 2016 13:40:47 GMT
< Server: Microsoft-IIS/7.5
< Cache-Control: private
< X-NoBuffering: 1
< X-AspNet-Version: 2.0.50727
< X-Powered-By: ASP.NET

< HTTP/1.1 1 Cancelled
< Soup-Debug-Timestamp: 1457704216
< Soup-Debug: ESoapMessage 0 (0x7f2b40005770)


I think I'm ready to submit a bug report with this log. Before I do,
let me ask: There are entries in the log like this

Authorization: NTLM XXX...

Is it safe to post that information? As in, is there anything in the
log that could reveal a password or some other secret?

And is there anything else I should trim?

-- Garrett Mitchener

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