I didn't see you get any replies. Let me add a couple things, but I can't claim to have THE answer.
First, I suspect that your address resolution description is not quite right. Client user interface do frequently display extraneous characters as though the MTA was trying to parse them in error, but I think that if you look at your server logs that you will see that Exchange did not make the implied error when formulating an SMTP string either for passing to a relay host or for use in DNS queries. But check that - there is a first time for everything. Next, I suspect that the real problem is a domain error. Also, you say "Outlook/Exchange is attempting . . ." That is not a fine enough description of what is going on. Generally, Outlook does not even try to parse an address, unless it is an item from either the Outlook Contacts or a PAB entry. This should not be the case. But, the next part of your description does look like it is starting to get at the problem. You say that the reply string looks like [SMTP:[EMAIL PROTECTED]] and not [SMTP:[EMAIL PROTECTED]]!!!!!!! Is that right? If so, then I think you are onto your answer. At this point, yes it does matter whether or not you are on E2k+AD or a non-AD previous version. The common practice is for UPN names to be SMTP strings that follow the form [EMAIL PROTECTED] and to make certain that either your Exchange systems native SMTP addresses, or an internal relay host (sometimes called a resolver) can perform a delivery using the UPN. Prior to E2K+AD, it was very common for the situation to arise in which a person's display name in Exchange looked nothing like a valid SMTP string. You will have to sort this out, but if your note is accurate, then I think you have assembled most of the critical data required to solved your problem. -----Original Message----- From: Mike Koch [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 6:07 AM To: Exchange Discussions Subject: NDRs using Palm.net We're running Exchange 5.5 w/ SP4, in case that matters. I'm starting our Exchange 2000 migration next week. Clients are various versions of Outlook, from 97 through 2002. I've got one user (a VP/lawyer) who uses a Palm device (model unknown at this time) and the Palm.net wireless service to send email to both internal and external recipients. By all accounts, his emails to external users of services like Yahoo Mail or Hotmail work perfectly. However, email to internal users, although delivered correctly, cannot be replied to - an NDR is generated. When the recipient clicks on Reply (using any version of Outlook), the To: field looks like: "[SMTP:[EMAIL PROTECTED]]". The address IS valid, but Outlook/Exchange is attempting use the entire string as an address (including the brackets and everything between them). Is there anything I can do in Exchange to get it to parse the address correctly, or is this strictly an issue with the configuration of his Palm? I've never worked with Palms before, and I'm trying to avoid looking like an idiot when I go up to speak with him. Any help would be appreciated. Thanks, Mike _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
