No one has responded to this discussion for at least a year, so this information may be out of date. If you're looking for information about this topic, please search for a more recent discussion or post a new question.

Outlook Meeting Request recieved as scrambled / plain text

This question is answered This question is answered

Hi,


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:


-----Original Message-----
From: xxxx
Sent: xxxxxxxxxx
To: xxxxxxxxxxxxxxx

...

...

...

CAgSG9hcmRpbmcNCuKAoiAgICAgICBTaXRlIEFjY2Vzcw0KRGF0ZSBhbmQgdGltZSAgIFRodXJz
ZGF5LCAwNyBKdWx5IDIwMTEgYXQgMTA6MDBhbQ0KVmVudWUgICBQUFAtUldBIE1haW4gQ29uZmVy
ZW5jZSBSb29tDQoNClBsZWFzZSBjb25maXJtIHlvdXIgYXR0ZW5kYW5jZS4gICBUaGFua


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.


Any idea?

Thank you all for your help.

Verified Answer
  • Hi Matjaz,

    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.

    Thanks,
    Grace Shi

     

All Replies
  • 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

    Thanks,
    Reken Liu

  • 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,

    Matjaz




  • Hi Matjaz,

    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.

    Thanks,
    Reken Liu

  • Hi Matjaz,

    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?

    Thanks,
    Reken Liu

  • Hi Reken,

    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.

    Any suggestion?

    Thank you and br,

    Matjaz

  • Hi Matjaz,

    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.

    Thanks,
    Grace Shi

     

  • 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?

    Thanks,

    Matjaz Sustersic

  • Hi Matjaz,

    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.

    Thanks,
    Reken Liu

  • Hi Matjaz,

    Is there any other assistance needed here?

    Thanks,
    Reken Liu

  • 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?

    Thank you and br,

    Matjaz

  • Hi Matjaz,

    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.

    Thanks,
    Reken Liu

  • Hi Matjaz,

    Have you tested it and does the meeting request work well in Outlook 2003 now?

    Thanks,
    Reken Liu

  • Hi Reken Liu


    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.


    -----Original Message-----

    From: Matjaž Šušteršič [mailto:matjaz.sustersic@janust.onmicrosoft.com]

    Sent: Monday, April 16, 2012 2:21 PM

    To: 'Dejan' (xxx@janustrade.si)

    Subject: Testni sestanek

    Return-path: <matjaz.sustersic@janust.onmicrosoft.com>

    Envelope-to: xxx@janustrade.si

    Delivery-date: Mon, 16 Apr 2012 14:21:42 +0200

    Received: from mail by juni.spletnahisa.net with spam-scanned (Exim 4.76)

                    (envelope-from <matjaz.sustersic@janust.onmicrosoft.com>)

                    id 1SJkw4-000IUg-HE

                    for xxx@janustrade.si; 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-Level:

    X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00,HTML_MESSAGE,

                    RCVD_IN_DNSWL_LOW,SPF_PASS,TVD_SPACE_RATIO autolearn=ham

    version=3.3.2

    Received: from ch1ehsobe005.messaging.microsoft.com ([216.32.181.185]

    helo=ch1outboundpool.messaging.microsoft.com)

                    by juni.spletnahisa.net with esmtps (TLSv1:AES128-SHA:128)

                    (Exim 4.76)

                    (envelope-from <matjaz.sustersic@janust.onmicrosoft.com>)

                    id 1SJkw4-000IUY-6b

                    for xxx@janustrade.si; 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  14.1.225.23; 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

     <xxx@janustrade.si>; Mon, 16 Apr 2012 12:21:34 +0000 (UTC)

    X-SpamScore: -2

    X-BigFish: PS-2(zzc89bhec9Qc857hzz1202h1957ozz8275bhz2fh2a8h668h839hd25h)

    X-Forefront-Antispam-Report:

    CIP:157.56.248.53;KIP:(null);UIP:(null);IPV:NLI;H:AMSPRD0510HT002.eurprd05.p

    rod.outlook.com;RD:none;EFVD:NLI

    Received-SPF: pass (mail157-ch1: domain of janust.onmicrosoft.com designates

    157.56.248.53 as permitted sender) client-ip=157.56.248.53; envelope-from=matjaz.sustersic@janust.onmicrosoft.com;

    helo=AMSPRD0510HT002.eurprd05.prod.outlook.com ;.outlook.com ;

    Received: from mail157-ch1 (localhost.localdomain [127.0.0.1]) by

    mail157-ch1

     (MessageSwitch) id 133457889238635_1137; Mon, 16 Apr 2012 12:21:32 +0000

     (UTC)

    Received: from CH1EHSMHS024.bigfish.com

    (snatpool2.int.messaging.microsoft.com

     [10.43.68.230])                by mail157-ch1.bigfish.com (Postfix) with ESMTP id

     EF52F3200B3    for <xxx@janustrade.si>; Mon, 16 Apr 2012 12:21:31

     +0000 (UTC)

    Received: from AMSPRD0510HT002.eurprd05.prod.outlook.com (157.56.248.53) by  CH1EHSMHS024.bigfish.com (10.43.70.24) with Microsoft SMTP Server (TLS) id  14.1.225.23; 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

    From: =?iso-8859-2?Q?Matja=BE_=A9u=B9ter=B9i=E8?=

                    <matjaz.sustersic@janust.onmicrosoft.com>

    To: "'xxx' (xxx@janustrade.si)" <xxx>

    Subject: Testni sestanek

    Thread-Topic: Testni sestanek

    Thread-Index: Ac0by2Qg8sxUH7FsSy6+QKX/RECgFAAAAzmA

    Date: Mon, 16 Apr 2012 12:21:25 +0000

    Message-ID:

    <AEC54DBE716E7A47B633060CCADCEB96D4C782@AMSPRD0510MB387.eurprd05.prod.outloo

    k.com>

    Accept-Language: sl-SI, en-US

    Content-Language: sl-SI

    X-MS-Has-Attach:

    X-MS-TNEF-Correlator:

    x-originating-ip: [89.212.56.62]

    Content-Type: multipart/alternative;

                   

    boundary="_000_AEC54DBE716E7A47B633060CCADCEB96D4C782AMSPRD0510MB387eu_"

    MIME-Version: 1.0

    X-OriginatorOrg: janust.onmicrosoft.com

    X-EsetId: 4B3A572F63325669543C577D69611A34

    --_000_AEC54DBE716E7A47B633060CCADCEB96D4C782AMSPRD0510MB387eu_

    Content-Type: text/plain; charset="iso-8859-2"

    Content-Transfer-Encoding: quoted-printable


  • Hi Matjaz,

    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.

    Thanks,
    Reken Liu

  • Hi Reken,

    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?

    Thanks,

    Matjaz