Created attachment 1926216 [details] sendmail.mc Created attachment 1926216 [details] sendmail.mc Description of problem: After upgrading from F36 to F37, sending emails was no longer possible. Sendmail did not start the authentication process and/or did not accept user/password any longer. I have been using my sendmail.mc for the past 10 years and it worked perfectly until I upgraded to F37. Turns out that the following directive breaks the sending functionality (authenticated submission via implicit TLS): define(`confAUTH_OPTIONS', `A p y')` After changing it to define(`confAUTH_OPTIONS', `p y')` sendmail starts working again. Version-Release number of selected component (if applicable): sendmail-8.17.1-6.fc37.x86_64 How reproducible: Steps to Reproduce: 1. setup sendmail to send emails via submissions on 465 with authentication 2. send email Actual results: Error message: Relaying denied. Proper authentication required. Server logs show that authentication was not even initiated. Expected results: The client should authenticate against the server and the mail should be sent. Additional info: The mail client is irrelevant. I haven't changed it for a long time (not even upgraded it, since I need its functionality that was removed with a later version), but I have also tried other (newer and most recent) mail cilents. For completeness I will attach my sendmail.mc (even though I don't think it will help, except for you to see that I didn't screw up my config.)
*** This bug has been marked as a duplicate of bug 2140596 ***
Interesting. testsaslauthd works just fine (which is something I forgot to mention in my bug report), so I guess sendmail's integration with SASL is borked and not sasl itself.