I'm not sure that one can sign up any more. I'll see if I can figure
something out, or if someone knows better, please speak up.
On 2/16/2017 10:00 AM, Chris wrote:
If the wiki is open to community editing, I'm happy to add updates to
legacy pages where the functionality has moved or changed.
-Chris
On Wed, Feb 15, 2017 at 12:33 PM, Eric Broch <[email protected]
<mailto:[email protected]>> wrote:
It's the same as my centos 6 run scripts, in fact that's where I
got the original src rpms for centos 7. I think Eric Shubert had
spamdyke in mind.
On 2/15/2017 1:26 PM, Chris wrote:
I gotta ask, while you said this was a stock QMT install, when
was it built?
I literally, in the last twenty minutes, spun up a new CentOS 7
VM, and installed QMT via the instructions and scripts from
http://www.qmailtoaster.com/, and I have a different
/var/qmail/supervise/smtp/run from you:
#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SPAMDYKE="/usr/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
On Tue, Feb 14, 2017 at 9:52 AM, CarlC Internet Services Service
Desk <[email protected] <mailto:[email protected]>> wrote:
Chris,
I loaded a stock QMT install, and in
/var/qmail/supervise/smtp/run, it has the line:
BLACKLIST=`cat /var/qmail/control/blacklists`
Which is used by SMTP before SPAMDYKE is called:
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 \
$RBLSMTPD $BLACKLIST \
$SPAMDYKE --config-file $SPAMDYKE_CONF \
$SMTPD $VCHKPW /bin/true 2>&1
I would think you could use either blacklists in
/var/qmail/control/ or the spamdyke config. Either should
work... Using RBL to block it might be faster/less load on
the server than waiting for SpamDyke to startup, but either
way will work.
And for blacklist in /var/qmail/control/blacklists, mine is:
-r b.barracudacentral.org
<http://b.barracudacentral.org> -r bl.spamcop.net
<http://bl.spamcop.net> -r zen.spamhaus.org
<http://zen.spamhaus.org> -r cbl.abuseat.org
<http://cbl.abuseat.org> -r dul.dnsbl.sorbs.net
<http://dul.dnsbl.sorbs.net>
Note: to use barracudacentral, you must sign up with them and
give them your IP address to allow access. So don't
Copy/Paste this unless you're signed up with barracuda. It is
free, and barracuda only blocks KNOWN/HARD spammers.
In either case, you would see the blocks in the
/var/log/qmail/smtp/current [or other files in that area].
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail:
[email protected]
<mailto:[email protected]>
For additional commands, e-mail:
[email protected]
<mailto:[email protected]>
--
Eric Broch, IMSO, DAM, NGOO, DITH, URTS
White Horse Technical Consulting (WHTC)
--
Eric Broch, IMSO, DAM, NGOO, DITH, URTS
White Horse Technical Consulting (WHTC)
