Alexey Loukianov wrote:
> Eric "Shubes" wrote:
>>> Currently, the "right way" to disable DK without unlinking/relinking qq
>>> handlers is to remove DKVERIFY and DKSIGN completely from tcp.smtp.
>> Beware (from qmail-dk man page):
>> If neither DKSIGN nor DKVERIFY are set, then DKSIGN will be set to
>> /var/qmail/control/domainkeys/%/default. If such a private key exists, it
>> will be used to sign the domain.
>
> Sure, if you've got private key for domain laying in
> /var/qmail/control/domainkeys/<domain name>/default, and you've got
> RELAYCLIENT set, qmail-dk will sign a message. This behavior will change
> in the next release of qmail-dk (as I don't like it), and in any case is
> very unlikely case to happen for Qmail Toaster.
>
> My initial thoughts were to add DKDISABLE environment variable for
> disabling of DK, but later on I came to a decision that the Right Way
> (TM) will be simply to do nothing if none of DKSIGN and DKVERIFY are set.
>
Makes Sense To Me (TM). ;)
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
