I know I'm connecting to port 587 since I specified it explicitly. But I don't understand the relevance to my problem.
Are you saying that when exim communicates with 587 it expects to negotiate TLS immediately? >From experiments with telnet it seems clear the server does a regular greeting >and then expects EHLO and STARTTLS. This seems consistent with the relevant >RFC (6409 seems the most current). Or perhaps you are saying that my use of 587 was only partly effective? Ross ________________________________________ From: Exim-users <[email protected]> on behalf of Lena--- via Exim-users <[email protected]> Sent: Saturday, April 29, 2017 4:32 AM To: [email protected] Subject: Re: [exim] TLS error on connection to smtp.office365.com (gnutls_handshake): An unexpected TLS packet was received. > The exim debug logs sort of look as if it is expecting to negotiate TLS > immediately on connection, rather than after the initial EHLO Yes. Look where the 465 came from: > Transport port=465 replaced by host-specific port=587 -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
