Hi guys, Sorry for crossposting this, but I think it's important enough for the development team and Evolution users who happen to have an Exchange backend. I received the following mail from one of those users (quoting instead of forwarding since I have no explicit permission to do so):
" Hi, Sorry to contact you this way as i'm not familiar with Bugzilla at all. I've read the following Bug Report http://bugzilla.ximian.com/show_bug.cgi?id=65915 and a few days ago we confirmed this bug with Microsoft. We have an Exchange 2000 Cluster system Crashing all the time with an Evolution Client accessing one specific appointment. An export of the item with outlook and import to a testsystem confirmed that it's working for all versions of Exchange 2000 available at the moment. We do not exactly know what evolution is doing wrong and / or if we have a working fix for Exchange (We test the fix: http://support.microsoft.com/?id=875550 at the moment) I'm trying to find out what exactly is wrong on the appointment to inform you what Evolution does wrong. " So maybe Evolution handles in a "wrong" way the appointments, but it's a known MS Exchange problem. So be warned. -- Gerardo Marin <[EMAIL PROTECTED]> Novell Inc. _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
