Hey Guys, We've set up exchange in our small office, at the moment we've got several people with @example.com emails in-office working fine in conjunction with our 1and1.co.uk email account. We also have several @example.com email addresses for employees that work from outside the office. They are set up on 1and1 so they are working fine externally, but when we send them emails from in-office to external @example.com, exchange keeps them in a mailbox. If we don't have a mailbox for them in exchange then we just get a bounce-back from exchange saying it doesn't exist.Completely new to exchange but have tried all the settings I can think of, if there's any other details you require please ask.Thanks, Leigh

Hi Leigh, Firstly, please let me know whether the Exchange 2003 or Exchange 2007 installed. For Exchange 2003, please check whether the @example.com email addresses have been added into Recipient Policy (Email Address Policy). If the @example.com is added to an E-mail addresses policy, the Exchange Server considers that it should be authoritative over this domain. When Exchange Server is authoritative over the domain, it assumes responsibility for delivering the message and returns a delivery status notification if it cannot find a recipient in Active Directory directory service. To solve the issue, we can attempt the following method: 1. Open the Recipient Policy which adding the @example.com email addresses 2. Under the E-Mail Addresses (Policy), double click the Generation rule regarding the @example.com email addresses 3. Uncheck This Exchange Organization is responsible for all mail delivery to this address For Exchange 2007, the e-mail address recipient policy concept in Exchange 2003 is separated into two concepts in Exchange 2007: E-mail Address Policies (EAP) and Accepted Domains. EAP defines the e-mail proxy addresses that are stamped onto recipient objects. Accepted domains define the SMTP namespaces for which an Exchange organization routes e-mail. In Exchange 2007, authoritative and relay domains are managed together as accepted domains. To solve the issue, please do not add the example.com as Authoritative Domain. Mike

Hi Mike Thanks for the reply to Leigh's message. Unchecking the This Exchange Organization is responsible for all mail delivery to this address solved the problem of sending out emails, but prevented those of us in the office from receiving any. Is this by design? We're using Exchange 2003 onSBS 2003. Is there something that I'm missing? Also, our users seem to be organised under "Users" in the System Managerrather than in the active directory, even though any attempt to add them to the AD tells us they are already registered users. Should this make a difference?Excuse our collective ignorance but I want it working perfectly. Thanks in advance David

Hi David, Please let me know whether only the external email cannot be sent to the internal user by using the @example.com email addresses. Whether the internal user can send to another internal user by using the @example.com email addresses. If only the external email cannot be sent to the internal user by using the @example.com email addresses and the unable relay NDR message is received, please attempt the following method to solve the issue. You can create a send connector by using the following method to allow relay for the @example.com domain: 1. Open Exchange System Manager 2. Click Connectors 3. Create a Send Connector 4. Under Local Bridgeheads, click Add. Add the SMTP Virtual servers that used to receive the Internet email. 5. Click the Address Space tab. Add an @example.com SMTP Address Space and check Allow messages to be relayed to these domains 6. After creating the Send Connector, please restart the SMTP service. David, please understand that when a message arrives, Exchange Server 2003 tries to find the destination address in the Active Directory database. If Exchange Server cannot find the destination address in Active Directory and Exchange Server is not the authoritative, Exchange checks the Exchange connectors and the local DNS for a match and delivers the mail when it finds a corresponding address space. When Exchange Server 2003 tries to deliver a message to a local address space (an address space that exists on a recipient policy), it tries to find the destination address in the Microsoft Active Directory directory service. If Exchange cannot find the destination address in Active Directory, the following occurs: a) If the Exchange organization is not authoritative, Exchange Server checks connectors and DNS to find another route to that address space. If Exchange finds a matching connector address space, the Message will be routed to that Connector b) If Exchange finds no Connector, it routes the e-mail through DNS and looks for a corresponding MX record and routes the e-mail to this host. c) If Exchange doesnt find any match, a non-delivery report (NDR) is generated with error code 5.4.0. This error code indicates that there is a name resolution issue. d) If the Exchange organization is authoritative for the e-mail domain, Exchange Server immediately generates an NDR with error code 5.1.1. This error code indicates that the destination address does not exist. For your reference: Exchange 2003 SMTP Namespace Sharing http://www.msexchange.org/tutorials/Exchange-2003-SMTP-Namespace-Sharing.html Mike