EWS: Mail folder is missing on the server / Server response is not XML

[mabahj]

Hi,

AquaMail version: 1.3.0-pre2 (paying)

I'm trying to get Exchange Web Services to work. The admins at work have assured me that EWS is active since the Mac users are using it. When I try to add the EWS account, I get "Exchange mail server (EWS): Mail folder is missing on the server. Please make sure the data is correct."

I have the log and can email it to you if you want it. What I found is:

• It fetches https:// webmail(dot)mycompany(dot)com/EWS/Exchange.asmx
• It gets a "302 Moved Temporarily" to "https:// webmail(dot)mycompany(dot)com/CookieAuth.dll?GetLogon?curl=Z2FEWSZ2FExchange.asmx&reason=0&formdir=3"
• It does a "GET /CookieAuth.dll?GetLogon?curl=Z2FEWSZ2FExchange.asmx&reason=0&formdir=3" and gets a "HTTP/1.1 200 OK"
• It checks some attributes and logs "Server response is not XML"
• And then it seems to stop.

The "server response is not XML", which is strange. When I browse to https:// webmail(dot)mycompany(dot)com/ews/exchange.asmx I do get XML, after a redirect to https:// webmail(dot)mycompany(dot)com/ews/Services.wsdl. The only clue the admins had, was that the Mac users had to enter the full https:// webmail(dot)mycompany(dot)com/ews/exchange.asmx address to get EWS working.

I would love to get this working! Any ideas?

(Great app! Worth every cent and more!)

Best regards,
Markus

[mabahj]

Problem is still there in version 1.3.0-pre5.

Sent from my GT-I9100 using Tapatalk

[Kostya Vasilyev]

The redirect is MS Forefront, a security proxy for Exchange.

I don't have any experience with it, and don't have a server that uses it, but.... apparently, Forefront doesn't like something in my app's XML/SOAP/HTTP and redirects to a page where you're supposed to confirm your credentials "manually". This doesn't work of course.

I've posted questions about it on stackoverflow and MS's own support forum... no replies in either place.

http://social.technet.microsoft.com/Forums/forefront/en-US/a60fbd3f-5ad4-4ba9-a52c-3a10dde2da3a

If you can ask your network admins about it, and they can shed some light on what exactly Forefront doesn't like in my app's server requests, it would be much appreciated.

I'd be happy to change whatever is necessary to make it work (XML formatting, HTTP headers, etc.) but I just don't have any info on what to change.

[mabahj]

Hi,

I'm really sorry for not following up on this. I did, however, notice that you were able to fix the problem, which is great! Now it works most of the time, but I do get some "Invalid server response" error messages. I'll email you a log.

[Kostya Vasilyev]

The Forefront issue is fixed (should be, I should say... but it appears to be really fixed).

For the 500's, yes, I'd appreciate a log, please make sure that "raw session data" is enabled so I can see the actual HTTP data.