Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
[exchange 2013] Problem with multipart/mixed message

Answered [exchange 2013] Problem with multipart/mixed message

  • Monday, December 24, 2012 10:37 AM
     
     
    Sign In to Vote
    0

    Hi,

      After a brand new installation of Exchange 2013 I have problem with multipart/mixed messages:

    some emails that was correctly handled by the old 2007 Exchange are now "broken" and it seems to be a MIME wrong decode..

    this is the header of a message received with the old Exchange server

    Received: from was1-mh251.smtproutes.com (174.36.154.126) by
     SERVER-MAIL.iptechnology.it (192.168.50.6) with Microsoft SMTP Server id
     8.3.279.5; Thu, 6 Dec 2012 19:33:01 +0100
    X-Katharion-ID: 1354818768.26441.was1-mh251 (12.0W)
    Return-Path: <statistics@reporting.smtproutes.com>
    Received: from was1-cp021.smtproutes.com ([10.21.46.88]) by
       was1-mh251.smtproutes.com [(10.20.102.93)] with ESMTP via TCP; 06 Dec
       2012 12:32:48 -0600
    Received: from was1-cp021.smtproutes.com (was1-cp021.smtproutes.com
     [174.36.154.80]) by was1-cp021.smtproutes.com (Postfix) with ESMTP id
     318BBB955B for <coelli@iptechnology.it>; Thu,  6 Dec 2012 12:32:45 -0600
     (CST)
    X-Katharion-ID: 1354818762.83562.was1-cp021 (12.0W)
    Date: Thu, 6 Dec 2012 12:32:42 -0600
    From: Digest Report <statistics@reporting.smtproutes.com>
    To: coelli@iptechnology.it
    Subject: Your Message Digest: coelli@iptechnology.it
    Message-ID: <1354818762.hae83zru@1354818762.83562.was1-cp021>
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
     boundary="_e00094c7-df45-4c8c-a227-cb431141090d_"


    and that one is the broken email header received with Exchange 2013

    Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
     EXCHANGE-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
     15.0.516.32 via Mailbox Transport; Mon, 17 Dec 2012 18:47:49 +0100
    Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
     exchange-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
     15.0.516.32; Mon, 17 Dec 2012 18:47:48 +0100
    Received: from was1-mh254.smtproutes.com (174.36.154.129) by
     EXCHANGE-01.iptech.local (192.168.50.4) with Microsoft SMTP Server id
     15.0.516.32 via Frontend Transport; Mon, 17 Dec 2012 18:47:47 +0100
    X-Katharion-ID: 1355766453.92161.was1-mh254 (12.0W)
    Return-Path: <statistics@reporting.smtproutes.com>
    Received: from was1-cp021.smtproutes.com ([10.21.46.88]) by
       was1-mh254.smtproutes.com [(10.20.102.99)] with ESMTP via TCP; 17 Dec
       2012 11:47:33 -0600
    Received: from was1-cp021.smtproutes.com (was1-cp021.smtproutes.com
     [174.36.154.80]) by was1-cp021.smtproutes.com (Postfix) with ESMTP id
     177FCB95A1 for <coelli@iptechnology.it>; Mon, 17 Dec 2012 11:47:33 -0600
     (CST)
    X-Katharion-ID: 1355766451.94043.was1-cp021 (12.0W)
    Date: Mon, 17 Dec 2012 11:47:31 -0600
    From: Digest Report <statistics@reporting.smtproutes.com>
    To: <coelli@iptechnology.it>
    Subject: Your Message Digest: coelli@iptechnology.it
    Message-ID: <1355766451.hatwc91h@1355766451.94043.was1-cp021>
    MIME-Version: 1.0
    Content-Type: text/plain
    X-MS-Exchange-Organization-Network-Message-Id: 62d785b9-0645-413d-ed81-08cfaa95c35c
    X-MS-Exchange-Organization-AuthSource: exchange-01.iptech.local
    X-MS-Exchange-Organization-AuthAs: Anonymous


    as you can see the second one is wrongly reported as "Content-Type: text/plain"

    I tried to change the content conversion as described here:

    http://technet.microsoft.com/en-us/library/bb232174.aspx


    but nothing has changed..

    do you have any suggestion?


    thank you

    Alessandro

     

All Replies

  • Wednesday, December 26, 2012 9:56 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hello Alessandro,

    Thank you for your post.

    This is a quick note to let you know that we are performing research on this issue.

    Happy New Year!

    Simon Wu
    TechNet Community Support

     
  • Thursday, December 27, 2012 6:22 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    The content conversion options that you set in the article you listed is for external recipients. That means when you send outbound emails, how the email will be convert to.

    When receiving emails, Exchange server will not change the message’s formatting. The only conversion happens is MAPI conversion which should not change the Content-Type.

    I noticed that the two messages you pasted have different mail flow routing.

    The old one:

    was1-cp021.smtproutes.com -> was1-mh251.smtproutes.com -> your old Exchange 2007 server

    The broken one:

    was1-cp021.smtproutes.com -> was1-mh254.smtproutes.com -> your new Exchange 2010 server

    The issue should be caused by sender side and I suppose the problem is exists on “was1-mh254.smtproutes.com”.

    You can try to have more tests to indicate it.

    Thanks,

    Da Xu

     
  • Thursday, December 27, 2012 10:56 PM
     
     
    Sign In to Vote
    0

    Hi Xu and Simon_wu, thanks for your  interest.

    The problem it's not outside exchange server but i'm sure that it's inside it.. 

    the same problem appear also in other email that I receive perfectly before  and the only thing that those email have equal is the multipart/mixed content..

    We have a scanner that send email trought SMTP on port 25 of the exchange, until it work with exchange 2007 the email had a multipart/mixed content wrotten in header an all works fine, now (and it's not possible that the printer have chaged it) the header report a Content-Type: text/plain..

    NEW HEADER (exchange 2013):

    Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
     EXCHANGE-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
     15.0.516.32 via Mailbox Transport; Sat, 22 Dec 2012 20:10:20 +0100
    Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
     exchange-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
     15.0.516.32; Sat, 22 Dec 2012 20:10:18 +0100
    Received: from RICOH (192.168.50.150) by EXCHANGE-01.iptech.local
     (192.168.50.4) with Microsoft SMTP Server id 15.0.516.32 via Frontend
     Transport; Sat, 22 Dec 2012 20:10:11 +0100
    From: <scanner@iptechnology.it>
    Subject: Scansione da Ricoh 171
    To: Coelli <coelli@iptechnology.it>
    Date: Sat, 22 Dec 2012 20:08:18 +0100
    Message-ID: <20121222200818PI.DCSML-S000160000.002673037354@192.168.50.150>
    MIME-Version: 1.0
    Content-Type: text/plain
    Return-Path: scanner@iptechnology.it
    X-MS-Exchange-Organization-Network-Message-Id: ce8e2367-55ff-4603-d379-08cfae8f1da7
    X-MS-Exchange-Organization-AuthSource: exchange-01.iptech.local
    X-MS-Exchange-Organization-AuthAs: Anonymous

    OLD HEADER (EXCHANGE 2007)

    Received: from RICOH ([192.168.50.150])        by SERVER-MAIL.iptechnology.it (192.168.50.6) with Microsoft SMTP Server id 8.3.279.5; Sat, 1 Dec 2012 09:21:40 +0100        for <coelli@iptechnology.it>;
     Sat, 01 Dec 2012 09:21:40 +0100
    From: <scanner@iptechnology.it>
    Subject: Scansione da Ricoh 171
    To: "Coelli" <coelli@iptechnology.it>
    Date: Sat, 1 Dec 2012 09:19:42 +0100
    Message-ID: <20121201091942W1.DCSML-S000210000.002673037354@192.168.50.150>
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
    boundary="_cdbbea60-3585-498c-b628-d8a17992135b_"
    Return-Path: scanner@iptechnology.it

    thanks

     
  • Friday, December 28, 2012 4:35 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    If this issue is always reproducible, you can enable Pipeline Tracing on your Exchange 2013 mailbox server. Then, check the tracing result one by one to see if any agent changes the formatting.

    For pipeline tracing, you can refer to following article. It still apply for Exchange 2013.

    Using Pipeline Tracing to Diagnose Transport Agent Problems

    Thanks,

    Da Xu

     
  • Friday, January 04, 2013 6:53 PM
     
     
    Sign In to Vote
    0

    Hi! I haven't been able to do a Pipeline Trace, but I can confirm that our fresh Exchange 2013 setup behaves the same way with scanned documents from our Ricoh scanners. Files are correctly received on Exchange 2012 and Domino 8.5.3, but Exchange incorrectly receives them as "plain text".

    Kind regards,

    Ivar

     
  • Thursday, January 10, 2013 11:36 AM
     
     
    Sign In to Vote
    0

    hi

    I enabled the pipeline tracing and the resul is:

    SmtpReceive0001.eml

    ------------------------------------

    X-CreatedBy: MessageSnapshot-Begin injected headers
    X-MessageSnapshot-UTC-Time: 2013-01-10T11:13:48.504Z
    X-MessageSnapshot-Protocol-Id: 08CFAE8E76B5016D;2013-01-10T11:13:48.347Z;1
    X-MessageSnapshot-Source: OnEndOfHeaders,Inbound Trust Agent
    X-Sender: scanner@iptechnology.it
    X-Receiver: coelli@iptechnology.it
    X-EndOfInjectedXHeaders: MessageSnapshot-End injected headers
    Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
     exchange-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
     15.0.516.32; Thu, 10 Jan 2013 12:13:48 +0100
    Received: from RICOH (192.168.50.150) by EXCHANGE-01.iptech.local
     (192.168.50.4) with Microsoft SMTP Server id 15.0.516.32 via Frontend
     Transport; Thu, 10 Jan 2013 12:13:48 +0100
    From: scanner@iptechnology.it
    Subject: Scansione da Ricoh 171
    To: "Coelli" <coelli@iptechnology.it>
    Date: Thu, 10 Jan 2013 12:11:41 +0100
    Message-ID: <20130110121141H2.DCSML-S000200000.002673037354@192.168.50.150>
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
     boundary="_198bc84b-4c4b-4394-9641-975573ec831c_"
    Return-Path: scanner@iptechnology.it
    X-MS-Exchange-Organization-OriginalArrivalTime: 10 Jan 2013 11:13:48.2698
     (UTC)
    X-MS-Exchange-Forest-ArrivalHubServer: EXCHANGE-01.iptech.local
    X-MS-Exchange-Organization-OriginalClientIPAddress: 192.168.50.150
    X-MS-Exchange-Organization-OriginalServerIPAddress: 192.168.50.4
    X-MS-Exchange-Organization-Cross-Premises-Headers-Processed: exchange-01.iptech.local
    X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=EXCHANGE-01.iptech.local:TOTAL=0;2013-01-10T11:13:48.332Z
    X-MS-Exchange-Organization-AuthSource: exchange-01.iptech.local
    X-MS-Exchange-Organization-AuthAs: Anonymous

    ------------------------------------

    SmtpReceive0002.eml

    ------------------------------------

    X-CreatedBy: MessageSnapshot-Begin injected headers
    X-MessageSnapshot-UTC-Time: 2013-01-10T11:13:48.504Z
    X-MessageSnapshot-Protocol-Id: 08CFAE8E76B5016D;2013-01-10T11:13:48.347Z;1
    X-MessageSnapshot-Source: OnEndOfData
    X-Sender: scanner@iptechnology.it
    X-Receiver: coelli@iptechnology.it
    X-EndOfInjectedXHeaders: MessageSnapshot-End injected headers
    Received: from EXCHANGE-01.iptech.local (192.168.50.4) by
     exchange-01.iptech.local (192.168.50.4) with Microsoft SMTP Server (TLS) id
     15.0.516.32; Thu, 10 Jan 2013 12:13:48 +0100
    Received: from RICOH (192.168.50.150) by EXCHANGE-01.iptech.local
     (192.168.50.4) with Microsoft SMTP Server id 15.0.516.32 via Frontend
     Transport; Thu, 10 Jan 2013 12:13:48 +0100
    From: <scanner@iptechnology.it>
    Subject: Scansione da Ricoh 171
    To: "Coelli" <coelli@iptechnology.it>
    Date: Thu, 10 Jan 2013 12:11:41 +0100
    Message-ID: <20130110121141H2.DCSML-S000200000.002673037354@192.168.50.150>
    MIME-Version: 1.0
    Content-Type: text/plain
    Return-Path: scanner@iptechnology.it
    X-MS-Exchange-Organization-OriginalArrivalTime: 10 Jan 2013 11:13:48.2698
     (UTC)
    X-MS-Exchange-Forest-ArrivalHubServer: EXCHANGE-01.iptech.local
    X-MS-Exchange-Organization-OriginalClientIPAddress: 192.168.50.150
    X-MS-Exchange-Organization-OriginalServerIPAddress: 192.168.50.4
    X-MS-Exchange-Organization-Cross-Premises-Headers-Processed: exchange-01.iptech.local
    X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=EXCHANGE-01.iptech.local:TOTAL=0;2013-01-10T11:13:48.332Z
    X-MS-Exchange-Organization-AuthSource: exchange-01.iptech.local
    X-MS-Exchange-Organization-AuthAs: Anonymous
    X-MS-Exchange-Organization-Network-Message-Id:
     8f7062b4-ca0c-403a-ec62-08cfbd3ab29e

    This is a multi-part message in MIME format.
    --DC_BOUND_PRE_<1357816301.002673037354>
    Content-Type: text/plain; charset=ISO-8859-1
    Content-Transfer-Encoding: quoted-printable

    ------------------------------------

     

    as you can see when the X-MessageSnapshot-Source change from OnEndOfHeaders,Inbound Trust Agent to OnEndOfData the Content-Type change from multipart/mixed to  text/plain

    Why?

     

    thanks

    Alessandro

     
  • Tuesday, January 15, 2013 8:42 AM
     
     
    Sign In to Vote
    0

    Hi, I can confirm that we are also experiencing this problem. Messages with PDF sent from Richo scanners gets changed to text/plain

     
  • Tuesday, January 15, 2013 11:21 AM
     
     
    Sign In to Vote
    0

    yes, but it's not only a Ricoh problem.. I've got also other email with the same problem.. for example the GFI MAX digest report have the same sistematically issue

    Alessandro

     
  • Friday, January 18, 2013 9:18 AM
     
     
    Sign In to Vote
    0

    Hello there, sorry to jump in on this thread but I am having the same problem with a Ricoh Aficio MP C2500 and Exchange 2013.

    Our mail passes through a Barracuda SPAM Filter before hitting Exchange 2013.

     I thought it was a Barracuda problem and worked with support but I was able to download the message and attachment successfully from the logs and open the PDF etc.

    The same scanned message sent to my Office 365 account was fine to open also.

    Interestingly, when I forwarded the message from Office 365 to Exchange 2013 the message was fine. Unfortunately this was only a test as my client needs to scan direct into Exchange 2013.

    Has anyone had any success with this?

    Cheers

    Paul

     
  • Friday, January 18, 2013 12:54 PM
     
     Proposed Answer
    Sign In to Vote
    0

    I can confirm that by forwarding from any other mail server to Exchange 2013, the problem disappears.

    But even more importantly, I have received a respons from Microsoft on the issue, in short:

    "This is a case where E2013 is being stricter than previous version regarding BNF notation in RFC 2046.  See BNF notation in RFC 2046 http://www.ietf.org/rfc/rfc2046.txt (...) This bug is due to be fixed in RU1 which will most likely be released sometime in February."

    Hurrah. Patience is a virtue and all that...

    - Ivar

    • Proposed As Answer by KANFA IT Friday, January 18, 2013 12:59 PM
    •  
     
  • Wednesday, January 23, 2013 6:44 PM
     
     
    Sign In to Vote
    0

    Hi,

    Same problem when scanning from CANON iR1025.

     
  • Wednesday, February 20, 2013 6:06 PM
     
     
    Sign In to Vote
    0
    Has anyone seen ANY information about RU1 for Exchange 2013 or any workaround on this issue?  This issue is affecting our SPAM message digests being sent to our users and is making them virtually useless. 
     
  • Wednesday, February 20, 2013 10:08 PM
     
     
    Sign In to Vote
    0

    I too am having the exact same issue. Exchange 2013 and Ricoh Scanner. The messages get stripped.

     
  • Thursday, February 21, 2013 4:27 PM
     
     
    Sign In to Vote
    0

    Same problem here with a Ricoh MF C2051 and Exchange 2013. Hope will
    come soon the RU1 and fix also the other problems which exists with
    Exchange 2013.

    Edit: mh, just saw here that there will be no RU's anymore for Exchange 2013. The first CU is target for 2013 Q1. Looks like we've to wait longer till this problem is fixed.


    • Edited by mabau Friday, February 22, 2013 8:23 AM
    • Edited by mabau Friday, February 22, 2013 8:23 AM
    •  
     
  • Tuesday, February 26, 2013 6:46 PM
     
     
    Sign In to Vote
    0
    Anyone found any workaround with Message Digests from GFI that are affected by this issue?  Besides having the user's log into the GFI site to retrieve the Message Digests.  I am wondering if anyone has found a work around with any "non-supported" fix as Microsoft has not acknowledged this issue and provided no concrete date on the first RU or CU. 
     
  • Tuesday, March 05, 2013 5:15 AM
     
     Proposed Answer
    Sign In to Vote
    0
    Hi Everyone,
    We just had this issue with a client where we deployed Exchange 2013. Have a solution for you.

    You have to create a custom receive connector in Exchange 2013 for the IP addresses of the local copiers. You then remove all authentication mechanisms and check only anonymous users for permissions group (see attachment for details).

    How to create a custom receive connector
    technet.microsoft.com/en-us/library/jj657467(v=exchg.150).aspx

    After you do this boom you receive the scan to email message with the PDF attachment.

    Keep in mind this works for internal copiers only.
     
  • Thursday, March 07, 2013 3:40 PM
     
     
    Sign In to Vote
    0
    Affinity Managed IT, i tried your solution and did not work. Any suggestions?
     
  • Tuesday, March 12, 2013 4:13 PM
     
     
    Sign In to Vote
    0

    Thanks for the information Affinity.  For our situation, this is happening with messages coming in from our external GFI SPAM system.

    Has anyone seen ANY information from Microsoft on the release of an update for Exhchange 2013 that addresses this issue?  It seems very odd that the only recognition of this issue is on this blog and Microsoft has not released any publication regarding this issue.  Please let me know if anyone has found any information to the contrary or any information regarding a patch schedule for Exchange 2013.  - Thanks

     
  • Wednesday, April 03, 2013 7:14 AM
     
     Proposed Answer
    Sign In to Vote
    0
    I had the same problem, after installing Exchange CU1 that got released yesterday the problem is now gone.
    • Proposed As Answer by Vidar Andersen Wednesday, April 03, 2013 7:15 AM
    •  
     
  • Wednesday, April 03, 2013 1:33 PM
     
     
    Sign In to Vote
    0
    I had the same problem, after installing Exchange CU1 that got released yesterday the problem is now gone.

    Perfect!

    For me too! :)


     
  • Tuesday, April 09, 2013 5:54 AM
     
     
    Sign In to Vote
    0

    Exchange 2013 CU1 fixed the problem.

    Reserve some time for the update, it tooks at me per installation around 1-2 hours.