I propose adding a new USE variable sa-exim. The variable would be off by default. When enabled it would cause the Exim ebuild to add the SA-Exim patch to Exim source before building. SA-Exim is an anit-spam patch for Exim that uses SpamAssassin. It also adds support for tarpitting/teergrubing. http://sa-exim.sf.net/ From googling it seems that SA-Exim patch can be used in addition to exiscan/exiscan-acl patch http://lists.merlins.org/archives/sa-exim/2002-October/000179.html http://lists.merlins.org/archives/sa-exim/2002-October/000188.html Assuming this is true, the sa-exim USE variable could be used with the exiscan-acl USE variable I proposed in bug 21302
_that_ would be a great idea. using sa-exim for some time, but manual patching with portage suckz.
http://dman13.dyndns.org/~dman/config_docs/exim-spamassassin/ shows you how to integrate spamassassin with exim without patching exim. exim-4.21 is on it's way into portage.
exiscan-acl for 4.21 supports spam filtering in the mean time. I would expect to be adding sa-exim soon but it doesn't feel like the right time yet. Upstream still seems to be working out issues with "teergrubing"... and hopefully they will have a point release upgrade for 3.0 soon...
exim-4.21 has been added to portage. Please test.
exim-4.22 is currently in portage. sa-exim support is coming. The upstream author was very quick to making a current-exim-source-compatible tarball of sa-exim... version 3.1... This support will be added to the exim ebuild real-soon-like. :)
I am now adding exim-4.24 to portage. exiscan-acl is doing well staying up to date with new releases. I can't say the same for sa-exim For now I am going to stick with exiscan-acl as the "gentoo way" for doing spam filtering and virus scanning in exim unless someone can convince me otherwise.
Please see also Bug 47106.