Hi Recently, where i work, there was a change on the exchange 2007 environment.A SmartHost was added to the exchange connector, so that outgoing emails could be automatically scanned for viruses by a 3rd party. all standard emails are working fine, externally and internally. However, there is a sharepoint server running on the domain, which used to recieve emails directly into sharepoint. the email address is crm.internal@sharepoint.mydomain.com (changed for privacy reasons) the sharepoint server is called mosshost, and there are MX and A records in DNS, pointing to this sharepoint server. The email address looks like its on a subdomain, but its not, it was just updated in the DNS as sharepoint, so that all exchange traffic under sharepoint.mydomain would go to that server (mosshost) this used to work perfectly, but now there are errors. first, there was an error (same as at the end) but from an external source, stating that the address did not exist. so i added sharepoint.mydomain.com to the "accepted domains" in exchange 2007, thinking that this would force exchange to look for the address in DNS, and to deliver it to mosshost, like it used to. but, its not recognising the entry in DNS, so i dont know how to get it working..... :(Admittedly, im a lot more experienced with Exchange 2003, with routing groups..... i just want exchange 2007 to use the DNS as well as using a SmartHost.(Hope this makes sense guys, thanks)Diagnostic information for administrators: Generating server: exchange.mydomain.com crm.internal@sharepoint.mydomain.com#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##

Hi, First lets try to clarify the issue. 1. Pleaseensure that you have the latest update for SharePoint Server. 2. Whether you have SMTP service installed on SharePoint Server. 3. Whether we use contact on Exchange Server to send and receive email for SharePoint Server. 4. Whether we have send connector created to sent for sharepoint.mydomain.com, please try to use mydomian.com as address space on send connector. Note: We can select Custom as the send connector type. 5. Please check properties on that contact. If we have two SMTP email address there. One is xxx@domain.com another is xxx@sharepoint.domain.com Besides, please delete the accept domain and then check the issue again. Regards, Xiu

Xiu, many thanks for replying :) The sharepoint server itself works fine, as i sent an email from an email client directly to the server itself via smtp, it dropped the email to the drop box and populated the sharepoint pages appropriately. There is a contact in the exchange server / AD; Alias: crm.internal Email Address: crm.internal@sharepoint.mydomain.com The connector Edgesync - Host to internet goes through a smarthost , which allegedly stopped this working in the first place. I have removed the accept domain as you have asked, and i have tested, but this causes additional problems... the message seems to bounce between the transport and edge servers... (so i have put the accepted domain back on) I have added a connector, mydomain.com, which is set to use the internal MX records to route traffic. I take it, that when a smarthost is added, all traffic goes through it, so specifying another connector for local traffic will make sure that the emails are sent using dns internally..... hope this provides more information. thanks

Hi,Please check the properties for contactfrom EMS, if it has xxx@mydomain.com as its email address.Besides,please try to check if you havesend connector copiedto Edge Server.Regards,Xiu

Hi,I have checked the contact in EMC, and it is set to crm.internal@sharepoint.mydomain.comThe contact in AD is the sameThe send connector is mydomain.com, with "include all subdomains" added.For some unknown reason, the exchange server doesnt know where to route emails for sharepoint.mydomain.com, when it should be.NSLOOKUP proves its not a DNS issue.thanks

Hi,Please try to add crm.internal@mydomain.comto the contact. Besides,I'd like to know where did you create send connector,please try to create the send connector on Edge Server.Regards,Xiu

thanks....i think it was a combination of things.the contact, the smtp relay security settings and also the accepted subdomain.thanks