Bug 201157

Summary:	RPM update replaces amavisd.conf
Product:	[Fedora] Fedora	Reporter:	Dennis Wagelaar <dwagelaar>
Component:	amavisd-new	Assignee:	Steven Pritchard <steve>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	extras-qa
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:	2006-08-05 23:11:54 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 Dennis Wagelaar 2006-08-03 09:19:15 UTC

Description of problem:
When yum automatically updates the amavisd-new rpm, it replaces the amavisd.conf
file (saving the old amavisd.conf as .rpmsave).

Version-Release number of selected component (if applicable):
amavisd-new-2.4.2-2.fc4

How reproducible:
Yum automatic update.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Amavisd restarts and uses new "default" config file.

Expected results:
Amavisd restarts and uses site-specific, customised config file.

Additional info:
When amavisd starts using a default config file, it starts sending spam bounces
(i.e. it starts generating spam) and sends any virus alerts to
virusalert. This has gotten me in trouble with upstream mail operators.

Comment 1 Steven Pritchard 2006-08-03 18:19:18 UTC

The config file is marked %config(noreplace) in the spec.  It should never be 
overwritten.  (On my servers, there is now a /etc/amavisd/amavisd.conf.rpmnew 
as expected.)

The default config in the rpm has $virus_admin and $mailfrom_notify_* set to 
undef and has $final_virus_destiny set to D_DISCARD, so I can't imagine why it 
would be sending any email.

Are you sure you didn't switch from dag or someone else's amavisd-new to the 
one in Extras?

Comment 2 Dennis Wagelaar 2006-08-05 19:11:37 UTC

I indeed switched from dag's amavisd-new rpm (amavisd-new.i386 2.4.1-2.fc4.rf).
The config file location then changed from /etc to /etc/amavisd. Yum probably
did not detect an existing config file?

As for the mails (bounces, alerts) being sent: I was mistaken. These mails were
sent before the installation of the new rpm.

Comment 3 Steven Pritchard 2006-08-05 23:11:54 UTC

(In reply to comment #2)
> I indeed switched from dag's amavisd-new rpm (amavisd-new.i386 
2.4.1-2.fc4.rf).
> The config file location then changed from /etc to /etc/amavisd. Yum 
probably
> did not detect an existing config file?

No, since it isn't in the same location, as far as rpm is concerned they 
aren't the same file.

Cross-repo upgrades are not (and can't be) guaranteed to work.