Sign up for Office 365
Learn more about Office 365
I'm using Outlook 2010 and exchange account via Office 365. When I'm sending a meeting request few users receives it in plain - scrambled text like:
I've already try to start "defected" Outlook in safe mode - no success. I'm the only one on the exchange, other users are using POP without exchange.
Thank you all for your help.
Thanks for your reply.
Outlook 2003 was designed and built for an environment where servers are maintained locally within an organization and not part of a cloud service. Therefore, it is not recommended to connect Office 365 Exchange Online account to client Outlook 2003 as some features and functionality are not supported. Outlook 2003 cannot provide a better end-user experience when connected to Office 365.
In this situation, I would like to know if the issue happened when send request from Outlook 2010 to Outlook 2010.
Hi Matjaz Sustersic,
I would like to confirm are the POP accounts also Office 365 users? If so, please check if they can receive the meeting request in Outlook Web App(OWA). Change the connection from POP to Exchange should be able to fix the issue.
If other accounts are not Office 365 users, please try to change the message format in Outlook to see if the issue can be resolved. The issue might be caused by the text format message settings in Outlook, and you change the format from text to HTML, or Rich Text.
Change the message format to HTML, Rich Text, or plain text in Outlook 2003
Change the message format to HTML, Rich Text, or plain text in Outlook 2007
Change the message format to HTML, Rich Text, or plain text in Outlook 2010
Hi Reken Liu
Thank you for you answer.
POP accounts are not on the Office 365 (Exchange), they are on completely different server/domain.
I tried and checked all options about message format:
- checked that all messages are sent as HTML
- checked that message for "defective" user is sent as HTML
Could it be the Outlook version? Because Outlook 2003 clients received corrupted meeting request, Outlook 2010 users received meeting request without problems.
Thank you and BR,
There have a big changes from Outlook 2003 to Outlook 2010. The issue might be a compatible error. To help to narrow down the issue, you can send a meeting request from one of the Outlook 2003 clients, and monitor if other Outlook 2003 can receive the request normally.
I am wiriting to follow up on my previous reply, and I would like to know the status of the issue. Is there any update from your side?
I didn't have chance to test Outlook 2003 – Outlook 2003 clients.
Today I tested:
1. Outlook 2010 (Exchange user) to Outlook 2003 (POP user). Result: Outlook 2003 received corrupted meeting request.
2. Outlook 2003 (POP user) to Outlook 2010 (Exchange user). Result: Outlook 2010 received meeting request without any errors, but when this Outlook 2010 confirmed and send meeting confirmation, Outlook 2003 received corrupted version of meeting confirmation.
Thank you and br,
Hi Grace Shi,
Thanks for you reply.
If I send meeting request from Outlook 2010 (Exchange) to Outlook 2010 (POP) it works fine. So that means than Office 365 users can not send meeting requests to Outlook 2003 users? What about Outlook 2007?
According to the software requirements for Office 365, Outlook 2007 SP2 or above versions are fully supported. It should work in Outlook 2007. If not, please update Outlook 2007 to SP2.
Is there any other assistance needed here?
Hi Reken Liu,
I see now, that Office 2003 isn't supported by Office 365, so obviously that's why Office 2003 can't receive meeting requests from Outlook 2007 or 2010. I'm I right? It there any workaround?
Apologize for the delay on response. Just received message that we will now offer support for Office 365 customers connecting to Outlook 2003 via POP or IMAP. You can try to send a meeting request from Outlook 2010 to test if it works now.
Have you tested it and does the meeting request work well in Outlook 2003 now?
Sorry for my late reply, I was absent for a while. The problem persists. Below you can see received message on a computer with Microsoft Office 2003.
From: Matjaž Šušteršič [mailto:email@example.com]
Sent: Monday, April 16, 2012 2:21 PM
To: 'Dejan' (firstname.lastname@example.org)
Subject: Testni sestanek
Delivery-date: Mon, 16 Apr 2012 14:21:42 +0200
Received: from mail by juni.spletnahisa.net with spam-scanned (Exim 4.76)
for email@example.com; Mon, 16 Apr 2012 14:21:42 +0200
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on juni.spletnahisa.net
X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00,HTML_MESSAGE,
Received: from ch1ehsobe005.messaging.microsoft.com ([126.96.36.199]
by juni.spletnahisa.net with esmtps (TLSv1:AES128-SHA:128)
for firstname.lastname@example.org; Mon, 16 Apr 2012 14:21:36 +0200
Received: from mail157-ch1-R.bigfish.com (10.43.68.242) by CH1EHSOBE008.bigfish.com (10.43.70.58) with Microsoft SMTP Server id 188.8.131.52; Mon, 16 Apr 2012 12:21:34 +0000
Received: from mail157-ch1 (localhost [127.0.0.1]) by
mail157-ch1-R.bigfish.com (Postfix) with ESMTP id 08F0934028D for
<email@example.com>; Mon, 16 Apr 2012 12:21:34 +0000 (UTC)
Received-SPF: pass (mail157-ch1: domain of janust.onmicrosoft.com designates
184.108.40.206 as permitted sender) client-ip=220.127.116.11; firstname.lastname@example.org;
helo=AMSPRD0510HT002.eurprd05.prod.outlook.com ;.outlook.com ;
Received: from mail157-ch1 (localhost.localdomain [127.0.0.1]) by
(MessageSwitch) id 133457889238635_1137; Mon, 16 Apr 2012 12:21:32 +0000
Received: from CH1EHSMHS024.bigfish.com
[10.43.68.230]) by mail157-ch1.bigfish.com (Postfix) with ESMTP id
EF52F3200B3 for <email@example.com>; Mon, 16 Apr 2012 12:21:31
Received: from AMSPRD0510HT002.eurprd05.prod.outlook.com (18.104.22.168) by CH1EHSMHS024.bigfish.com (10.43.70.24) with Microsoft SMTP Server (TLS) id 22.214.171.124; Mon, 16 Apr 2012 12:21:30 +0000
Received: from AMSPRD0510MB387.eurprd05.prod.outlook.com ([169.254.12.206]) by AMSPRD0510HT002.eurprd05.prod.outlook.com ([10.255.42.37]) with mapi id 14.16.0143.004; Mon, 16 Apr 2012 12:21:25 +0000
To: "'xxx' (firstname.lastname@example.org)" <xxx>
Thread-Topic: Testni sestanek
Date: Mon, 16 Apr 2012 12:21:25 +0000
Accept-Language: sl-SI, en-US
Content-Type: text/plain; charset="iso-8859-2"
It seems that the message was sent from an Office 365 mail account to an external mail account. Is your Outlook 2003 connecting to none Office 365 mailbox now? Please confirm this. If so, I think the result is normal. Other mail system may not be able to recognize the meeting format of Exchange messages.
The original message was sent from Outlook 2010 with Office 365 mail account to Outlook 2003 with regular non-exchange mail account.
So that means that Outlook 2003 can not receive meeting requests from exchange mail users / Office 365 users?
Whether you can get the meeting request normally doesn't depend on which client you are using, but for the mail servers. Non-exchange mail account may not be able to recognize the meeting request from an Exchange account, even if you have connected this account with Outlook, no matter Outlook 2003 or Outlook 2007.
So that means that non-exchange users can not receive meeting request from users who has exchange accounts (speaking about Outllok 2003)?
That's awkward because how could you know which users are using exchange account when you send meeting request outside of your firm?
Is there any other solution or suggestion?
Based on my experience, not all the non-exchange users cannot receive meeting request. At least, Windows Live Mail can receive meeting request from Exchange account properly. This may depend on the calendar function included in the mail system. Some type of calendars may not be able to recognize the meeting request from Exchange account. If it is possible, I suggest you change to another mail provider for the non-exchange users.
Thank you for your answer. The problem is that user with Office 365 account, who is sending out the meeting request, doesn't know what kind of mail client or server the recipient users are using.
I find this very strange because:
Outlook 2010, non-exchange - Outlook 2003, non-exchange WORKING
Outlook 2010, exchange - Outlook 2003, non-exchange DOES NOT WORKING
So if we start using Office 365 and exchange accounts, the meeting request is practically useless, because you will never know what kind of mail client or server the other side is using and you will never know it they received the meeting request or not, because if they are using non-exchange on Outlook 2003, they receive my meeting request into SPAM folder.
With other side I mean users outside our firm.
I understand this may cause a potential issue when the external recipients are using an email system which is incompatible with Exchange meeting request format. However, based on my experience, most of the meeting request should be sent internally. I would suggest you preparer a non-Exchange account for the external meeting request. Meanwhile, you can send us a feedback about this feature, hope this can be improved in the further.