Repointed MX record being rejected by Recipient Server IP Address

Hi , I recently repointed a MX record for this domain: investalliance.com to point to mail1.atlantic-alliance.net. which currently hosts the mx records for the atlanticalliance.net domain. However , now that propagation has cleared and the recipient policy has been configured to accept the @investalliance domain. I have sent test emails to the administrator account as well as users but am  still getting the same error message :

_______________________________________________
62.49.218.53 does not like recipient.
Remote host said: 550 5.7.1 Unable to relay for administrator@investalliance.com
Giving up on .62.49.218.53

-----------------------------------------------------------------------------------
Now i have set multiple domains on other SBS 2003 boxes without a problem so long as the recipient policy is configured properly, incoming mail is accepted without problems. The server is working perfectly fine with the exsiting default  domain but not sure whats amiss with adding this second domain- please help.

Details for the server are: SBS 2003 with Exchange Version 6.5 Service Pack 2)
62.49.218.53 is the routers IP - The Server is configured with one network card only and hence the router is port forwarding port 25.

Open in new window

zejarraAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
giltjrConnect With a Mentor Commented:
What the message seems to be saying to me is that 62.49.218.53 received an e-mail for administrator@investalliance.com and that it, the smtp server, is setup not to receive e-mail for the domain investalliance.com and further it is configured not to relay e-mail for this domain also.

Is 62.49.218.53 supposed to receive the e-mail for investalliance.com or is it supposed to relay it to another server?
0
 
giltjrCommented:
It appears that the smtp server on mail1.atlantic-alliance.net is not configured to send e-mail for the domain investallianc.com.

I am assuming that mail1.atlantic-alliance.net is the same host as 62.49.218.53.  If it is not, what is 62.49.218.53?
0
 
zejarraAuthor Commented:
Hi  giltjr: Yes that is correct - mail1.atlantic-alliance.net resolves to the hosts IP 62.49.218.53 which is where the server is at.
Please bear in mind i have only tested incoming emails, havent even tried sending out yet using the investalliance.com address.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
zejarraAuthor Commented:
Its meant to receive the email and relay it potentially cos i would like users to send emails using this doman address as an option - But like i said earlier , i havent even got to the stage where the mail is hitting the mailboxes it gets rejected beforehand!
0
 
giltjrCommented:
If you have not properly configured the SMTP server at 62.49.218.53 it will get rejected before it hits the mail box.  It has to get to/through the SMTP server before it gets to the mail box.

You need to make sure that 62.49.218.53 is configured to accept and relay e-mail for investalliance.com first.
0
 
zejarraAuthor Commented:
Hmmm - in past experience - configuring the recipient policy was enough to get mail accepted on the server, not sure where else to configure the server to accept this domain - any suggestions?
0
 
MesthaConnect With a Mentor Commented:
Adding the domain to recipient policy is all that needs to be done for Exchange to accept email for a network. Whether there is anything third party software that needs to be updated is another matter altogether.

However I have seen some occasions where the recipient policy doesn't update the SMTP Service correctly. Try restarting the SMTP Server service and then test again.

-M
0
 
zejarraAuthor Commented:
Hi Mestha - i did reboot the server which i suspect is as good as restarting the service - However am still getting an error message - Given the fact that there is no indication of the Server's name on the bounceback message, is it possible that the router is blocking it before it reaches the server?
Can a router be configured to accept only some domains but not others?
0
 
MesthaCommented:
The fact that the server name is not in the NDR doesn't mean a thing. The server name in the NDR is not the address of the server that rejected the message, but the address of the server that generated the NDR. As this error is generated at the point of connection, the NDR would be generated by the server sending the message.

While some routers have SMTP scanning capabilities, unless yours has some kind of antispam functionality I doubt if it is rejecting the message. It is most likely that Exchange hasn't updated SMTP correctly so the SMTP engine on the server is rejecting the message. Correcting that though can be troublesome.

Run the SBS best practises tool on the server and correct anything Exchange related.

I would also suggest removing the domain from recipient policy, then restarting the SMTP Server Service and then putting it back in again.

-M
0
 
giltjrCommented:
To test you can use telnet.

Telnet to the SMTP server IP address, but specify port 25:


    telnet x.x.x.x 25

Then just press enter.  Then type in HELO xxxxx where xxxxx is your AD domain name.  They type:

    MAIL FROM: <aaa@bbbb.cccc>
    RCPT TO: <administrator@investalliance.com>
    DATA
    Subject:  This is a test
    <cr>
    This is a test.
    <cr>
    .
    <cr>

Where you see <cr> this means to to just press enter.  In the mail from address replace aaa@.bbbb.cccc with a valid e-mail address, BUT do NOT use one that is valid on your Exchange server, use a google, hotmail, yahoo or some other account as long as it is a vaild e-mail addersss, but not valid on your Ecchange server.

If your Exchange server is rejecting the e-mail, then it will show up in the above test.
0
 
zejarraAuthor Commented:
Hi Mestha,

Have done as you recommended and still getting the rejection - Am upping the points up because this is getting increasingly troublesome as it needs sorting -

As for Telnet'in in , in the telnet prompt i am not successfully connecting - a) becuase when i use the open command it insists on connecting to port 23 despite me putting :25 -
When i type - open port 25 62.49.218.53 - it doesnt work - I know i am not doing the switches properly will keep trying -
0
 
giltjrCommented:
You don't put :25 just 25 and there is space between the host name and the number 25 for you it would be


     telnet 62.49.219.53  25

0
 
zejarraAuthor Commented:
My apologies for the delay on this  - had to go away for a week , though the urgency has gone up a gear as a result-  I passed this job onto a colleague who believes the problem could be to do with the intricaties of the way i repointed the MX records. I am investigating this now, alongside testing the Telnet'in as mentioned above. Will report back.
0
 
zejarraAuthor Commented:
Ok , once again apologies for the delayed response -  I can now confirm that i can send outbound mail from the server using the investalliance.com address - Hence my problem is still with incoming. I thought it may have been an issue with the recipient update list service not applying the settings i made, but i presume the fact that i can send out using this new address means that it must be working fine. Any cool suggestions?
0
 
giltjrCommented:
Does scorpiopartnership.com mean anything to you?  It seems that your server is configured only to accept e-mail for that domain.
0
 
zejarraAuthor Commented:
Hi giltjr,

It does actually , and their support is handled by another company , it turns out that they are sharing a router with these guys  and i suspect the mail goes via them as well. I have contacted their support a few hours back, and they have said they will look into it. I suspect we are very close to a solution here, i will report back when i get an answer and close this question hopefully, then award points.
0
 
giltjrCommented:
Doing nslookups:

MX records for scorpiopartnership.com point to relay.mhx.biz and spl01-adsl.demon.co.uk

MX records for investalliance.com point to relay.mhx.biz and mail1.atlantic-alliance.net

Both mail1.atlantic-alliance.net and spl01-adsl.demon.co.uk reslove to the IP address 62.49.218.53.

I don't know if these are the same exact host or if they are supposed to be different hosts.  Is 62.49.218.53 supposed to be the IP address of your Exchange server?
0
All Courses

From novice to tech pro — start learning today.