On Tue, Jun 20, 2006 at 10:19:23PM +0200, Julien Lousi wrote: > On Tue, Jun 20, 2006 at 11:42:33AM +0300, Marko Mäkelä wrote: > > Package: msmtp > > Version: 1.4.6-1 > > Severity: grave > > > > msmtp 1.4.6-1 refuses to initiate a STARTTLS connection to a server that > > works fine with msmtp 1.4.5-1. Downgrading to 1.4.5-1 worked around the > > problem. Here's what happens on 1.4.6-1. I replaced the addresses with > > example.com: > > [snip] > > > --> STARTTLS > > <-- 220 begin TLS > > msmtp: TLS handshake failed: A TLS fatal alert has been received. > > msmtp: could not send mail (account default from example-msmtp) > > It seems that an error occured when it wanted to upgrade to an encrypted > connection. > > > On msmtp 1.4.5-1, the line "220 begin TLS" is followed by > > "TLS certificate information:" etc. > > I have the same result with msmtp 1.4.6-1 and an exim4 server with a > self-signed > certificate. > > > I can provide the server name in private email, if it is needed for > > troubleshooting. It seems to me that the username and password will > > be sent only after the TLS handshake has completed. > > Yes, please send me the server name, i try will do some checks. > msmtp 1.4.5-1 was accidentally linked against libssl, did you remember if > previous versions worked ?
Does the bug still appear in the current (1.4.6-2) version ? Some more info about the server would be appreciated. Thanks -- Day of inquiry. You will be subpoenaed.
