Problem with forwarding messages on mobile phones using Mail for Exchange (MfE) (Network Steve Forum)

Problem with forwarding messages on mobile phones using Mail for Exchange (MfE)

When a "forward" option is selected for a message in inbox, then a forwarded message can be added inline (as text) or as attached file. The same MfE client is forwarding a message differently, depending on the MS Exchange email account. Example 1. MS Exchange server: mail.rosehavenhomes.com Email account: ms@rosehavenhomes.com Mail for Exchange on Symbian Anna and on Android ("Exchange ExMail" app by AECorp) is forwarding emails as attached files. It is impossible to edit the content of forwarded message. If the forwarded message is sent to e.g. gmail eccount, then such atached email is available as file noname.eml in raw format (with headers). Example 2. MS Exchange server: dbxprd0710.outlook.com Email account: <my-user-name>@vertu.com Mail for Exchange on Symbian Anna and on Android ("Exchange ExMail" app by AECorp) is forwarding emails inline, as a text, i.e. the recipient of forwrded messages can see the content of the message in text format (the same email message was tested as in Example 1). It is impossible to edit the content of forwarded message (this is not a problem). Examples listed above prove that the same email client (on Symbian and Android) can handle the "forward" action differently, depending on the MS Exchange account. Questions: (1) What are the conditions checked by MfE clients before tking the decision whether to forward a message as attachment, or inline? There is no possibility to set-up a forwarded message format (in-line or as attachement), like it is possible in Outlook PC application (see e.g. http://office.microsoft.com/en-us/outlook-help/change-how-the-original-message-appears-in-replies-and-forwards-HA102087334.aspx) (2) Does MS Exchange contain a configurable policy how to forward a message (in-line or as attachment) ? (3) Does the MfE client allow to set the forwarding option (inline or "as attachemnt") via the MfE Appliction Progrmming Interface (API) ? The MfE client is integrated on Symbian Anna as a binary file, developed by third-party supplier (probably Microsoft). No info whether a similar development model works in case of Android app "Exchange ExMail" by AECorp. This is an example of MfE client specification: http://symbianworld.org/1365-mail-for-exchange-version-29158-available/ (for Symbian) Below is an example of file noname.eml, being sent as an attachment by MfE client on Symbian Anna (MS Exchange server: mail.rosehavenhomes.com) --- File noname.eml --- Received: from am1outboundpool.messaging.microsoft.com ([213.199.154.209]) by mx-out.melroseinvestments.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 18 Jul 2012 04:19:45 -0400 Received: from mail110-am1-R.bigfish.com (10.3.201.232) by AM1EHSOBE003.bigfish.com (10.3.204.23) with Microsoft SMTP Server id 14.1.225.23; Wed, 18 Jul 2012 08:19:54 +0000 Received: from mail110-am1 (localhost [127.0.0.1]) by mail110-am1-R.bigfish.com (Postfix) with ESMTP id AF27332022C for <mg@rosehavenhomes.com>; Wed, 18 Jul 2012 08:19:54 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.253.197;KIP:(null);UIP:(null);IPV:NLI;H:DBXPRD0710HT001.eurprd07.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -10 X-BigFish: PS-10(zzfadRc85fhzz1202hzz8275bh8275dhz2fh2a8h668h839hd25hf0ah107ah) Received-SPF: pass (mail110-am1: domain of vertu.com designates 157.56.253.197 as permitted sender) client-ip=157.56.253.197; envelope-from=pawel.szyszuk@vertu.com; helo=DBXPRD0710HT001.eurprd07.prod.outlook.com ;.outlook.com ; Received: from mail110-am1 (localhost.localdomain [127.0.0.1]) by mail110-am1 (MessageSwitch) id 1342599592410985_30743; Wed, 18 Jul 2012 08:19:52 +0000 (UTC) Received: from AM1EHSMHS014.bigfish.com (unknown [10.3.201.243]) by mail110-am1.bigfish.com (Postfix) with ESMTP id 590FC2200E0 for <mg@rosehavenhomes.com>; Wed, 18 Jul 2012 08:19:52 +0000 (UTC) Received: from DBXPRD0710HT001.eurprd07.prod.outlook.com (157.56.253.197) by AM1EHSMHS014.bigfish.com (10.3.207.152) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 18 Jul 2012 08:19:52 +0000 Received: from DBXPRD0710MB394.eurprd07.prod.outlook.com ([169.254.3.231]) by DBXPRD0710HT001.eurprd07.prod.outlook.com ([10.255.79.164]) with mapi id 14.16.0175.005; Wed, 18 Jul 2012 08:19:49 +0000 From: "Szyszuk Pawel (Vertu/ChurchCrookham)" <pawel.szyszuk@vertu.com> To: "mg@rosehavenhomes.com" <mg@rosehavenhomes.com> Subject: Test 2 Thread-Topic: Test 2 Thread-Index: Ac1kvijIEM7RemLZRFWBY4e8s4KLHQ== Date: Wed, 18 Jul 2012 08:19:48 +0000 Message-ID: <6A3D3CB29C77A6499203626D3F78ED8401E670@DBXPRD0710MB394.eurprd07.prod.outlook.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-headerinfofordlp: None x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None; x-tituslabs-classificationhash-30: lRdGDfGIN8wlCPRly3WQX9Ls8V1nHQwRqPVPAEKfTxiKGF9tG4nM+ysGtnDkzAnmu3Ue64WUCWXBZyBEyRpqen02dmljxCLOcfSRAT3xVQuWn8rbk8iTv1kXtdS17t9xnQAezIQWQZIiFCxdVEV4EooEY4reHrMDZZZ2+cmIJcNepaZqMsXi7TwDrDEhBxxLisLaNw9n5wpT+oaNyZz3tQ== x-titus-version: 3.3.8.1 x-originating-ip: [192.100.107.39] Content-Type: multipart/alternative; boundary="_000_6A3D3CB29C77A6499203626D3F78ED8401E670DBXPRD0710MB394eu_" MIME-Version: 1.0 Return-Path: pawel.szyszuk@vertu.com X-OriginatorOrg: vertu.com X-OriginalArrivalTime: 18 Jul 2012 08:19:45.0006 (UTC) FILETIME=[16A490E0:01CD64BE] --_000_6A3D3CB29C77A6499203626D3F78ED8401E670DBXPRD0710MB394eu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dfgs dghd This message and any attachment is intended only for the use of the individ= ual or entity to which it is addressed and may contain information that is = privileged, confidential and exempt from disclosure. If the reader of this= message is not the intended recipient, or an employee or agent responsible= for delivering the message to the intended recipient, you are hereby notif= ied that any dissemination, distribution or copying of this communication i= s strictly prohibited. If you have received this communication in error, pl= ease accept our apology and we should be obliged if you would contact the s= ender. Please note that any views or opinions presented in this email are solely t= hose of the sender and do not necessarily represent those of Vertu. The com= pany therefore does not accept liability for any errors or omissions in the= contents of this message, or which arise as a result of e-mail transmissio= n. --_000_6A3D3CB29C77A6499203626D3F78ED8401E670DBXPRD0710MB394eu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span lang=3D"EN-GB">Dfgs dghd<o:p></o:p></span></p>= </div> <br clear=3Dall> This message and any attachment is intended only for the u= se of the individual or entity to which it is addressed and may contain inf= ormation that is privileged, confidential and exempt from disclosure. If t= he reader of this message is not the intended recipient, or an employee or = agent responsible for delivering the message to the intended recipient, you= are hereby notified that any dissemination, distribution or copying of thi= s communication is strictly prohibited. If you have received this communica= tion in error, please accept our apology and we should be obliged if you wo= uld contact the sender.=0D =0D Please note that any views or opinions presented in this email are solely t= hose of the sender and do not necessarily represent those of Vertu. The com= pany therefore does not accept liability for any errors or omissions in the= contents of this message, or which arise as a result of e-mail transmissio= n.=0D </body> </html> --_000_6A3D3CB29C77A6499203626D3F78ED8401E670DBXPRD0710MB394eu_--

July 18th, 2012 7:22am

It may not be the device at all, but how the two Exchange systems differ in configuration. The first thing to check/try is look at your remote domains in Exchange and see if you have a specific domain setup for the ones that are working, if not, check the default domain setting, click on message format, then check the Exchange rich-text format section, I am thinking the one that is working is set to Never Use and the one that isnt (attaches forwards) is set to 'Determined by individual user settings'. Check that out and let me know what you see.

Free Windows Admin Tool Kit Click here and download it now

August 22nd, 2012 11:19am

This topic is archived. No further replies will be accepted.