New
#1
Outlook 2010 calendar invite being recieved as plain text
When Outlook calendar invitations are sent to certain recipients, they receive a plain text email as opposed to an actual iCal file. I have been doing my research on this, but have yet to find an answer. In order to narrow down the problem, I did a tightly controlled experiment:
I have Outlook configured to access email from several different POP3 servers, with all mail being directed to the same PST file. The first POP3 server is on my personal domain - I have a Linux-based VPS where the site is manage. The second POP3 server is a GoDaddy server.
Sent via my personal domain:
I created a first event in my Calendar and invited myself (personal domain). The message in the Sent folder is a proper iCal invitation and the invitation that I received is a proper iCal invitation. I then created a second event in my Calendar and invited myself (GoDaddy domain). The message in the Sent folder is a proper iCal invitation and the invitation that I received is plain text.
Sent via the GoDaddy domain:
I created a first event in my Calendar and invited myself (personal domain). The message in the Sent folder is a proper iCal invitation and the invitation that I received is a proper iCal invitation. I then created a second event in my Calendar and invited myself (GoDaddy domain). The message in the Sent folder is a proper iCal invitation and the invitation that I received is a proper iCal invitation.
In summary, the only instance that failed was when I sent the invite via my personal domain to another domain. (While my testing is far from exhaustive, this should at least provide a strong clue as to what is happening.) And yes, the Options->Calendar->When sending meeting requests outside of your organization, use the iCalendar format box is checked.
Can anyone suggest what might be going wrong? Based on these experiments, is it possible that something on my server is configured improperly? If so, what? (I did a further test and sent myself an invite via an Exchange server, and it showed up properly - thus I suspect even more strongly that the problem is with my server.)