Microsoft KB Archive/244129

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:11, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


XFOR: Notes Connector Rejects Incoming Messages with the Apostrophe (') Character in the SMTP Address

Article ID: 244129

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Exchange Server 5.5 Service Pack 1
  • Microsoft Exchange Server 5.5 Service Pack 2
  • Microsoft Exchange Server 5.5 Service Pack 3



This article was previously published under Q244129

SYMPTOMS

The Microsoft Exchange Notes Connector cannot deliver mail when a Lotus Notes user either sends mail that contains an SMTP address with an apostrophe (') in the user name or replies to mail that contains an SMTP address with an apostrophe in the user name. For example, the user name, user.o'hara, contains an apostrophe. The following events are logged in the application event log:

31500 : MSExchangeNotes : Information : notes to exchange
Sender: user/cert@domain, size xxxx, Message id: C=US, a= , p=microsoft, l:messageid date time, notes:domain (servername/cert).
(mexe)
31501 : MSExchangeNotes: Information : transport to exchange
Report generated : sender: system administrator. message id..........etc
(mexe)
31040 : MSExchangeNotes : Warning : transport to exchange
No valid message recipients in message
(mexin)
31092 : MSExchangeNotes : Information : transport to exchange
Message contains empty recipient list, purging item automatically.
(mexin)


CAUSE

The apostrophe character (') is not allowed when checking the user name.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

Keywords: kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbqfe KB244129