Re: [exim] EXIM Timeout on tcp required ports

2019-03-14 Thread Andrew C Aitchison via Exim-users
On Thu, 14 Mar 2019, Ryan McClung via Exim-users wrote: Unfortunately no one answered my initial question. When trying to connect to the TLS required ports it simply times out. I have the ports listening, the ports are not blocked by our firewall, and yet nothing works. Any thoughts? Can you

Re: [exim] EXIM Timeout on tcp required ports

2019-03-14 Thread Dominic Benson via Exim-users
> On 14 Mar 2019, at 18:56, Ryan McClung via Exim-users > wrote: > > Unfortunately no one answered my initial question. > > When trying to connect to the TLS required ports it simply times out. When you changed 587 to not be tls_on_connect, did that affect your ability to connect to that

Re: [exim] EXIM Timeout on tcp required ports

2019-03-14 Thread Ryan McClung via Exim-users
Unfortunately no one answered my initial question. When trying to connect to the TLS required ports it simply times out. I have the ports listening, the ports are not blocked by our firewall, and yet nothing works. Any thoughts? On Thu, Mar 7, 2019 at 1:31 AM Christian Balzer via Exim-users <

Re: [exim] EXIM Timeout on tcp required ports

2019-03-06 Thread Christian Balzer via Exim-users
On Tue, 05 Mar 2019 09:45:47 -0500 Bill Cole via Exim-users wrote: > On 5 Mar 2019, at 9:10, Ryan McClung via Exim-users wrote: > > > Why use only 465 and not 587? Just curious there. > > Or why not every port between 400 and 1? :) > > The way daemons on ports 465 and 587 can be expected

Re: [exim] EXIM Timeout on tcp required ports

2019-03-05 Thread Heiko Schlittermann via Exim-users
Ryan McClung via Exim-users (Di 05 Mär 2019 15:16:16 CET): > Update on this issue. > > I set 465 as the only TLS port. Time out is still occurring on 465. The > openssl client is connecting successfully but testing with an mta testing > tool like swaks times out. > What is the swaks command line

Re: [exim] EXIM Timeout on tcp required ports

2019-03-05 Thread Bill Cole via Exim-users
On 5 Mar 2019, at 9:10, Ryan McClung via Exim-users wrote: Why use only 465 and not 587? Just curious there. Or why not every port between 400 and 1? :) The way daemons on ports 465 and 587 can be expected to behave are defined in IETF RFCs 6409 and 8314. If you want your mail system to

Re: [exim] EXIM Timeout on tcp required ports

2019-03-05 Thread Ryan McClung via Exim-users
Update on this issue. I set 465 as the only TLS port. Time out is still occurring on 465. The openssl client is connecting successfully but testing with an mta testing tool like swaks times out. On Tue, Mar 5, 2019 at 9:10 AM Ryan McClung wrote: > Why use only 465 and not 587? Just curious

Re: [exim] EXIM Timeout on tcp required ports

2019-03-05 Thread Ryan McClung via Exim-users
Why use only 465 and not 587? Just curious there. As for the openssl client connection -- it has been timing out without any response from the server. Can confirm this worked before upgrading. On Tue, Mar 5, 2019 at 7:01 AM Graeme Fowler via Exim-users < exim-users@exim.org> wrote: > On 4 Mar

Re: [exim] EXIM Timeout on tcp required ports

2019-03-05 Thread Graeme Fowler via Exim-users
On 4 Mar 2019, at 18:49, Ryan McClung via Exim-users wrote: > daemon_smtp_ports = 25 : 465 : 587 > tls_on_connect_ports = 465 : 587 Port 587 is the submission port; it uses SMTP and STARTTLS rather than tls-on-connect. tls_on_connect_ports should *only* be 465. For testing, use this:

[exim] EXIM Timeout on tcp required ports

2019-03-05 Thread Ryan McClung via Exim-users
Greetings, Please see config below: (Hidden sections are just LDAP queries) ### LDAP ###Default LDAP servers ldap_default_servers = #SEARCH MACROS EXIM_DIR=/etc/exim SYSTEM_ALIASES_FILE = /etc/aliases BLACKHOLE = INACTIVEDOMAINS = USER_ALIASES = USER_FORWARDS = USER_HOST = USERS =