Tests done:
1) Build and install from snf-server-3.0.12.tar.gz.
2) 'SNFClient -status.second' gives expected response.
3) 'SNFClient junkmsg.txt' returned a status of 54.
4) 'SNFClient cleanmsg.txt' returned a status of 0.
git-svn-id: https://svn.microneil.com/svn/PKG-SNF-CS-NIX/trunk@53 233e721a-07f6-49eb-a7da-05e0e16828fc
1) snf4sa.pm correctly reads the configuration for SNFServer result of
zero.
2) snf4sa.pm uses static score reporting for spamassassin versions
earlier than 3.2.0.
git-svn-id: https://svn.microneil.com/svn/PKG-SNF-CS-NIX/trunk@51 233e721a-07f6-49eb-a7da-05e0e16828fc
Incremented version to 3.0.5. This contains SNF4SA version 0.9.2
(contribution to SA score submitted correctly by
$permsgstatus->{conf}->{scoreset). This addresses the problem with
amavisd-new always having a score of 1.
git-svn-id: https://svn.microneil.com/svn/PKG-SNF-CS-NIX/trunk@21 233e721a-07f6-49eb-a7da-05e0e16828fc