On 2024-09-19 Michael Deegan <[email protected]> wrote: > Package: swaks > Version: 20240103.0-1 > Severity: normal
> eg. connecting to an SSMTPA on port 465: > swaks -a -tlsc --server submission.example.com --to [email protected] > Successfully connects on port 465, negotiates SSL, but then bombs out > complaining that STARTTLS is not advertised (names changed to protect the > innocent): [...] > I think --tls-on-connect should imply something similar to --tls-optional (I > would argue that advertising STARTTLS here would actually be a configuration > error). Hello, That behavior does not make sense, I cannot it reproduce though. :-( ametzler@argenau:~$ swaks -tlsc --server localhost --to [email protected] -q rcpt === Trying localhost:465... === Connected to localhost. === TLS started with cipher TLSv1.3:TLS_AES_256_GCM_SHA384:256 === TLS client certificate not requested and not sent [...] === TLS peer certificate failed CA verification (self-signed certificate), passed host verification (using host localhost to verify) <~ 220 argenau.bebt.de ESMTP Exim 4.98 Thu, 19 Sep 2024 19:12:57 +0200 ~> EHLO argenau.bebt.de <~ 250-argenau.bebt.de Hello localhost [::1] <~ 250-SIZE 52428800 <~ 250-LIMITS MAILMAX=1000 RCPTMAX=50000 <~ 250-8BITMIME <~ 250-PIPELINING <~ 250-PIPECONNECT <~ 250-AUTH CRAM-MD5 <~ 250-CHUNKING <~ 250-PRDR <~ 250 HELP ~> MAIL FROM:<[email protected]> <~ 250 OK ~> RCPT TO:<[email protected]> <~ 250 Accepted ~> QUIT <~ 221 argenau.bebt.de closing connection cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
