Re: [Evolution] Cannot Authenticate with Exchange Server

["Davis Ford" <davisford gmail com>]

Hi Paul,

Thanks for the response.  I enabled the proposed repo and pulled down
92 updates -- including the latest evolution and evolution-exchange.
Still no luck.  I tried all permutations I could think of for the
username/URL...

TANA\davidfor
TANA\\davidfor
TANA/davidfor
TANA\/davidfor
TANA\\davidfor
davidfor

https://mail.somewhere.com
https://mail.somewhere.com/exchange
https://mail.somewhere.com/exchange/davidfor

Every time it fails to authenticate.  The final HTTP response is a 200
OK, and then nothing happens.  I notice there is a 302 re-direct, but
this appears to work fine.  Is E2K_DEBUG=2 the highest log level, or
can I crank it up to get more information?   I'm not an HTTP header
wizard, but should it be expecting a Connection: close on the final
HTTP response?

< HTTP/1.1 302 Moved Temporarily
< Soup-Debug-Timestamp: 1212163645
< Soup-Debug: SoupMessage 2 (0x8601670)
< Location: https://mail.somewhere.com/CookieAuth.dll?GetLogonWrapper?url=%2Fexchange%2F&reason=0
< Set-Cookie: sessionid=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Set-Cookie: cadata=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Connection: close
< Content-Length: 0

> GET /CookieAuth.dll?GetLogonWrapper?url=%2Fexchange%2F&reason=0 HTTP/1.1
> Soup-Debug-Timestamp: 1212163645
> Soup-Debug: SoupSessionSync 1 (0x86294c0), SoupMessage 2 (0x8601670), SoupSocket 3 (0x81289a0), restarted
> Host: mail.somewhere.com
> User-Agent: Evolution/2.22.2
> Authorization: NTLM TlRMTVNTUAABAAAABoIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA

< HTTP/1.1 200 OK
< Soup-Debug-Timestamp: 1212163646
< Soup-Debug: SoupMessage 2 (0x8601670)
< Pragma: no-cache
< Cache-control: no-cache,max-age=0,must-revalidate
< Content-Length: 998
< Connection: close



On Fri, May 30, 2008 at 11:50 AM, Paul Smith <paul mad-scientist us> wrote:
> Do you have the "hardy proposed" repository enabled?  There's an update
> to Evo Exchange there, to this version:
>
> 2.22.2-0ubuntu1
>
> There's also a critical update to libldap that you'll need if you intend
> to use the Exchange address list for completion, etc.
>
> > username: TANA\davidfor
> > OWA URL: https://mail.somewhere.com/exchange/
>
> First, the URL just needs to be the hostname; you can leave off the
> "exchange" part:
>
>        https://mail.somewhere.com/
>
> I haven't needed to use a domain but I do remember having problems with
> earlier releases.  Getting this syntax right is definitely the first
> step.  I recommend trying a forward slash instead:
>
>        TANA/davidfor
>
> to see if that works.



-- 
Zeno Consulting, Inc.
http://www.zenoconsulting.biz
248.894.4922 phone
313.884.2977 fax