Bug 1333910

Summary:	dspam-web package doesn't create "dspam" user
Product:	[Fedora] Fedora EPEL	Reporter:	Gary T. Giesen <ggiesen+redhat>
Component:	dspam	Assignee:	Orphan Owner <extras-orphan>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	nathanael, perl-devel
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-09 15:36:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gary T. Giesen 2016-05-06 16:00:59 UTC

Description of problem:
The dspam-web package doesn't create "dspam" user. If you install it then restart httpd without either adding the user or modifying the dspam-web.conf file to use another user for SuexecUserGroup, then httpd will die on restart because the user doesn't exist. 

Version-Release number of selected component (if applicable):
3.10.2-11

How reproducible:
Always

Steps to Reproduce:
1. Install dspam-web
2. Restart httpd

Actual results:
httpd fails to restart

Expected results:
httpd restarts successfully without having to manually create the user or modify the config file.

Comment 1 Nathanael Noblet 2016-08-31 15:40:54 UTC

Sorry for the delay on responding. When you install dspam-web. Does it not bring in dspam + dspam-libs (dspam-libs is where the user is created). Which would result in the user being created? How did you install dspam-web?

Comment 2 Fedora Admin XMLRPC Client 2020-02-21 04:20:56 UTC

This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 3 Troy Dawson 2024-07-09 15:36:13 UTC

EPEL 7 entered end-of-life (EOL) status on 2024-06-30.  EPEL 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.