I apologize, I believe I've figured it out. The culprit was a lingering qmailctl script that I hadn't updated properly from an older version.
Updating this script and running qmailctl again seems to have helped simscan to function properly. My /var/log/spamd/current looked like this when I just sent an email: 2006-05-12 06:01:29.474455500 [2218] info: spamd: connection from localhost [127.0.0.1] at port 45095 2006-05-12 06:01:29.521875500 [2218] info: spamd: processing message <[EMAIL PROTECTED]> for clamav:89 2006-05-12 06:01:29.838356500 [2218] info: spamd: clean message (0.3/5.0) for clamav:89 in 0.4 seconds, 1355 bytes. 2006-05-12 06:01:29.838800500 [2218] info: spamd: result: . 0 - RCVD_BY_IP scantime=0.4,size=1355,user=clamav,uid=89, required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=45095,mid=<[EMAIL PROTECTED]>,autolearn=no 2006-05-12 06:01:29.968121500 [4948] info: prefork: child states: II The headers on the received email also show the Spamassassin addition: Received: by simscan 1.2.0 ppid: 2627, pid: 2628, t: 0.9050s scanners: attach: 1.2.0 clamav: 0.88.1/m:38/d:1456 spam: 3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mailserver.exampleserver.com X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=RCVD_BY_IP autolearn=no version=3.1.1 Well, thanks anyway - maybe this entry in the list archives will help all the other Clark Griswalds like me out there;) -Brian -- <>
