I'm using ical4j version 1.0.3 and running into this issue which seems to be related to http://support.microsoft.com/kb/2643084.
Here's an example of an ics created with ical4j:
PRODID:-//Foo Software//Foo Events//EN
SUMMARY:TESTING EVENT DURRR
DESCRIPTION:blah blah halb
Have you tried enabling the OUTLOOK_COMPATIBILITY hint in ical4j.properties? I am not sure if the fold length impacts on Outlook's parsing of ICS data:
If you find out it's caused by something else please let me know and I will try to update the above hint to cater for it. Thanks.
Thanks for the reply. Adding the OUTLOOK_COMPATIBILITY hint didn't fix the issue. The code already had RELAXED_UNFOLDING and RELAXED_PARSING hints set so I'm not sure if there could be a bad combination of hints.
After doing more research last night, it seems Exchange Server 2010 added more restrictive ics processing. I've also found this doc (http://msdn.microsoft.com/en-us/library/ee219935(v=exchg.80).aspx) which outlines the ical to outlook appointment conversion algorithm. Hopefully going through this will shed some light on the issue.
If you have any other references or ideas you think might be helpful I'd appreciate it. It seems this is a common problem.
I was also wondering if there's an up-to-date changelog? I haven't been able to find one for versions 1.0.3 and up.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.