Description of problem:
msmtp with gnutls support does not work with an debian exim 4.72-6+squeezy3
Version-Release number of selected component (if applicable):
Try to use TLS with the remote server.
Steps to Reproduce:
1. configure tks, starttls off, tls_certcheck on
2. run msmtp -Sv
Local error: TLS handshake failed: the operation timed out
Remote: A TLS packet with unexpected length was received
no errors should occur
Recompiling the SRPM with OpenSSL makes it work again.
OpenSSL does not support all settings like GnutLS, such as tls_min_dh_prime_bits or tls_priorities.
The problem did not occur with Fedora 17.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This should be fixed already (circa September, 2013). Please test it and if the issue still exists then reopen it.
It is still a problem in Fedora 23:
The remote error was now: TLS error on connection from ... (SSL_accept): error:00000000:lib(0):func(0):reason(0)
TLS client disconnected cleanly (rejected our certificate?)
The local error is still: TLS handshake failed: the operation timed out
The remote server is exim on current stable compiled against OpenSSL.
(In reply to Till Maas from comment #3)
> It is still a problem in Fedora 23:
> The remote error was now: TLS error on connection from ... (SSL_accept):
> TLS client disconnected cleanly (rejected our certificate?)
> The local error is still: TLS handshake failed: the operation timed out
> The remote server is exim on current stable compiled against OpenSSL.
I can't really debug this. I don't have any setup where I can test it. My the only use case for msmtp is to send git patches through gmail.com to those projects who still doesn't use GitHub. Could you please verify this issue still persists in the latest msmtp builds?
I used this commandline to make sure that it would accept the certificate: LANG=C msmtp --serverinfo --tls --tls-certcheck=off -vv
But I got the same error as in comment:3
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
Does this problem still exist? If so, could you please report upstream and annotate this ticket. There is a new website for reporting issues:
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.