Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
* Prior to this update, the ldap_routing feature did not work as expected. If ldap_routing was used, sendmail reported the "-T<TMPF>" option missing, and the user was required to insert "-T<TMPF>" manually. With this update, the macro for generating configuration for ldap_routing has been fixed, and the user is no longer required to add "-T<TMPF>" manually when using ldap_routing. (BZ#890227)
Description of problem:
When using LDAP-less mail routing, I noticed that m4(1) does not produce a
usable sendmail.cf file. Simply put the following into sendmail.mc:
LDAPROUTE_DOMAIN(`example.net')dnl
FEATURE(`ldap_routing', `hash -o /etc/mail/transport.db', `hash -o /etc/mail/virtusertable.db', `bounce')dnl
Afterwards try to let a new sendmail.cf produce by running m4(1).
$ make -C /etc/mail transport.db all
make: Entering directory `/etc/mail'
*** WARNING: missing -T<TMPF> in first argument of FEATURE(`ldap_routing')
*** WARNING: missing -T<TMPF> in second argument of FEATURE(`ldap_routing')
make: Leaving directory `/etc/mail'
$
Version-Release number of selected component (if applicable):
sendmail-8.14.4-8.el6.x86_64
How reproducible:
Everytime, see above and below.
Actual results:
LDAP-less routing is broken and thus it complains about missing -T<TMPF> all
the time. This issue is already known upstream and has been solved ages ago;
see errata section of http://www.sendmail.com/sm/open_source/download/8.14.4/
or http://www.sendmail.com/sm/open_source/download/8.14.5/?show_rs=true#RS.
Expected results:
Backported patch for sendmail-8.14.4-8.el6 and updated RPM package in RHEL 6.
Additional info:
Yes, there is the workaround to add "-T<TMPF>" yourself, however this doesn't
seem to make much sense in LDAP-less setups.
Comment 6Andrius Benokraitis
2013-10-07 01:34:52 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6, and will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.
Just closing this bug report is not acceptable, especially as it is linked
with ticket 00769705 in the Red Hat customer portal. If you are lacking any
information, you also could have let us know so via an official path or via
an e-mail instead of just closing this report...reopening.
Comment 8RHEL Program Management
2013-10-14 00:06:54 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-1299.html