The tcp.smtp.new file isn't actually used for anything. It's what the
default would be if you didn't already have a tcp.smtp file (which you
had altered).
I don't know what you have that's referring to simcontrol. That's the
name of the config file for simscan in /var/qmail/control/, and doesn't
really need to be referenced anywhere, as the simscan program picks it
up automatically.
The tcp.smtp file should have QMAILQUEUE="/var/qmail/bin/simscan" as one
of the variables for the last/default entry (begins with : ), and any
other entry for which you want to scan messages. This is what causes the
emails to be passed to simscan from qmail-smtpd.
HTH.
--
-Eric 'shubes'
On 04/03/2013 07:29 AM, Matt wrote:
Thanks Eric,
I found that file (tcp.smtp.new - helps if I look!).
It also refers to simscan and not simcontrol.
Should I create a file called simscan or should I change the tcp.smtp.new
file to call simcontrol? Which would be the "correct" way to do it?
Thanks,
Matt
-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: 03 April 2013 14:49
To: [email protected]
Subject: [qmailtoaster] Re: How to check that Spamassassin is working?
Right. It's a config(noreplace) file, because it's typically customized by
admins, and an update shouldn't wipe out those changes. You should find a
tcp.smtp.rpmnew file that contains what would be installed had you not
changed yours. ;)
--
-Eric 'shubes'
On 04/03/2013 06:37 AM, Matt wrote:
Oh!
Just ran through adding QMAILQUEUE="/var/qmail/bin/simscan" again and
it's now working!
I love it when a plan comes together!
Looks like /etc/tcprules.d/tcp.smtp doesn't get updated on install.
Thanks,
Matt
-----Original Message-----
From: Matt [mailto:[email protected]]
Sent: 03 April 2013 14:34
To: [email protected]
Subject: RE: [qmailtoaster] Re: How to check that Spamassassin is working?
This is what I get:
[root@charlie smtp]# qmlog spamd
04-02 23:27:03 Apr 2 18:27:03.887 [23315] info: spamd: server started
on port 783/tcp (running version 3.3.2)
04-02 23:27:03 Apr 2 18:27:03.887 [23315] info: spamd: server pid:
23315
04-02 23:27:03 Apr 2 18:27:03.899 [23315] info: spamd: server
successfully spawned child process, pid 23415
04-02 23:27:03 Apr 2 18:27:03.911 [23315] info: spamd: server
successfully spawned child process, pid 23416
04-02 23:27:03 Apr 2 18:27:03.913 [23315] info: prefork: child
states: IS
04-02 23:27:03 Apr 2 18:27:03.914 [23315] info: prefork: child
states: II
04-03 00:31:25 Apr 3 00:31:25.387 [23315] info: spamd: server killed
by SIGTERM, shutting down
04-03 00:36:55 Apr 3 00:36:55.316 [2979] info: spamd: server started
on port 783/tcp (running version 3.3.2)
04-03 00:36:55 Apr 3 00:36:55.316 [2979] info: spamd: server pid:
2979
04-03 00:36:55 Apr 3 00:36:55.327 [2979] info: spamd: server
successfully spawned child process, pid 3296
04-03 00:36:55 Apr 3 00:36:55.338 [2979] info: spamd: server
successfully spawned child process, pid 3297
04-03 00:36:55 Apr 3 00:36:55.340 [2979] info: prefork: child states:
IS
04-03 00:36:55 Apr 3 00:36:55.341 [2979] info: prefork: child states:
II
<----- repeats lots----------->
04-03 14:00:45 Apr 3 14:00:45.739 [5913] info: spamd: server started
on port 783/tcp (running version 3.3.2)
04-03 14:00:45 Apr 3 14:00:45.739 [5913] info: spamd: server pid:
5913
04-03 14:00:45 Apr 3 14:00:45.751 [5913] info: spamd: server
successfully spawned child process, pid 5998
04-03 14:00:45 Apr 3 14:00:45.762 [5913] info: spamd: server
successfully spawned child process, pid 5999
04-03 14:00:45 Apr 3 14:00:45.764 [5913] info: prefork: child states:
IS
04-03 14:00:45 Apr 3 14:00:45.765 [5913] info: prefork: child states:
II
I have been following the earlier posts here -
http://www.mail-archive.com/[email protected]/msg3449
5.html but I do not have a simscan file, only a simcontrol.
I added " QMAILQUEUE="/var/qmail/bin/simcontrol"" to the end of
/etc/tcprules.d/tcp.smtp as suggested then ran qmailctl cdb. This
resulted in an smtp error on my email client.
Any ideas?
Thanks,
Matt
-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: 03 April 2013 14:27
To: [email protected]
Subject: [qmailtoaster] Re: How to check that Spamassassin is working?
On 04/03/2013 05:26 AM, Matt wrote:
Is there a way to test that Spamassassin is actually checking
messages or have I left something obvious out?
# qmlog spamd
You can also look at the headers of received emails. You'll see the SA
scoring there as well.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
