You are right - that's what we'll do. The port 26 thing came about
decades ago when traveling users would find port 25 blocked.
Jeff
On 6/8/2021 5:12 PM, Remo Mattei wrote:
Why not use 465 then at this point?
Remo
On Jun 8, 2021, at 10:55 AM, Jeff Koch <[email protected]
<mailto:[email protected]>> wrote:
Hi Eric and list:
Thanks for the suggestion and for thinking about this. In the
meantime we figured out the problem. We've isolated the issue to a
local ISP operating under the names Netlife/Ecuanet/Telconet. All
users with issues are using this ISP. Changing the smtp port to 26
solves the problem - which on our mailservers is prerouted and
redirected to 587. Looks like the ISP is doing something on port 587.
Weird
Jeff
On 6/8/2021 4:11 PM, Eric Broch wrote:
If you're using spamdyke it will do TLS encryption. Disable it. In
/etc/spamdyke/spamdyke.conf do the following:
# QMT does encryption/decryption when cert file is commented
#tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp
On 6/8/2021 12:19 PM, Jeff Koch wrote:
Hi
More info.
From some locations telnetting to port 587 on this mailserver and
then entering EHLO gets a list of services that
includes STARTTLS and from other locations STARTTLS and PIPELINING
are not shown. Any idea why that would happen?
What controls the list of services announced to email clients?
Jeff
<kkicacokkcbnlloi.png>
<dnlpiagmiaaaffdd.png>
