Bug 11245

Summary: amavisd-new doesn't really require spamassassin-spamd and spamassassin-spamc
Product: Mageia Reporter: Luca Olivetti <luca>
Component: RPM PackagesAssignee: Thomas Spuhler <thomas>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal    
Version: 2   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: amavisd-new-2.7.0-2.mga2.src.rpm CVE:
Status comment:

Description Luca Olivetti 2013-09-17 13:01:33 CEST 
According to the release notes, since 2002 amavisd-new doesn't need spamd:

"Amavisd calls Mail::SpamAssassin directly, avoiding the need to set up
  spamc/spamd or to chain filters. This is more efficient, one daemon
  less to worry about, although maybe less flexible for some taste.
  At the moment the SA per-user database is not used. Feel free to
  experiment with it and let me know what you came up with."

so those requires should be dropped.
In fact, I think that even spamassassin itself isn't required (the Requires on perl-Mail-Spamassassin should be enough), the only thing needed from that package is probably "sa-update" (which in turn has a cron job in spamassassin-spamd, but it doesn't trigger a reload of the rules by amavisd-new).

Note that I noticed this bug in mageia 2 (where I just removed spamassassin-spamd and spamassassin-spamc using --nodeps), but I checked the spec in svn and those Requires are still there.
Luca Olivetti 2013-09-17 13:02:19 CEST

Source RPM: (none) => amavisd-new-2.7.0-2.mga2.src.rpm

Manuel Hiebel 2013-09-18 12:04:12 CEST

Assignee: bugsquad => thomas

Comment 1 Thomas Spuhler 2013-10-03 02:05:05 CEST 
I see this.
I will make the change in cauldron and get some test results.
I am not going to update mga2 since it's close to EOL

Status: NEW => ASSIGNED

Comment 2 Thomas Spuhler 2013-10-05 02:24:36 CEST 
It seems there is no issue when removing them (in cauldron). I will keep watching it, but will close the bug.
I don't see an advantage of removing the Requires in mga3 and keep our scarce QA resources busy.
It's working, you solved your problem and there were no other bug reports.
Mageia 2 is close to EOL:
Mageia 2 will be supported until November 22nd, 2013.

Status: ASSIGNED => RESOLVED
Resolution: (none) => WONTFIX