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

x
?
Solved

Exchange 2013 Outbound Email Send Connector via Smarthost configuration

Posted on 2013-12-26
7
Medium Priority
?
3,382 Views
Last Modified: 2013-12-27
I need to configure Exchange 2013 to use my email providers settings as a smarthost to be used in a send connector. So far I have tried configuring the hostname with authentication and the right port but TLS / SSL doesn't seem to get enabled.

Here are the SMTP settings from the provider (Fastmail)


SMTP


Server: mail.messagingengine.com
Port: 465
SSL/TLS Encryption: Enabled (but not STARTTLS)
Authentication: PLAIN (Our SMTP ports are for authenticated SMTP only; you'll need to make sure your software supports authenticated SMTP and also set up a username and password)

Username: your FastMail username/login name/email address (must include @fastmail.fm part)

Password: your FastMail password

Alternatively, if you're client supports STARTTLS only, you can use port 587 with STARTTLS enabled.
0
Comment
Question by:elchermans
  • 4
  • 3
7 Comments
 
LVL 12

Expert Comment

by:Navdeep
ID: 39741288
Hi,

Exchange 2013 uses starttls, have you tried using port 587 instead of 465?

Regards,
Nav
0
 
LVL 1

Author Comment

by:elchermans
ID: 39741337
I did try using port 587 as well.

I can ping the ips 66.111.4.73  and  82.145.212.145

Here are the protocol logs:



2013-12-26T09:00:40.652Z,Fastmail Outbound,08D0D02F6C4711F4,1,,66.111.4.73:587,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 66.111.4.73:587"
2013-12-26T09:00:40.653Z,Fastmail Outbound,08D0D02F6C4711F5,0,,66.111.4.72:587,*,,attempting to connect
2013-12-26T09:01:01.647Z,Fastmail Outbound,08D0D02F6C4711F5,1,,66.111.4.72:587,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 66.111.4.72:587"
2013-12-26T09:01:01.648Z,Fastmail Outbound,08D0D02F6C4711F6,0,,66.111.4.70:587,*,,attempting to connect
2013-12-26T09:01:22.652Z,Fastmail Outbound,08D0D02F6C4711F6,1,,66.111.4.70:587,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 66.111.4.70:587"
2013-12-26T09:01:22.653Z,Fastmail Outbound,08D0D02F6C4711F7,0,,66.111.4.71:587,*,,attempting to connect
2013-12-26T09:01:43.647Z,Fastmail Outbound,08D0D02F6C4711F7,1,,66.111.4.71:587,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 66.111.4.71:587"
2013-12-26T09:01:43.648Z,Fastmail Outbound,08D0D02F6C4711F9,0,,82.145.212.141:587,*,,attempting to connect
2013-12-26T09:02:04.646Z,Fastmail Outbound,08D0D02F6C4711F9,1,,82.145.212.141:587,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 82.145.212.141:587"
2013-12-26T09:02:04.646Z,Fastmail Outbound,08D0D02F6C4711FA,0,,82.145.212.145:587,*,,attempting to connect
2013-12-26T09:02:25.651Z,Fastmail Outbound,08D0D02F6C4711FA,1,,82.145.212.145:587,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 82.145.212.145:587"
2013-12-26T09:02:25.651Z,Fastmail Outbound,08D0D02F6C4711FB,0,,82.145.212.142:587,*,,attempting to connect
2013-12-26T09:02:46.692Z,Fastmail Outbound,08D0D02F6C4711FB,1,,82.145.212.142:587,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 82.145.212.142:587"
2013-12-26T09:02:46.692Z,Fastmail Outbound,08D0D02F6C4711FC,0,,82.145.212.143:587,*,,attempting to connect

0
 
LVL 12

Expert Comment

by:Navdeep
ID: 39741339
based on this log, it seems that you are not able to connect to the remote server, if you use telnet / putty and try to connect to IP Port, do you get to see the banner of fastmail?
like this
telnet IP portNo
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
LVL 1

Author Comment

by:elchermans
ID: 39741342
telnet mail.messagingengine.com 465:

Blank Screen - so connection is being established



telnet mail.messagingengine.com 587:

220 mail.messagingengine.com ESMTP ready
0
 
LVL 12

Accepted Solution

by:
Navdeep earned 2000 total points
ID: 39741358
So now 587 works well. Did fastmail provided any specific settings for setting up TLS? in exchange 2013, it will try to submit the msg using tls and if tls is not available it will switch to non tls mode. Also know as opportunistic TLS.

btw does your provider require you to use trusted certificate? TLS can fail if certificate requirements are strict.

Check this article on mutual tls. This for 2010 but the concept is almost the same.
http://technet.microsoft.com/en-us/library/bb123543%28v=exchg.141%29.aspx

Regards,
Nav
0
 
LVL 1

Author Comment

by:elchermans
ID: 39741365
I got it to work after using the IP address rather than the hostname. Thanks for your assistance!
0
 
LVL 12

Expert Comment

by:Navdeep
ID: 39741368
Glad, it worked for you.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

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

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
Upgrading from older Exchange server to the latest Exchange server can be tiresome, error-prone and risky, without being a seasoned exchange server administrators. It can become even problematic if you're an organization that runs on tight timeline…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
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…
Suggested Courses

571 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