?
Solved

smart host not responding

Posted on 2009-04-06
7
Medium Priority
?
517 Views
Last Modified: 2012-05-06
We are in the middle of moving to a new ISP.  I tried switching us over to the new connection and had not problem with general connectivity, however our Exchange server could not seem to connect to the new ISPs SMTP to forward outbound mail.  Can all SMTP servers act as a smart host for Exchange, or do they have to be specially configured to allow Exchange to connect to forward mail?  Our ISP has not stated either way whether they have an Exchange smart host available; they just say they have an SMTP server.
0
Comment
Question by:I_play_with_DNA
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 

Author Comment

by:I_play_with_DNA
ID: 24081536
I should have added that the following error appeared in the event log:

MSExchangeTransport, Event ID 4006
Message delivery to the host '72.1.205.168' failed while delivering to the remote domain  'smtp.bluarc.ca' for the following reason: The remote server did not respond to a connection attempt.

And I was able to Telnet to the SMTP server on port 25.
0
 
LVL 65

Expert Comment

by:Mestha
ID: 24082741
Smart host is almost an exclusive Microsoft term. You just need to know your ISPs SMTP server and whether they have restrictions on its use (domains need to registered, username/password required etc).

Can you telnet to the smart host on port 25?
Have you changed any DNS forwarding on the domain controllers to use the new ISP?

Any reason why you cannot use DNS for delivery? Do you not have a static IP address or have reverse DNS/PTR records set?

Simon.
0
 

Author Comment

by:I_play_with_DNA
ID: 24083158
I can telnet to the SMTP on port 25.

There were no DNS forwarders set on the domain controller.  This controller was set up by my predecessor and he did not configure any forwarders, but DNS resolution on our network works fine, so I assume that the domain controller is using it's gateway as the DNS automatically, and the gateway has it's DNS set as the new ISPs DNS.

I am considering using DNS for delivery, but I worry about our static IP being blacklisted if our mailserver were to become compromised at some point.  If we were to be blacklisted it would cripple the company.  II do have a PTR set though, so DNS is a possibility.



0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 65

Expert Comment

by:Mestha
ID: 24086873
Blacklisting is something that every company has to worry about. Using a smart host wouldn't really help with that - if the server was compromised then the spam would go through the smart host and your ISP could kick you off their network.
As long as the secure is secured, you have applied the relevant settings (recipient filtering, tar pit, restricted relaying, used strong passwords etc) then the chances of being blacklisted are minimised significantly.

Simon.
0
 

Author Comment

by:I_play_with_DNA
ID: 24093617
Further information:

When I telnet into the ISPs smart host (FROM the Exchange server) I can connect and actually send an e-mail using manual SMTP commands.  The e-mail is received by the recipient account.  But when Exchange tries to relay through the smart host I get "The remote server did not respond to a connection attempt" (MSExchangeTransport Event 4006) as mentioned above.

When I configure the SMTP Connector on our Exchange server to send using DNS, outbound mail simply sits in the various SMTP Connector queues and is never actually sent.

It seems that I cannot get our Exchange server to connect to ANY smtp server other than that of our old ISP.  I can relay mail through that server.  So I must be missing something in the Exchange configuartion.

Any ideas?
0
 
LVL 65

Accepted Solution

by:
Mestha earned 2000 total points
ID: 24099134
If telnet can connect then Exchange should be able to connect. There is nothing in Exchange which would stop the email from flowing correctly.

However what can stop email delivery is an authentication issue, so a username and password has been put on the SMTP virtual server directly and/or a smart host set on the SMTP virtual server directly.

Simon.
0
 

Author Closing Comment

by:I_play_with_DNA
ID: 31567228
I think the problem was that there was a password set in the SMTP Virtual Server, but I only removed the one from the connector.  I ended up deleteing the connector completely and removing the PW from the virtual server and this fixed the problem.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
New style of hardware planning for Microsoft Exchange server.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question