Exchange 2007 smtp relay problem
Hi experts i have recently configured new domain for a new company with server 2003 active directory and exchange 2007,i have put the mx record in our head office which is completely different domain,users from the new company can send email to every domain including the head office.when i send and email from head office exchange i am getting the following error message,i assume is about relaying but have no clue on which server i must setup relay and how,is being four days struggling.some body please help with concise information regarding this issue,error message below This message was created automatically by the SMTP relay on ***FIREWALL.DOMAIN.LOCAL A message that you sent could not be delivered to all of its recipients. The following address(es) failed: user@domain.org.za SMTP error from remote mail server after RCPT TO:<userm@domain.org.za>: host exchange ip address [*.*.*.*]: 550 5.7.1 Unable to relay ------ This is a copy of the message, including all the headers. ------ Return-path: <user@domain.gov.za> Received: from [*.*.*.*] (port=39554 helo=exchange.domain.local) by firewall.domain.gov.za with esmtps (TLSv1:RC4-MD5:128) (Exim 4.69) (envelope-from <user@domain.gov.za>) id 1QhMkZ-0003r7-0e for user@domain.org.za; Thu, 14 Jul 2011 16:18:47 +0200 Received: from exchange.domain.local ([*.*.*.*>*]) by exchange.domain.local ([*.*.*.*.*]) with mapi; Thu, 14 Jul 2011 16:18:19 +0200 From: "" <user@domain.gov.za> To: "user@domain.org.za" <user@domain.org.za> Date: Thu, 14 Jul 2011 16:18:18 +0200 Subject: testing Thread-Topic: testing Thread-Index: AQHMQjDhS8hwPxtja0CAWcxb7n2ZJA== Message-ID: <A7704D8100681343BCC2A9D796E45C321BA844B3BA@exc001gp.dst.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
July 14th, 2011 12:49pm

Hi, Did you configure EDGE server in new company loction to receive email from outside. go in default receive connector and set "anonymous access" and then check. To find receive connectors in the EMC, navigate to Server Configuration -> Hub Transport. Then select your server and you'll see the Receive Connectors tab below. The "Default" receive connector on a Hub is configured for other Exchange servers to authenticate, but it doesn't accept anonymous email by default. The easiest way to address this is to add the Anonymous users<acronym></acronym> permissions group to this connector Please see sextion "Receive connector configuration" in below. http://blogs.technet.com/b/exchange/archive/2006/11/17/3397307.aspx Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2011 1:07pm

The way i see it, you seem to have 2 different Exchange organization. The HO is receiving the email for both environments. If this is the case, in your HO, i would create an additional accepted domain that matches the email addresses of the 2nd Exchange org and set it an internal relay and point the destination to the IP of the new Exchange server
July 14th, 2011 1:48pm

yes,the new org is receiving and sending emails everywhere including to the head office,the head office also send and receive emails but can not send to the new org.there is no relationship between two exchanges,the only thing is did is to setup mx record for the new org at head office dns server.
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2011 4:08pm

Thanks lafontma,it was the first thing that comes to my mind and did it but didn't work,when i created a new accepted domain i didn't get an option to specify the new exchange server and i set it for external relay.i will try again and set it an internal.
July 14th, 2011 4:14pm

host exchange ip address [*.*.*.*]: 550 5.7.1 Unable to relay Whose IP is this? yours or the remote server in the new Org? When you say you setup MX records? Was this on your internal DNS? Where do they point to?Sukh
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2011 4:39pm

hi sukh that ip address is for exchange at head office,the mx record for the new org is at head office and pointed to public ip for exchange for the new org.
July 15th, 2011 2:50am

Thank you very much for all your respond, the problem was on the firewall,there was a rule which was meant for internal servers and exchange for new org was added there.
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2011 7:36am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics