[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 702
  • Last Modified:

Exchange 2013 Callender invite Issue ( You cannot forward an external meeting request in an Exchange Server 2013 environment )

HI Team

we are facing problem with Microsoft Exchange 2013 , problem is if we try to send calender invite to any one outside our network it goes as an email and not as an Calender Invite , we searched online and found out that this is a known issue Microsoft has even released updates for the same after checking out we found out that updates have already been applied and infect we are using a higher version then that was recommended   .

below is the link referred - http://support.microsoft.com/kb/2892464/en-us.

they recommend using Cumulative update 3 for Exchange and we are already using  - Servicepack1 Built 847.32.

We can still upgrade to Cumulative update 5 but it will not fix our problem as this issue must have been fixed in previous 2 Roll-ups , we are looking forward for your suggestions.

  • 5
  • 5
1 Solution
Jian An LimSolutions ArchitectCommented:
i can't find the kb you mention.
the kb 2902929 You cannot forward an external meeting request in an Exchange Server 2013 environment has nothing to do with your symptom.

do you have the message header of the email (that suppose to be calendar invite?)
PacificAliAuthor Commented:
Hi limjianan

sorry for late reply i was so busy with other issue did not get time to update this ticket.

as far as email haader is concerned please see below.


Received: from DB4PR05MB560.eurprd05.prod.outlook.com ( by
 DB3PR05MB553.eurprd05.prod.outlook.com ( with Microsoft SMTP
 Server (TLS) id 15.0.1005.10 via Mailbox Transport; Fri, 8 Aug 2014 08:57:55
Received: from DBXPR05CA004.eurprd05.prod.outlook.com ( by
 DB4PR05MB560.eurprd05.prod.outlook.com ( with Microsoft SMTP
 Server (TLS) id 15.0.995.14; Fri, 8 Aug 2014 08:57:55 +0000
Received: from DB3FFO11FD009.protection.gbl (2a01:111:f400:7e04::142) by
 DBXPR05CA004.outlook.office365.com (2a01:111:e400:9800::44) with Microsoft
 SMTP Server (TLS) id 15.0.1005.10 via Frontend Transport; Fri, 8 Aug 2014
 08:57:55 +0000
Received: from mail134.wdc04.mandrillapp.com ( by
 DB3FFO11FD009.mail.protection.outlook.com ( with Microsoft SMTP
 Server (TLS) id 15.0.990.10 via Frontend Transport; Fri, 8 Aug 2014 08:57:54
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=mandrill; d=ersg.co.uk;
 h=From:Subject:To:Message-Id:Date:MIME-Version:Content-Type; i=Ali@ersg.co.uk;
DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=mandrill; d=ersg.co.uk;
Received: from pmta05.wdc01.mailchimp.com ( by mail134.wdc04.mandrillapp.com id hsi8h41jvjgc for <vibhu@khan.vg>; Fri, 8 Aug 2014 08:57:53 +0000 (envelope-from <bounce-md_30107196.53e49111.v1-21cc5cd76fb54a658ba7e662f8d54276@mandrillapp.com>)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mandrillapp.com;
 i=@mandrillapp.com; q=dns/txt; s=mandrill; t=1407488273; h=From :
 Subject : To : Message-Id : Date : MIME-Version : Content-Type : From :
 Subject : Date : X-Mandrill-User : List-Unsubscribe;
From: Ali <Ali@ersg.co.uk>
Subject: test6
Return-Path: <bounce-md_30107196.53e49111.v1-21cc5cd76fb54a658ba7e662f8d54276@mandrillapp.com>
X-Originating-Ip: []
To: vibhu vibhu <vibhu@khan.vg>
Message-ID: <603ce44c84dd438883ed540f91970f70@ERSGExchange.ersgnetwork.loc>
Received: from [] by mandrillapp.com id 21cc5cd76fb54a658ba7e662f8d54276; Fri, 08 Aug 2014 08:57:53 +0000
X-Report-Abuse: Please forward a copy of this message, including all headers, to abuse@mandrill.com
X-Report-Abuse: You can also report abuse here: http://mandrillapp.com/contact/abuse?id=30107196.21cc5cd76fb54a658ba7e662f8d54276
X-Mandrill-User: md_30107196
Date: Fri, 8 Aug 2014 08:57:53 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="_av-vKdTCn-wpG9JLWHB5rJXeQ"
X-EOPAttributedMessage: 0
X-MS-Exchange-Organization-MessageDirectionality: Incoming
X-Forefront-Antispam-Report: CIP:;CTRY:US;IPV:NLI;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(6009001)(438002)(189002)(199002)(31966008)(83072002)(74502001)(564344004)(16796002)(956001)(946001)(87836001)(573454002)(81542001)(20776003)(106866001)(46102001)(74482001)(16236675004)(79102001)(74662001)(64706001)(99396002)(85852003)(95666004)(15395725005)(104766002)(92566001)(85306004)(107886001)(71186001)(4396001)(77096002)(50986999)(19580395003)(18206015026)(76482001)(83322001)(102836001)(229853001)(15202345003)(44976005)(54356999)(84326002)(16799955002)(80022001)(110136001)(77982001)(15975445006)(66066001)(110476001)(106466001)(81342001)(6806004)(19627405001)(21056001)(33646002)(24736002)(217283001)(108616003)(18926415006)(19627315001)(19607625011);DIR:INB;SFP:;SCL:1;SRVR:DB4PR05MB560;H:mail134.wdc04.mandrillapp.com;FPR:;MLV:sfv;PTR:mail134.wdc04.mandrillapp.com;MX:1;A:1;LANG:;
X-MS-Exchange-Organization-Network-Message-Id: a410a1eb-6f5b-41e1-e5b3-08d180fdfa53
X-Microsoft-Antispam: BCL:5;PCL:0;RULEID:(71001)
X-MS-Exchange-Organization-AVStamp-Service: 1.0
Received-SPF: Pass (protection.outlook.com: domain of mandrillapp.com
 designates as permitted sender)
 receiver=protection.outlook.com; client-ip=;
Authentication-Results: spf=pass (sender IP is
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-Organization-AuthSource: DB3FFO11FD009.protection.gbl
X-MS-Exchange-Organization-AuthAs: Anonymous

Please check attached Email if required its the same one for which we have copied header for.
Jian An LimSolutions ArchitectCommented:
sorry for the late reply

i think we need to do a pipeline tracing


this will give you some idea, is this change on submit (i.e. outlook decides) or through hub transport (i.e. exchange decide)
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

PacificAliAuthor Commented:
Thanks for your reply we will do the pipeline tracing and let you know this is through hub transport.

Jian An LimSolutions ArchitectCommented:
remember also do one internal as well for comparison
PacificAliAuthor Commented:
Hi limjianan

We have traced our problem is from our email relay service they have conformed that this is a known problem from their end so we can close this case now, thanks for your time .

Jian An LimSolutions ArchitectCommented:
Well done :)
hopefully the pipeline tracing have pin pointed the issues
PacificAliAuthor Commented:
I've requested that this question be deleted for the following reason:

Did Not find a solution hear solved us on our own
Jian An LimSolutions ArchitectCommented:
I hope at least you can accept the answer given that this at least prove that it is not exchange 2013 causing the trouble and pipeline tracing confirmed the email did not change before leaving exchange 2013 environment.
PacificAliAuthor Commented:
Thanks for your Help


Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now