QA:Testcase ABRT Mailx plugin

Description

This test case tests the functionality of the ABRT feature using the Mailx plugin.

How to test

1. Edit /etc/abrt/abrt.conf to enable and activate the Mailx plugin. A sample config is noted below

# common abrt settings
[ Common ]
# enabled plugins
# there has to be exactly one database plugin
EnabledPlugins = Mailx, SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python
# reporters association with analyzers
[ AnalyzerActionsAndReporters ]
CCpp = Mailx, Bugzilla, Logger
Python = Mailx, Bugzilla, Logger

1. Edit /etc/abrt/plugins/Mailx.conf and make sure the configuration is valid. The default configuration:

# Configuration to Email reporter plugin
# Parameters
Parameters =

# Your Email
EmailFrom = user@localhost

# Email To
EmailTo = root@localhost

# Warning! enabling this may cause sending a lot of MB via email
SendBinaryData = no

should work. Only change the EmailTo address to a public address that would require forwarding through a real SMTP server if you have the 'mailx' configuration set so that such mails are correctly handled.

Restart ABRT:

# service abrt restart

And final steps are:

1. Ensure that the abrt and abrt-applet processes are both running
2. Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
3. Click on the panel applet to start abrt-gui
4. Select the entry matching the recently crashed application, select Generate
5. At the report window, click Apply

Expected Results

1. A mail reporting the crash should be sent to the email address specified in /etc/abrt/plugins/Mailx.conf. If you left this set to root@localhost, you should be able to see the mail in the file /var/spool/mail/root in a default Fedora setup or via command mail as a root.