--On Saturday, September 25, 2004 00:21:44 -0400 David Brodbeck <[EMAIL PROTECTED]> wrote:
For example, it would break the Exim port which by default includes the ExiScan patches. (The Exim port would still build; but the SpamAssassin support would fail at run time.)
Sure about that? I'm running Exim with Exiscan version 22, built from the port, and it's working fine with SpamAssassin 3.0.
Are you using SA via the spam ACL clauses; or do you have it set up as a filter?
In the past, ExiScan has had to be updated to adapt to changes to the SpamAssasin output. The last couple of updates have supported both of the most recent 2.x SA versions; but I've seen nothing about 3.0 support. I'm not certain that it won't work; but I wouldn't expect it to. Even if it appears to work, I wouldn't trust it until there's been an announcement on the Exim lists.
And, just as a note, the latest ExiScan is 27, for Exim 4.42.
-Pat
