2008/2/7, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Are most folks using or not using DK? It seems to be an endless pain in
the
butt. Yet again today, more domains not being allowed to send out because
they
can't sign DK.
I don't get the behavior, some domains work, some don't. I'd love to just
be replaced with DKIM. Check the list archive for the proper way to entirely
disable it.
I guess it's as easy as making a backup of the bin directory. That's what I'll
do then follow the wiki. It doesn't say anything about the tcp.smtp file
changes needed though?
What should it look like
127.:allow,RELAYCLIENT=,RBLSMTPD=,NOP0FCHECK=1
192.168.1.:allow,RELAYCLIENT=,RBLSMTPD=,NOP0FCHECK=1
xx.xx.xx.:allow,RELAYCLIENT=,RBLSMTPD=,NOP0FCHECK=1
:allow,BADMIMETYPE=,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER
_WRONGRCPTLIMIT=10,QMAILQUEUE=/var/qmail/
bin/simscan,,NOP0FCHECK=1
I'm missing
[EMAIL PROTECTED] wrote:
Are most folks using or not using DK? It seems to be an endless pain in the
butt. Yet again today, more domains not being allowed to send out because
they
can't sign DK.
I don't get the behavior, some domains work, some don't. I'd love to just
stop
trying to
Are most folks using or not using DK? It seems to be an endless pain in the
butt. Yet again today, more domains not being allowed to send out because they
can't sign DK.
I don't get the behavior, some domains work, some don't. I'd love to just stop
trying to fuss with DK but I badly need email to
checking incoming sometimes rejects when it shouldn't). DK will eventually
be replaced with DKIM. Check the list archive for the proper way to entirely
disable it.
Disabling it is what caused me a lot of grief when I first installed. The wiki
suggested method ends up breaking things you can't
[EMAIL PROTECTED] wrote:
127.:allow,RELAYCLIENT=,RBLSMTPD=,NOP0FCHECK=1
192.168.1.:allow,RELAYCLIENT=,RBLSMTPD=,NOP0FCHECK=1
xx.xx.xx.:allow,RELAYCLIENT=,RBLSMTPD=,NOP0FCHECK=1
:allow,BADMIMETYPE=,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER
_WRONGRCPTLIMIT=10,QMAILQUEUE=/var/qmail/
