On 11/02/2013 12:10 PM, Tim Whitaker wrote:
Thanks for all the responses and feedback, here's where I'm at.
I definitely do not have Spamdyke installed, I'm about to try that.
"Check in logs in /var/log/qmail/smtp for simscan entries, like this:"
I just grepped the entire directory and there are no CLEAN entries anywhere.
"In my logs in /var/log/qmail/spamd I see entries like this when
SpamAssassin analyzes a message:"
I don't see anything like that in my logs, this is what my logs look like:
@4000000052691c611110d3ec Oct 24 09:10:47.272 [2095] info: spamd: server
successfully spawned child process, pid 2364
@4000000052691c611110d7d4 Oct 24 09:10:47.277 [2095] info: spamd: server
successfully spawned child process, pid 2365
@4000000052691c611110dbbc Oct 24 09:10:47.279 [2095] info: prefork: child
states: II
@4000000052730d082650ad7c Oct 31 22:07:58.558 [2095] info: spamd: server
killed by SIGTERM, shutting down
@4000000052730d100438a294 Oct 31 22:08:06.071 [16622] info: spamd: server
started on port 783/tcp (running version 3.3.2)
@4000000052730d10043b1b64 Oct 31 22:08:06.071 [16622] info: spamd: server
pid: 16622
@4000000052730d10048781fc Oct 31 22:08:06.076 [16622] info: spamd: server
successfully spawned child process, pid 16692
@4000000052730d1004dac27c Oct 31 22:08:06.081 [16622] info: spamd: server
successfully spawned child process, pid 16693
@4000000052730d1004f07cfc Oct 31 22:08:06.083 [16622] info: prefork: child
states: II
I'm starting to think my original suspicions are correct... it doesn't
appear to be filtering anything at all, just running.
Tim-
I agree it looks like SpamAssassin is running but not processing
anything. This leads me to think that SpamAssassin may not be
configured properly.
Will you post the output of this command:
sudo -u vpopmail -H spamassassin -D --lint 2>&1
This causes SpamAssassin to generate some diagnostic output.
sudo -u vpopmail -H causes SpamAssassin to run in the context of the
vpopmail user, which is how SpamAssassin normally runs.
When you say there are no CLEAN entries it makes me wonder if there are
problems with simscan. Are there any other simscan entries in the
logs? In my logs I see entries like this:
<timestamp> simscan:[<pid>]:ATTACH:<more info>
<timestamp> simscan:[<pid>]:CLEAN <more info>
<timestamp> simscan:[<pid>]:SPAM REJECT <more info>
<timestamp> simscan:[<pid>]:VIRUS:<more info>
Regards,
Brent Gardner
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
