Environment:

• Exchange 2013 with Rollup 1 on Win 2008 R2 Server
• Multiple domains per server

Problematic Area:

• Read receipt

User Configuration:

• SMTP-Address: mike.meyer@test.com
• Display Name: Mike

Problem description:

• User mike confirms to send a read receipt to the mails sender)
• Mails sender gets the read receipt from Mike (mike.meyer@test.com) on behalf of mike@invalid.domain

Where is exchange picking up that invalid.domain and how can I change it to pick the usual SMTP Address?

Hi, This happens on different clients (Outlook/Webmail/etc.). So that cannot be the problem.

Hi,

Please clear up the nickname cache on the problematic client:

http://www.slipstick.com/outlook/email/understanding-outlooks-autocomplete-cache-nk2/

Thanks,

Hi,

we've got the same problem.

I think it's down to Exchange 2013 not sending a properly formatted 'From:' header when it sends the read receipt.

Headers from Exchange 2013: (domains / IPs changed!)

Received: from exch2013.domain.co.uk (ipv4addr) by
 exch2013.domain.co.uk (ipv4addr) with Microsoft SMTP Server (TLS) id
 15.0.712.22; Thu, 25 Jul 2013 10:55:19 +0100
Received: from exch2013.domain.co.uk ([ipv6addr]) by
 exch2013.domain.co.uk ([ipv6addr]) with mapi id
 15.00.0712.012; Thu, 25 Jul 2013 10:55:19 +0100
From: Administrator
To: Remote User <Remote.User@remotedomain.co.uk>
Subject: Read: test 7
Thread-Topic: test 7
Thread-Index: Ac6JHQB44HBWnVEdQ1+FuHdMlR61kw==
Sender: Administrator <Administrator@domain.co.uk>
Date: Thu, 25 Jul 2013 09:55:19 +0000
Message-ID: <e0e1116282074780b4969a3ce3967560@exch2013.domain.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/report;
        boundary="_000_e0e1116282074780b4969a3ce3967560exch2013domainlocal_";
        report-type=disposition-notification
MIME-Version: 1.0

Headers from Exchange 2010 for comparison:

Received: from exch2010.domain2.co.uk ([ipv4addr]) by
 exch2010.domain2.co.uk with Microsoft SMTPSVC(6.0.3790.4675);
         Thu, 25 Jul 2013 13:53:54 +0100
Received: from exch2010.domain2.co.uk ([ipv6addr]) by
 exch2010.domain2.co.uk ([ipv6addr]) with mapi id
 14.03.0123.003; Thu, 25 Jul 2013 13:53:54 +0100
From: Administrator <Administrator@domain2.co.uk>
To: Remote User <Remote.User@remotedomain.co.uk>
Subject: Read: test
Thread-Topic: test
Thread-Index: Ac6JNfJV1/PT52W5RgusoIyJu3xtOwAABHWZ
Date: Thu, 25 Jul 2013 12:53:53 +0000
Message-ID: <3997F5578595784FB4F436448F0EE71602B957@exch2010.domain2.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/report;
        boundary="_000_3997F5578595784FB4F436448F0EE71602B957exch2010domain2_";
        report-type=disposition-notification
MIME-Version: 1.0
Return-Path: Administrator@domain2.co.uk

The line in question is the From: line - in 2013 it's missing the email address, in 2010 (and below) it's present, and read receipts work as you'd expect.

This was taken from a packet capture of the SMTP conversation between the Exchange servers and the email gateway. We use Postfix as a gateway, which attempts to fix the missing email address by inserting it's own hostname - I suspect the 'invalid.domain' is being inserted by your recipient's mail gateway or spam filter.

We've got a call open with Exchange product support - will post up as and when anything happens!

OK, the official answer from MS support is that Exchange 2013 is operating 'as designed'. Stunning.

Seems to me this is breaking RFC5322...

I've worked round it by making the Postfix relay append the primary email domain to the malformed 'From' header ("myorigin = $mydomain" if anyone's interested). It's not ideal though as it makes read receipts from our secondary domains look as though they're coming from the primary domain.