Windows Small Business Server 2003 SR2 Exchange 2003 SR2Newbee here and I have been requested to set up Contacts that have the same domain name that are not part of the Domain, so they can select these users when generating an e-mail to them.These contacts are not physically connecting to the domain but receive e-mail for an external hosted POP account and are on site. I have tried to create the physical users and do see them in my drop down inOutlookwhen selecting to send to them. However the e-mail never reaches them. I just cant find any resources that provide an answer to creating external e-mail contacts or reciepents with same same domain name so these users can select them when generating an e-mail.I can send to anyone that is a part of the domain but the 11 users that have the same domain for their email accounts never arrives.Any help would greatly be appreciated.Thank you

Hi,I'm trying to understand your topology. So you have an e-mail domain hosted by an ISP. You are downloading the messages ofa groupof your users via the SBS POP3 connector. You have an other group of your users who doesn't have mailbox on your SBS server and using the ISP directly. You cannot send messages from your SBS users to your ISP users.If the situation what I mentioned above is correct you have to do two things:1. On the default recipinet policy disable the "This Exchange Organization is responsible for all mail delivery to this address" checkbox. You will notbe able to do this on the default domain. If this is your default domain you should create an other domain and make it default. In this case you have to configure additionalrecipient policy for the automatic e-mail address generation2. Create an SMTP Connector for this domain what route the messages to the ISP.Regards,Zoltnhttp://www.clamagent.org - Free Antivirus for Exchange http://www.it-pro.hu http://emaildetektiv.hu

Yes as Zoltan told, you need to configure Exchange server to share same SMTP address space with ISP otherwise sender will receive NDR saying that user doesn't exists and mail never reches to users who have mailboxes at ISP.... How to share an SMTP address space in Exchange 2000 Server or in Exchange Server 2003 http://support.microsoft.com/kb/321721Amit Tank | MVP Exchange Server | MCITP: EMA, MCSA: M | http://ExchangeShare.WordPress.com

Thank you Zolta'n and Amit for your prompt reply.We do have have an e-mail domain hosted by the ISP. There is currently no POP3 connector in place as the messages are not downloaded as a group, but rather each user has a specific mailbox they connect to from the ISP and those settings are set in thier Outlook respectivley.Ex. POP3 mail.domainname.com SMTP mail.domainname.comEven though some of these users do not use the domain,but have the same "E-Mail" domain name,its the users who do, that would like to have the ability to select these users from the "Global Address List" and route correctly.I didmodify modify therecipient policy as you suggested and am now able to send to the user next to me who only connects to the INet and uses e-mail through thePOP and not Exchange.I will update once I confirm all havenow received. Thank you both very much forsharing your knowledgbaseas thishelped very much.Paul

I have a similar issue but different variables and I am not sure that my situation meets any of the suggested methods. I have a domain that is primarily used by users within the Active Directory structure, however we have about 10 users that we do not want to have any access to the network or even have their mail to pass through our server, instead we want to mail to reside on server that hosts our domain, (fairpoint) that we get 50 email boxes with. I can setup the user with fairpoint, any user on the internet can send a receive email from said user, but if you try to send within the Exchange internal network I receive, The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <domainname.org #5.1.1> Does one of the methods within KB Article 321721 satisfy the issue I am receiving?