Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :
1.2.3.:allow,RELAYCLIENT=,RBLSMTPD=,SPAMDYKE=,NOP0FCHECK=1
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file from
spandyke ?
Thx for the info
hello,
I have succesfully installed spamdkye.but i don't want pop3 succesfully users
make rbl
control. to do this how var/qmail/supervise/smtp/run should be ? Thanks
my current config
#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat
Philip wrote:
Hello
I was wondering about how to disable spamdyke by ip range
can we do something like :
1.2.3.:allow,RELAYCLIENT=,RBLSMTPD=,SPAMDYKE=,NOP0FCHECK=1
in tcp.smtp file
or you better add your c-class or any subnet to the whitelist_ip file
from spandyke ?
Thx for the info
I'm not sure I understand the question.
Are you asking if the toaster can be configured to do pop-before-smtp
authorization? I don't believe this is possible, with or without spamdyke.
Spamdyke does not enforce any rules for authenticated connections,
including RBL checking.
Tolga Cengiz wrote:
Heheh
Yes I am using the
whitelist_ip file
you can either enter x.y.z or x.y.z. for a c-class
I was just curious about the tcp.smtp file :)
I know that spamdyke cant use cdb files
-P
Eric Shubert wrote:
Philip wrote:
Hello
I was wondering about how to disable spamdyke by ip range
can we
Ok, I know that in the past to create a whitelist I would create a file
and place it into the /etc/mail/spamassassin. Usually I would call this
the whitelist.cf. Inside the file I would have entries like:
whitelist_from [EMAIL PROTECTED]
whitelist_from [EMAIL PROTECTED]
This however does not
You would want to use the tcprules.d folder only if you were trying to
alter the general processing of inbound messages. As it appears you're
trying to limit only the spamdyke functions, I suggest you look in the
spamdyke config folder (its location is configurable -- I put mine in
the spamassassin config entry for whitelisting should look like:
def_whitelist_from_rcvd [EMAIL PROTECTED]
def_whitelist_from_rcvd [EMAIL PROTECTED]
You can also whitelist entire domains:
def_whitelist_from_rcvd [EMAIL PROTECTED]
This should get you started in the right direction!