It's a couple of weeks now I'm running mail-filter/spamassassin-3.1.7 by mean of mail-filter/amavisd-new-2.4.1 on a mail-mta/postfix-2.2.10 with mail-filter/dcc-1.3.24, dev-python/pyzor-0.4.0-r2, mail-filter/razor-2.82 and app-antivirus/clamav-0.90_rc2 (also tried with app-antivirus/clamav-0.88.5). I'm having no problems at all and the new sa-update tool is really awesome. I would suggest to "stable" mail-filter/spamassassin-3.1.7. This is also because this is a version fixing some troubles afflicting previous ones. Regards, giampaolo
Also no problems here with the following packages: mail-filter/spamassassin-3.1.7 (installation date: Nov 20 2006) mail-filter/amavisd-new-2.3.3-r2 mail-filter/dcc-1.3.24 dev-python/pyzor-0.4.0-r2 mail-filter/razor-2.82 app-antivirus/clamav-0.88.7 I would also suggest to stable mail-filter/spamassassin-3.1.7
is spamd used spamassassin needs Net::Ident perl module i dont know if this is just 3.1.7 that have this requirements one of the devs on spamassassin says it on maillist but if spamd is not used i admit spamassassin is stable i just have 2 bugs that is not gentoo fault since its core sa not gentoo spamassassin --lint will if run as root create /./spamassassin/ and not ~/.spamassassin so files is created non chroot'ed, i belive this is so it olso works for windows users in perl code ? but in gentoo its a secureity problem no ?
(In reply to comment #2) > is spamd used spamassassin needs Net::Ident perl module i dont know if this is > just 3.1.7 that have this requirements > one of the devs on spamassassin says it on maillist > but if spamd is not used i admit spamassassin is stable I guess that the need for a further perl module doesn't mean SA 3.1.7 is not stable. The Net::Ident dependency can easily be included into the SA ebuild. > i just have 2 bugs that is not gentoo fault since its core sa not gentoo So you would suggest to wait for a SA version fixing this also? > spamassassin --lint will if run as root create /./spamassassin/ and not > ~/.spamassassin > so files is created non chroot'ed, i belive this is so it olso works for > windows users in perl code ? Mmmm. Better ask upstream, but I guess windows compatibility has few to do with this. Also, you probably mean that "files are created not user home's-rooted": chroot is another matter which can't actually be applied to SA. > but in gentoo its a secureity problem no ? I don't see how: the .spamassassin dir is created with 0750 permissions and root user and group. Inside it, files' permissions have 'x' bit set. A non-root user can't read them a even less modify them. It would be better to have this dir in ~/, however. But it is not a big deal. The important matter are the "2 bugs" you spoke above, anyway. Do you know if they got fixed in a later SA version?
3.1.8 has been marked stable. See bug #166969.
