On 03/12/2014 03:59 AM, Scot Needy wrote:
Yea I got, that but I’m a little confused on how one would have multiple
mail scanners operating on a msg in flight to a forward.
This is how I think that’s working.
/
/
//
/The supervise script runs both symscan and spamdyke via the supervise
script. /
/tcprules/tcp.smtp run’s simscan via QMAILQUEUE /
/
/
/Then spamdyke is initiated from the run script. /
/
/
/[bash]# cat /var/qmail/supervise/smtp/run/
/#!/bin/sh/
/QMAILDUID=`id -u vpopmail`/
/NOFILESGID=`id -g vpopmail`/
/MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`/
/SPAMDYKE="/usr/local/bin/spamdyke"/
/SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"/
/SMTPD="/var/qmail/bin/qmail-smtpd"/
/TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"/
/HOSTNAME=`hostname`/
/VCHKPW="/home/vpopmail/bin/vchkpw"/
/REQUIRE_AUTH=0/
/
/
/exec /usr/bin/softlimit -m 64000000 \/
/ /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \/
/ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \/
/ $SPAMDYKE --config-file $SPAMDYKE_CONF \/
/ $SMTPD $VCHKPW /bin/true 2>&1/
/
/
I don’t think spamassasin is running at all in my install.
To get spamassasin up and running correctly I need to update my tcp.smtp
QMAILQUEUE
From
QMAILQUEUE="/var/qmail/bin/simscan”
To
QMAILQUEUE="/var/qmail/bin/qmail-queue”
This, ironically, would turn off all scanning.
Check the spamd log to see if spamassassin is running:
# qmlog spamd
(use the -f option to tail)
Here's how it works.
In the run file, tcpserver invokes spamdyke, which invokes qmail-smtpd.
So spamdyke is on the front end, and it feeds qmail-smtpd. spamdyke
doesn't really do any scanning per se, it simply checks out some things
(mostly related to the sender's IP address) and passes stuff on to
qmail-smtpd.
Once qmail-smtpd receives a complete message, the QMAILQUEUE program is
invoked, which normally is simscan. Note, at this point, spamdyke and
qmail-smtpd are essentially done, but still connected to the sending
server. simscan then invokes clamav and spamd to do actual scanning.
When those are done, simscan passes results back to spamdyke/qmail-smtpd
to finish up the session, either rejecting or accepting the message.
That's the gist of that part. When the message is accepted, there's a
whole nother set of processes that happen for delivery.
Welcome to qmail. ;)
On Mar 12, 2014, at 6:34 AM, Eric Shubert <[email protected]
<mailto:[email protected]>> wrote:
On 03/12/2014 02:41 AM, Scot Needy wrote:
So I installed spamdyke using /usr/sbin/qtp-install-spamdyke thinking
that would replace my spam engine but from the logs and your comment
I’m guessing I need to uninstall spamassasin as I still see simscan
in the logs from tcprules.
Don't get me wrong, I'd still keep spamassassin. There are times when
you want to flag things and not outright reject them, ans SA is good
at that. I was simply speculating *IF I had to pick just one*. They
happily work side by side as it is.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail:
[email protected]
<mailto:[email protected]>
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
