On Do, 2013-01-10 at 22:15 +0000, Graham Cobb wrote: > On Wednesday 09 January 2013 22:43:43 Graham Cobb wrote: > > Alternatively, anyone implemented an ActiveSync proxy so I can proxy the > > server and log the messages? > > I found an answer: mitmproxy. It works well (although it would be even > better > if it knew how to decode wbxml).
Good to know, I need to try mitmproxy sometimes. I was about to suggest the activesyncd debugging env variable (from env_var_use_in_activesyncd): EAS_DEBUG 1 output 'critical', 2 output 'warnings' and above, 3 output 'messages' and above, 4 output 'debug' and above, 5 output libsoup debug and XML responses EAS_DEBUG_FILE <filename> writes debug output to specified file (only in activesyncd binary, libraries use glib logging with default handler for their domains: libeas, libeasclient, libeastest) EAS_SOUP_LOGGER 0 don't output soup logger debug, >0 output soup logger debug > I even found the problem, I think. It seems that the Username in the command > parameters should just be the username without the domain, but the > domain\username format has to be used for the authorisation. I will try that > out when I get a chance. If it works, I'll send a patch. I saw in your other email that it was something else. Patch welcome, of course. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
