• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

Exchange Server Refusing to Send/Receive via SMTP

Hi,

I have a new-build Exchange Server, to which I have migrated by previous SBS2003 mailboxes and AD, via joining it to the domain, promoting to DC, and then seizing the Op master roles etc and restoring the mailboxes. Mailbox access and local email is fine, but anything in and out is getting 550 5.7.1 Unable to relay as an error. The virtual server is set to allow relay from all and anonymous access. Any suggestions appeciated.

Ben
0
Ben-Higgins
Asked:
Ben-Higgins
  • 4
  • 4
1 Solution
 
Ben-HigginsAuthor Commented:
Ok, now with some tweaking all outbound emails are displaying error "The remote server did not respond to a connection attempt" I can telnet the mail host fine from the server though.
0
 
SembeeCommented:
First - review your relay settings. You have probably turned yourself in to an open relay. You don't need to adjust the relaying settings to get email to flow out.

Are you using a smart host to send email? Does that smart host require a username and password?

Simon.
0
 
Ben-HigginsAuthor Commented:
Thanks for your comment. We are using DNS to send, not a smart host, and as far as realy settings go, I have a test SMTP virtual server/connector pair with no realy restrictions to ensure relay restrictions aren't causing a problem, which they are not.

Cheers
0
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.

 
SembeeCommented:
When you did your telnet test, did you actually send an email message?

Simon.
0
 
Ben-HigginsAuthor Commented:
Nope; just telnet and both helo and ehlo with response. Ignorant as I am, I don't know any other SMTP commands
0
 
SembeeCommented:
I have a quick guide here:
http://www.amset.info/exchange/telnet-test.asp

Simon.
0
 
Ben-HigginsAuthor Commented:
Simon,

Thanks for that; a useful guide indeed.

I have however, solved the issue by building a new Exchange server on the old SBS hardware and transferring mailboxes and master role, as well as adding new connectors/virtual servers. This is what I planned to do in the medium term anyway, so no major harm done.

The one further thing I need to do is remove the troubled server from the Exchange implementation. Is it just a case of using the remove server option on the menu for a given server?

If you could clarify this and any other issues I need to be aware of when removing this server, i'm happy to award you the points.

Thanks,

Ben
0
 
SembeeCommented:
There is a procedure that must be followed for removing the first installed Exchange server.
http://support.microsoft.com/default.aspx?kbid=822931

If you don't follow the procedure, it makes an awful mess to clean up.

Simon.
0

Featured Post

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

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