This one is bothering me, too, although I'm not sure that it's the upgrade to Evolution that's broken things for me. I suspect that changes to the server may be causing problem instead or as well.
In my case, it was coincident with upgrading from 2.4 to 2.6. One thing I discovered is that if I get a meeting request etc from Exchange, the URL appended by the server doesn't work : the server returns "500 Invalid URL". Changing "%0A" to "_x000A_" and "%0D" to "_xOOOD_" gives one that it's happy to process. Looks like someone made a fix to a URL exploitation bug without considering the knock-on effects? Perhaps just coincidence, though - I can't confirm that this failure only started when Evolution stopped working for me. I don't know how to identify the server version from Evolution or the Web front end, nor how to do any protocol debugging (e.g. seeing what error message the server returns). If this is straightforward, I'll have a look and report what I find. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
