GNOME Bugzilla – Bug 578920
MAPI Connector uses "Display Name" for email address, therefore Replies are not possible.
Last modified: 2009-04-15 04:43:43 UTC
Please describe the problem: It is not possible to reply to a message with Evolution on my Exchange 2007 SP1 server. The message bounces with an NDR, a copy of which is contained at the bottom of this report. I can see via my Sent Items on Evolution, the Outbox on Outlook (where the messages with Invalid recipients are stuck), that the email address field shows the same as the Display Name or Full name, rather than an email address. Here's an example NDR: Delivery has failed to these recipients or distribution lists: Charlotte Quinn The format of the recipient's e-mail address isn't valid. A valid address looks like this: username@contoso.com. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try sending the message again, or provide the following diagnostic text to your system administrator. Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: svr2.home.compsup.net Charlotte Quinn #550 5.1.3 STOREDRV.Submit; invalid recipient address #SMTP# Original message headers: Received: from svr2.home.compsup.net ([192.168.253.22]) by svr2.home.compsup.net ([192.168.253.22]) with mapi; Tue, 14 Apr 2009 09:10:08 +0100 MIME-Version: 1.0 Content-Type: text/plain Date: Tue, 14 Apr 2009 09:10:08 +0100 Message-ID: <3AE318AF845C224C9A5118CC89D52272055ECA9A0A@svr2.home.compsup.net> Subject: Re: Steps to reproduce: 1. Setup Evolution MAPI, using IP address of Exchange server instead of Hostname, since this is the only way to get it to setup without SIGSEGV on Ubuntu Jaunty. 2. Reply to an email 3. Observe NDR / bouce. Actual results: Message bounces with an NDR from the Exchange server. Replies are not able to be sent. Expected results: Reply should arrive at destination. NDR should not be received. Does this happen every time? Yes Other information: I am using Ubuntu Jaunty, as up to date as possible. I understand there are Openchange improvements upstream which Ubuntu does not have yet, perhaps this has already been fixed upstream too.
This problem has been fixed in our software repository. Fix should be available as part of 0.26.1 Thank you for your bug report. *** This bug has been marked as a duplicate of 572518 ***