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.
Source RPM: (none) => amavisd-new-2.7.0-2.mga2.src.rpm
Assignee: bugsquad => thomas
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
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 => RESOLVEDResolution: (none) => WONTFIX