Bug 1323625 - reporter-mailx fails for blank spaces in /etc/libreport/plugins/mailx.conf
Summary: reporter-mailx fails for blank spaces in /etc/libreport/plugins/mailx.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libreport
Version: 6.8
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Martin Kutlak
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 1236613
Blocks: 1518652
TreeView+ depends on / blocked
 
Reported: 2016-04-04 09:44 UTC by Jakub Filak
Modified: 2018-06-19 05:17 UTC (History)
12 users (show)

Fixed In Version: libreport-2.0.9-34.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1236613
Environment:
Last Closed: 2018-06-19 05:17:06 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1892 0 None None None 2018-06-19 05:17:33 UTC

Description Jakub Filak 2016-04-04 09:44:29 UTC
+++ This bug was initially created as a clone of Bug #1236613 +++

Description of problem:
reporter-mailx fails if there are blank spaces before parameters in /etc/libreport/plugins/mailx.conf

Version-Release number of selected component (if applicable):
libreport-plugin-mailx-2.1.11-23.el7_1.x86_64
abrt-2.1.11-22.el7_1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Enter the Email Subject, Sender and Recipient details in `/etc/libreport/plugins/mailx.conf`
=====================
  5 #
  6 # String parameters:
  7  Subject="[abrt] a crash has been detected"
  8  EmailFrom="root@localhost"
  9  EmailTo="test@localhost"
 10 #
 11 # Boolean parameter:
 12 # SendBinaryData=yes/no
=====================

2. Kill a process by sending SIGSEGV signal.
# /bin/sleep 60 &
[1] 12372
[root@dhcp210-48 rpms]# kill -11 12372
[1]+  Segmentation fault      (core dumped) /bin/sleep 60

3. Email isn't send to test@localhost, instead defaults to "root@localhost".

Actual results:
/var/log/messages :
Jun 29 19:42:37 dhcp210-48 gnome-session: abrt-applet: repeated problem in coreutils-8.22-11.el7, not showing the notification
Jun 29 19:42:37 dhcp210-48 abrt-server: Email address of sender was not specified. Would you like to do so now? If not, 'user@localhost' is to be used [y/N] 
Jun 29 19:42:37 dhcp210-48 abrt-server: Email address of receiver was not specified. Would you like to do so now? If not, 'root@localhost' is to be used [y/N] 
Jun 29 19:42:37 dhcp210-48 abrt-server: Sending an email...
Jun 29 19:42:37 dhcp210-48 abrt-server: Email was sent to: root@localhost  <--====

Expected results:
Jun 29 19:43:54 dhcp210-48 abrt-server: Sending an email...
Jun 29 19:43:54 dhcp210-48 abrt-server: Email was sent to: "test@locahost"

Additional info:

Workaround is to remove the blank spaces.
====================
#
#String parameters:
Subject="[abrt] a crash has been detected"
EmailFrom="root@localhost"
EmailTo="test@locahost"
#
# Boolean parameter:
# SendBinaryData=yes/no
=====================

/var/log/messages :
Jun 29 19:43:54 dhcp210-48 abrt-server: DUP_OF_DIR: /var/tmp/abrt/ccpp-2015-06-24-17:47:44-20013
Jun 29 19:43:54 dhcp210-48 abrt-server: Deleting problem directory ccpp-2015-06-29-19:43:47-10397 (dup of ccpp-2015-06-24-17:47:44-20013)
Jun 29 19:43:54 dhcp210-48 gnome-session: abrt-applet: repeated problem in coreutils-8.22-11.el7, not showing the notification
Jun 29 19:43:54 dhcp210-48 abrt-server: Sending an email...
Jun 29 19:43:54 dhcp210-48 abrt-server: Email was sent to: "test@locahost"

--- Additional comment from Richard W.M. Jones on 2016-03-31 18:20:37 CEST ---

Try editing the libreport.aug lens, changing:

    let option = [ key ident . value_sep . value_to_eol . eol ]

to:

    let option = [ del /[ \t]*/ . key ident . value_sep . value_to_eol . eol ]

Comment 9 errata-xmlrpc 2018-06-19 05:17:06 UTC
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://access.redhat.com/errata/RHBA-2018:1892


Note You need to log in before you can comment on or make changes to this bug.