There is a well-written comment in the spamassassin ebuilds that explains why taint mode was disabled: # If you are going to enable taint mode, make sure that the bug where # spamd doesn't start when the PATH contains . is addressed, and make # sure you deal with versions of razor <2.36-r1 not being taint-safe. # <http://bugzilla.spamassassin.org/show_bug.cgi?id=2511> and # <http://spamassassin.org/released/Razor2.patch>. Neither of these problems apply any more: the oldest razor release in the tree is 2.77, and the bug with spamd and '.' in the PATH was fixed back in 2003 (not to mention hopefully people are not using '.' in the first place...) So, we should take out this workaround and let spamassassin run in taint mode. Reproducible: Always
Reassigning to maintainer.
Created attachment 210034 [details] spamassassin-3.2.5-r1.ebuild Should let spamassassin run in taint mode.
fixed in 3.3.1-r1
