Hi ,We haveimplented twoExchange 2007 SP2 HUB & CAS servers in our existing exchange 2003 environment. No mailbox roles insatlled so far. Now we noticed that some of the Exchange 2003 recipeints are shown as anonymous users in the from field of their emails. Their addresses are treated as anonymous user not getting resolved. Issue noticed mainly for remote Site ( Routing group) users but alsofor a few main site recipients. Totest this issue I have enabled "resolve anonymous email" option in SMTP virtual server proeprties of all servers andit resolved the issue. But we don't want this option to be enabled permanentlyand it seems there is some issue after the introduction of exchnage 2007.All these users our internal exchange recipients. Any body have any suggestion to resolve this issue.ThanksAboo Arif

Hi, Would you please let me know how the problem message is submitted? Whether the issue is submitted by Outlook MAPI profile or POP3/SMTP client? I would like to explain that by default, if the message is delivered by using POP3/SMTP client and the client does not authenticate to Exchange server before delivering the message, the Exchange server will not attempt to resolve the P2 address. For your reference: Resolve Anonymous Senders Functionality in Microsoft Exchange 2003 http://support.microsoft.com/kb/828770/en-us ~~~~~~~~~~~~~~~~ Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb @ microsoft.com ~~~~~~~~~~~~~~~~

They are using Outlook MAPI profile and not using any SMTP or POP3. As I know the deafult behaviour Exchnage 2003 is not to resolve anonymous mails( SMTP, POP3 or applciation generated). But this users are my internal outlook users. Also this issue started only after the schema upgrade and introduction of HUB & CAS servers. Whether I need to make any changes in Exchange connector or settings?Thanks,Arif

Hi Aboo, Would you please let me know whether the issue occurs when sender and recipient are on the same server? I have performed a local test. If the sender and recipients mailbox on different server and two Exchange servers are not able to authenticate to each other successfully, the issue will occur. Therefore, if the issue only occurs when sender and recipient are on different Exchange server. I suggest you checking the SMTP protocol between the two servers to check whether they are able to authenticate successfully. ~~~~~~~~~~~~~~~~ Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com ~~~~~~~~~~~~~~~~

Hi Mike,Issue happenseven if the sender and recipients areon the same server.We noticed mailnly while mailingto DL's. Incase of different servers this happens very often. Only the sender address is not getting resolved.ThanksAboo Arif

Hi Aboo,Would you please let me know whether the DL is configured to be expanded on other Exchange server rather than the local server which the Sender and Recipients' mailbox reside on?In addition, would you please help me gather related message tracking log for further research?Thanks,Mike

Hi Mike,Issue while sending to DL has been resolved after changing the expansion server to "Any Server" from a specfic internal exchange server. Now issue exists only with remote server users. Whenver we sent or recievefrom/to remote server the "from"address field isnot getting resolved at the recieveing end. I checked SMTP virtual servers properties are deafult. Do you want me check any thing specifically.ThanksArif

Hi Arif, Thanks for your response. As I explained in my previous thread, if the Exchange server is not able to authenticate to remote server successfully before delivery the message, the remote Exchange server will consider the message is submitted anonymousely. As you know, the Exchange will not resolve sender address if message is submitted anonymousely by default. Therefore, we need to check whether the Exchange server is able to authenticate to remote server successfully. You can check the SMTP protocol log regarding the issue. In addition, please understand that the Exchange 2003 server use X-EXPS GSSAPI command to authenticate by default. Please check whether any firewall between two Exchange servers which may filter the command. For your reference: SMTP Protocol Extensions http://technet.microsoft.com/en-us/library/bb123786(EXCHG.65).aspx Mike

Hi Mike,Thanks for the informtion. There is no firewall between the servers. I have hecked the SMTP protocol logs. As you mentioneditlogs the follwing authentication realted events.Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:SMTP Protocol Event ID:7004Description:This is an SMTP protocol error log for virtual server ID 1, connection #199. The remote host "10.0.x.y", responded to the SMTP command "xexch50" with "504 Need to authenticate first ". The full command sent was "XEXCH50 2296 2 ".This will probably cause the connection to fail. also Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:SMTP Protocol Event ID:7010Description:This is an SMTP protocol log for virtual server ID 1, connection #29. The client at "10.0.x.y" sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first ". The full command sent was "xexch50 1084 2". This will probably cause the connection to fail.I haveadded send as permission for Exchange DomainServers groupon on all exchange servers( which was not present when I checked)based on artcilce http://support.microsoft.com/kb/843106but still same error logs and issue persists.I have checked any other nested group have explicit deny permission but couldn't find.Please let me know if have any other sugestions.Thanksregards,Aboo Arif

Hi Mike,The issue resolved ... Looks like the settings took some time toget applied on all servers. The solution was ,Take "security settings" of all servers and provide "Send As" permission for "Exchange domain Servers" group.orelse provide the same permission from adinistrative group level.http://support.microsoft.com/kb/843106Iam sure thispermission has been removed by Exchange 2007 sp2setup. This happened immediateley after the exchange 2007 setup and intorduction of first HUB & CAS servers.Your support was excellent, Yousuggestionswas pointing tothe solution clearly, Thanks muchRegards,Arif

Hi Arif, I am glad to know the issue is resolved and thanks for sharing your solution here. Thanks,Mike