Right, I've got somewhere...
I've just built from CVS and checked the changelog, and as far as I can
tell there's been no change that would resolve this problem. Can anyone
confirm that if dspam --deliver (with --source=error) fails because of a
missing signature then an error is logged but the return code is 0?
There appears to be a genuine bug here, I just need to confirm it
applies to current builds. Unless anyone can tell me otherwise it looks
like releasing an email from quarantine after its signature has expired
will cause the email (which is ham not spam) to be lost.
I have fixed this (horribly!) on my system temporarily by removing
--deliver from the cgi code and sending emails via sendmail immediately
after I retrain, but it's not pretty.
[PS: I now have 3.8's dspam.cgi from the above process so ignore my
requests for a copy.]
--
Mark Rogers // More Solutions Ltd (Peterborough Office) // 0845 45 89 555
Registered in England (0456 0902) at 13 Clarke Rd, Milton Keynes, MK1 1LG
!DSPAM:1011,488628ce150921612819075!
