RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

cyrus-sasl should provide /etc/(sasl2/)saslauthd.conf.

postfix provides a basic /etc/sasl2/smtpd.conf that integrates postfix with cyrus-sasl.

/etc/saslauthd.conf is a required configuration file if you choose MECH=ldap in /etc/sysconfig/saslauthd.

Some package should provide /ets/saslauthd.conf as it is in essential configuration file for cyrus-sasl/openldap integration. If cyrus-sasl doesn't provide saslauthd.conf openldap-servers is the most likely alternative to do so.

cyrus-sasl upstream doesn't provide saslauthd.conf file. Default package configuration uses pam mechanismus. In adition, there is /usr/share/doc/cyrus-sasl-2.1.23/LDAP_SASLAUTHD file with instruction how to use auth_ldap module.

All the patches RHEL uses aren't provided by any of the upstream distributors. Upstream not providing the file is not a valid argument.

So instead of providing this file and tagging it %config you'd rather have this file orphaned and not belonging to the package cyrus-sasl? So much for clarity and straight forwardness.

And yes, I am aware of LDAP_SASLAUTHD. The point of the request for inclusion is that it makes things more obvious. If people have to figure out every detail of their system what's the point of a distribution in the first place? Adding this configuration file with an example setup and the comment that it only needs to be configured when using MECH=ldap saves users a bit of time having to figure out how to setup their system.

Please reconsider.