Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Stan Hoeppner (stanhardwarefreak.com)
Date: Sun Dec 26 2010 - 07:09:36 CST
Roman Gelfand put forth on 12/25/2010 6:06 PM:
> Actually, the original proble reported with the previous post namely
> connection timeout was resolved. After checking tcpdump, I realized
> outgoing smtp port was closed.
> But, as it appears, this email was not in vain. I need to use a
> different smtpd server. Nevertheless, the 587 server worked well. I
> suppose the right thing to do here will be to use 10225.
I picked 10225 at random. You can use nearly any TCP port you choose
for your custom smtpd listener in master.cf, within reason. I'm not
going to take the time to list all the exceptions. Others have written
books on the subject.
The key is that you must program that port into the outbound smtp client
on the Exchange server to match the port declaration in master.cf. This
so Exch not only knows what IP addresses to relay to but also what TCP
port. This combo is typically called a TCP socket address IIRC.
> Thanks for your help.
You're welcome Roman. Glad I was able to help you.