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.
Description of problem:
An out of the box configuration creates reports with an impossible from email address.
The address is not from a “real” user or alias or an obvious fake/no-replay address.
The FQDN is invalid, as a concatenation of localhost and the domain portion.
Version-Release number of selected component (if applicable):
libreport-plugin-mailx-2.0.9-19
How reproducible:
Always
Steps to Reproduce:
1. have the SMTP set to forward email to you…
2. cause a crash / core dump …
3. view headers of received email.
Actual results:
Email headers:
Return-Path: <user.pdinc.us>
Received: from five-72.internal.pdinc.us (nsa1.pdinc.us [67.90.184.2])
by mail.pdinc.us (8.12.11.20060308/8.12.11) with ESMTP id s41CJvOn032440
Expected results:
Return-Path: <root.pdinc.us>
Received: from five-72.internal.pdinc.us (nsa1.pdinc.us [67.90.184.2])
by mail.pdinc.us (8.12.11.20060308/8.12.11) with ESMTP id s41CJvOn032440
or
Return-Path: <mailer-daemon.pdinc.us>
or
Return-Path: <root>
or
Return-Path: <DoNotReply>
or
Etc…
Additional info:
May be caused by:
[from mailx man page]
-S variable[=value]
Sets the internal option variable and, in case of a string option, assigns value to it. Note, that when setting from variable, domain name of
host is automatically added if value does not contain any. If you want to enter from address with owner’s name, you can use, for example, fol-
lowing format: -S "from=System User <DoNotReply>"
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.
http://rhn.redhat.com/errata/RHBA-2014-1572.html
I don't know if I should report new bug about this or not, but this change makes inconsistence between EL6 and EL7.
Also, not it's impossible to configure ABRT mails using /etc/libreport/plugins/mailx.conf cause it's just not used in Mailx anymore (which still works in EL7!).
Since we're migrated a lot servers to EL7 we didn't saw problem until today, when I was segfault in dmesg, but no mail. And I found out this "fix" which destroyed configuring mailx via that file.
Why you didn't just add that file with those default values? Should I configure /etc/libreport/events.d/mailx_event.conf then instead of /etc/libreport/plugins/mailx.conf? How certain can be it won't change later again?
Description of problem: An out of the box configuration creates reports with an impossible from email address. The address is not from a “real” user or alias or an obvious fake/no-replay address. The FQDN is invalid, as a concatenation of localhost and the domain portion. Version-Release number of selected component (if applicable): libreport-plugin-mailx-2.0.9-19 How reproducible: Always Steps to Reproduce: 1. have the SMTP set to forward email to you… 2. cause a crash / core dump … 3. view headers of received email. Actual results: Email headers: Return-Path: <user.pdinc.us> Received: from five-72.internal.pdinc.us (nsa1.pdinc.us [67.90.184.2]) by mail.pdinc.us (8.12.11.20060308/8.12.11) with ESMTP id s41CJvOn032440 Expected results: Return-Path: <root.pdinc.us> Received: from five-72.internal.pdinc.us (nsa1.pdinc.us [67.90.184.2]) by mail.pdinc.us (8.12.11.20060308/8.12.11) with ESMTP id s41CJvOn032440 or Return-Path: <mailer-daemon.pdinc.us> or Return-Path: <root> or Return-Path: <DoNotReply> or Etc… Additional info: May be caused by: [from mailx man page] -S variable[=value] Sets the internal option variable and, in case of a string option, assigns value to it. Note, that when setting from variable, domain name of host is automatically added if value does not contain any. If you want to enter from address with owner’s name, you can use, for example, fol- lowing format: -S "from=System User <DoNotReply>"