On Fri, Jan 30, 2015 at 06:39:36PM +0000, srach wrote:
> I also set the unique port to listen for the relay AUTH using TLS cert check
> so there is no conflict with the other ports and the options they are set
> with.
>
> The unique port to listen to for TLS cert AUTH on # server is 9443.
What software is listening on that port?
> I can check this now with simple telnet
>
> ?telnet XX.XX.XX.XX 9443
> ?? Trying XX.XX.XX.XX....
> ?? Connected to XX.XX.XX.XX.
> ?? Escape character is '^]'.
Where is the SMTP 220 banner???
> So now in the Postfix #1 relay client configuration I set
>
> - relay_transport = relay2:[XX.XX.XX.XX]:25
> + relay_transport = relay2:[XX.XX.XX.XX]:9443
No, you should have stopped at the previous step, your port 9443
service is not working. Look in the logs on that server.
> Jan 30 18:24:22 srchsvr PF-out/relay2/smtp[19829]: 160973C11E:
> to=<srcht...@clientdomain.com>, relay=XX.XX.XX.XX[XX.XX.XX.XX]:9443,
> delay=60, delays=0.01/0.01/60/0, dsn=4.4.2, status=deferred (lost connection
> with XX.XX.XX.XX[XX.XX.XX.XX] while receiving the initial server greeting)
As expected. Check the remote logs.
> I have changed the master.cf for PF-out to 'qmgr -v'
Whatever for?
> and 'relay2 ... smtp -v'
The remote server does not answer, debugging the local side is pointless,
especially the queue manager which does not even communicate with the
remote system.
--
Viktor.
