Bug 464207

Summary:	postfix plugin for sos name does not fit naming convention (too general) and add postconf.
Product:	Red Hat Enterprise Linux 5	Reporter:	Eric Sammons <esammons>
Component:	sos	Assignee:	Adam Stokes <astokes>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.4	CC:	agk, astokes, azelinka, bmr, syeghiay
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, the sos plugin that collects postfix data was simply named mail.py. This name was too general to be meaningful, and was not consistent with the naming of other plugins. The plugin is now named postfix.py, which better describes what data it collects.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-02 07:30:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eric Sammons 2008-09-26 18:12:27 UTC

Description of problem:

The sos plugin that collects postfix data is name mail.py, while the sendmail plugin is name sendmail.py.  mail.py should be renamed to postfix.py to remain consistent with other plugins.  In addition, I would like to suggest adding the postconf command (output) to the plugin.

Comment 8 Ruediger Landmann 2009-09-02 05:15:57 UTC

Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Previously, the sos plugin that collects postfix data was simply named mail.py. This name was too general to be meaningful, and was not consistent with the naming of other plugins. The plugin is now named postfix.py, which better describes what data it collects.

Comment 9 errata-xmlrpc 2009-09-02 07:30:24 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1418.html