Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 284
  • Last Modified:

Changed from Dynamic to Static IP -> 550 5.7.1 Unable to relay error. What's the fix?

My client recently changed from dynamic to static IP, and has Exchange Server 2003 running on his machine. DNS is also configured there as well.  MX points to mail.lincolnparkone.com (which is the mail server), but still not able to relay.

Error message as follows:

<blah@mail.lincolnparkone.com>:
71.216.209.95 does not like recipient.
Remote host said: 550 5.7.1 Unable to relay for blah@mail.lincolnparkone.com Giving up on 71.216.209.95.

I am wondering what's the problem here.

Thanks!

David
0
hawkeyex
Asked:
hawkeyex
  • 6
  • 3
1 Solution
 
SembeeCommented:
The DNS of that domain is in a real state.

http://www.dnsreport.com/tools/dnsreport.ch?domain=lincolnparkone.com

The other MX records don't accept email for that domain, so should be removed. It will save confusion and ensure a timely email delivery, especially of the primary email server goes down.

Is mail.lincolnparkone.com in the recipient policy?
I would expect lincolnparkone.com to be, but not mail.lincolnparkone.com.

The change of IP address shouldn't have affected anything, unless there have been restrictions placed on the SMTP virtual server.
What happens internally? Can you do an internal telnet test and send?

Simon.
0
 
hawkeyexAuthor Commented:
Right, lincolnparkone.com is set as recipient policy.

I did not put down mail.lincolnparkone.com
0
 
hawkeyexAuthor Commented:
I think I know what the problem is. Originally, the pop3 connector has it set in its old format, with username as blah@lincolnparkone.com and pw, but I have removed blah@lincolnparkone.com and changed it to just blah. It should work, no?

David
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
SembeeCommented:
In the DNS report there is an Exchange server responding.
The POP3 connector is only used to collect email from a POP3 server - but it appears that you are using SMTP Delivery.

I don't know what you mean by "I did not put down mail.lincolnparkone.com".

Simon.
0
 
hawkeyexAuthor Commented:
okay, so I don't need the POP3 connector for this?

I did not put down mail.lincolnparkone.com as my recipent policy. Should I?
0
 
SembeeCommented:
No you shouldn't put mail.lincolnparkone.com in the recipient policy. However in your original question...

<blah@mail.lincolnparkone.com>:
71.216.209.95 does not like recipient.
Remote host said: 550 5.7.1 Unable to relay for blah@mail.lincolnparkone.com Giving up on 71.216.209.95.

ie it is showing the email address as being @mail.lincolnparkone.com

If that wasn't in the recipient policy then the error you are getting is normal.

Recipient policy tells Exchange what domains it is responsible for.

However you have mentioned the POP3 connector. Is this SBS? If so you shouldn't be configuring things by hand. Use the Internet and Email wizard (or whatever it is called) to configure email for lincolnparkone.com. Trying to do things manually usually causes problems.

Simon.
0
 
hawkeyexAuthor Commented:
Ok. I will try that.
0
 
hawkeyexAuthor Commented:
Yes, it's SBS. I'm still trying to find the wizard..
0
 
hawkeyexAuthor Commented:
Found the wizard.. configured.. testing.. stand by..
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now