That's my understanding, but I don't use it myself. Jake (or someone
other than me) would have the definitive answer on that.
Maxwell Smart wrote:
OK, now I'm confused.
Does this mean that if the box is not "ticked" that SPAM mail will make
it to your POP3 inbox marked as SPAM?
CJ
Eric Shubert wrote:
spambox doesn't have anything to do with scanning messages, it only
takes effect during delivery after a message has been scanned and accepted.
You may have done this before, but even if so, will you do it again? I'd
like to see the contents of:
cat /etc/tcprules.d/tcp.smtp
cat /var/qmail/control/simcontrol
Also, do you see any simscan messages in your smtp log, like this:
08-10 18:05:43 simscan:[13851]:CLEAN (5.30/12.00):8.7898s:[SPAM] ...
# qmlog -lc simscan smtp
will find them for you.
Mike Canty wrote:
Jake,
You mention the compiled rules. In an effort to see what is
happening to Spamassassin I looked at you video on how to speed up
Spamassassin
(http://video.qmailtoaster.com/files/movies/mbr005/ep5-full.mov) and
followed all the steps, so effectively I am now running the compiled
rules.
Regardless, Spamassassin does not appear to scan mail either way. All
the
tests I run show that Spamassassin is operational and error free, but
nothing seems to pass through.
Could a problem have occurred when I ran the steps from an earlier
version
where we turned on the Spambox for all users.
rpmbuild --rebuild --with cnt50 --define 'spambox 1'
qmailadmin-toaster-1.2.12-1.3.8.src.rpm
There is a "tick box" for each user in qmailadmin to turn on/off "Spam
detection". This is currently not ticked on all users. Do I need to
manually "tick" each, or is the "spambox1" part of the rebuild script to
manage this?
Any assistance would be appreciated.
Cheers
-----Original Message-----
From: Jake Vickers [mailto:[email protected]] Sent: Monday, 10
August 2009 8:19 PM
To: [email protected]
Subject: Re: [qmailtoaster] Spamassassin Errors - Still
Mike Canty wrote:
First of all, thanks to those who assisted me in installing the correct
Perl
modules for Spamassasin to operate correctly. I can now run "tail -f
/var/log/qmail/spamd/current | tai64nlocal" and not see any errors.
However, this just takes me back to my initial problem I presented to
Jake
Vickers, in that Spamassassin appears not to be checking my mail.
When I
check the log, there are no errors, but the log is not being appended
to.
Below are the last 6 lines of the log, where spamassassin is stopped and
restarted. Nothing appears after this.
2009-08-10 17:07:49.404383500 [20983] info: spamd: server killed by
SIGTERM,
shutting down
2009-08-10 17:08:06.951150500 [22001] info: spamd: server started on
port
783/tcp (running version 3.2.5)
2009-08-10 17:08:06.951207500 [22001] info: spamd: server pid: 22001
2009-08-10 17:08:06.958022500 [22001] info: spamd: server successfully
spawned child process, pid 22038
2009-08-10 17:08:06.965582500 [22001] info: spamd: server successfully
spawned child process, pid 22039
2009-08-10 17:08:06.967421500 [22001] info: prefork: child states: II
I have receive message from outside of my network and there is a no
information on the spamassassin count in the header information.
I have updated the base install of Qmail-toaster for CentOS 5.3 with
compiled ruleset shown in
http://video.qmailtoaster.com/files/movies/002/ep2-1.mov and I have
installed "Plus".
Can someone assist me with the setup of Spamassassin, especially with
where
I might have gone wrong.
Does it scan if you turn the compiled rules off?
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
