Description of problem: Using STARTTLS and authentication to send mails does not work. Version-Release number of selected component (if applicable): 8.17.1-6 How reproducible: every time Steps to Reproduce: 1. setup sendmail.mc to use SSL with authentication 2. 3. Actual results: No AUTH available: 04924 >>> 220 hoyer.xyz ESMTP Sendmail 8.17.1/8.17.1; Sat, 5 Nov 2022 15:28:21 +0100 04924 <<< EHLO [192.168.178.156] 04924 >>> 250-hoyer.xyz Hello p5b0acefd.dip0.t-ipconnect.de [91.10.206.253], pleased to meet you 04924 >>> 250-ENHANCEDSTATUSCODES 04924 >>> 250-PIPELINING 04924 >>> 250-8BITMIME 04924 >>> 250-SIZE 04924 >>> 250-DSN 04924 >>> 250-STARTTLS 04924 >>> 250-DELIVERBY 04924 >>> 250 HELP 04924 <<< STARTTLS 04924 >>> 220 2.0.0 Ready to start TLS 04924 <<< EHLO [192.168.178.156] Expected results: Additional info: see also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263287 Solution seems to be: https://cgit.freebsd.org/ports/commit/?id=0625156b336bacba1e5dc541680af85e97feb0e2
Downgrading to F36 version works again: # rpm -q sendmail cyrus-sasl sendmail-8.17.1-5.fc36.x86_64 cyrus-sasl-2.1.27-18.fc36.x86_64
Complete log after STARTTLS: [root@hoyer harald]# cat /tmp/test.log 04924 >>> 220 hoyer.xyz ESMTP Sendmail 8.17.1/8.17.1; Sat, 5 Nov 2022 15:28:21 +0100 04924 <<< EHLO [192.168.178.156] 04924 >>> 250-hoyer.xyz Hello p5b0acefd.dip0.t-ipconnect.de [91.10.206.253], pleased to meet you 04924 >>> 250-ENHANCEDSTATUSCODES 04924 >>> 250-PIPELINING 04924 >>> 250-8BITMIME 04924 >>> 250-SIZE 04924 >>> 250-DSN 04924 >>> 250-STARTTLS 04924 >>> 250-DELIVERBY 04924 >>> 250 HELP 04924 <<< STARTTLS 04924 >>> 220 2.0.0 Ready to start TLS 04924 <<< EHLO [192.168.178.156] 04924 >>> 250-hoyer.xyz Hello p5b0acefd.dip0.t-ipconnect.de [91.10.206.253], pleased to meet you 04924 >>> 250-ENHANCEDSTATUSCODES 04924 >>> 250-PIPELINING 04924 >>> 250-8BITMIME 04924 >>> 250-SIZE 04924 >>> 250-DSN 04924 >>> 250-DELIVERBY 04924 >>> 250 HELP 04924 <<< MAIL FROM:<harald> BODY=8BITMIME SIZE=476 04924 >>> 530 5.7.0 Authentication required 04924 <<< [EOF]
FEDORA-2022-dd2a34a033 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-dd2a34a033
FEDORA-2022-36db63d44f has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-36db63d44f
FEDORA-2022-36db63d44f has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-dd2a34a033 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-dd2a34a033` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-dd2a34a033 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thanks! Works!
*** Bug 2143412 has been marked as a duplicate of this bug. ***
*** Bug 2144614 has been marked as a duplicate of this bug. ***
FEDORA-2022-dd2a34a033 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.