Hi Our company with windows server sbs 2003 ,we are sending the mails to our employees who are not having exchange account ,they are not be able to recieve emails from exchange users i.e internal office mails are getting bounced with the following error: the e-mail account does not exist at the organisation this message was sent to.Check the e-mail address,or contact the recipient directly to find out the correct address" We are sure that the mail address of the remote employee of our company is correct.All the mail addresses are created in the third part domain which hosted outside our organisation.We are sure that the mail id exists in the organisation. But why we are getting this error?If we send the mails through exchange to yahoo,hotmail,gmail,etc.......,they are properly going and recieving N.B: Before it was going properly.But after changing the hosting people this type of problem started .It worked fine for few months with the new hosting people Please provide a solution Thanks swaminathan

Hi Martin If you go through my previous reply you can get an idea from the NDR issued by the exchange to me -administrator. The same setup was running without problem even with the new hosting people but all of a sudden this issue occurred Thanks Swaminathan

The first response that I have provided is still valid. Nothing you have posted changes that. Exchange presumes that it is responsible for all email for the domain. The fact that you may have changed providers would have no effect on that whatsoever, because Exchange is still involved. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

On Wed, 10 Nov 2010 14:38:29 +0000, TECHSHAN wrote: > > >Hi Our company with windows server sbs 2003 ,we are sending the mails to our employees who are not having exchange account ,they are not be able to recieve emails from exchange users i.e internal office mails are getting bounced with the following error: the e-mail account does not exist at the organisation this message was sent to.Check the e-mail address,or contact the recipient directly to find out the correct address" We are sure that the mail address of the remote employee of our company is correct.All the mail addresses are created in the third part domain which hosted outside our organisation.We are sure that the mail id exists in the organisation. But why we are getting this error?If we send the mails through exchange to yahoo,hotmail,gmail,etc.......,they are properly going and recieving Are you sharing the domain name between your Exchange organization and that 3rd-party mail system? http://support.microsoft.com/kb/321721 Do you expect the Exchange mailboxes to receive e-mail from external senders? If so, then the MX record for your domain should direct connections to your Exchange server, not the the hoster's servers. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 11 Nov 2010 11:13:23 +0000, TECHSHAN wrote: >I am using Mdaemon for recieving MULTIPOP emails and exchange is configured for sending. So there are no mailboxes on the Exchange server? >Users remote are having the email addresses : ....@domain.com where @domain.com is the primary smtp address for inhouse users( active directory users) in exchange recipient policy . This sure sounds like a "shared namespace" situation. See previous answer about shared namespaces and refer to the KB article in that reply. >Users remote are not logging into our domain.They are not active directory or domain members.But they have the mail addresses in @domain.com. Is "domain.com" in your set of Recipient Policies? Is it marked as being authoritative for that domain? See my previous reply asking about shared domain namespaces. >Moreover our local domain name for our company is xyz.com .In our domain xyz.com, we have only one domain controller sbs 2003 with exchange . The DNS domain name of the Active Directory isn't important here. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 11 Nov 2010 14:04:35 +0000, TECHSHAN wrote: >If you go through my previous reply you can get an idea from the NDR issued by the exchange to me -administrator. Post the whole NDR. Check your SMTP protocol log and see if the hoster's server is refusing to deliver the e-mail. >The same setup was running without problem even with the new hosting people but all of a sudden this issue occurred If you've made no changes to your organization then it looks like the hoster is the one refusing to accept (or deliver) the e-mail. If that's the case you'll have to deal with the hoster to find out what they changed. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP