Now my test conf file: amavis_test.conf, has:
dkim_key('domain1.com', "dkim", "/var/lib/dkim/domain1.com.pem");
dkim_key('others.com', "dkim", "/var/lib/dkim/others.com.pem");
@dkim_signature_options_bysender_maps = ( {
".domain1.com" => { d => "domain1.com" },
"." => { d => "others.com" },
});
And DKIM etc records for 'newdomain.com' are all published in DNS.
However, the following commands still fail:
amavisd -c amavis_test.conf showkeys .org newdomain.com
amavisd -c amavis_test.conf testkeys .org newdomain.com
the outcome of the above commands are something like no matching
private key found.
Is it due to what you wrote as below, both these commands only care
what dkim key for that explicit domain is defined?
Is there *any* way I can make certain the amavis conf will work with
newdomain.com , *before" actually installing the amavis conf file?
Thank you!
On Wed, Mar 27, 2019 at 6:54 AM Marc Pujol <[email protected]> wrote:
>
> Then showkeys just shows you these definitions, and testkeys checks that
> the DNS records are actually published and correspond to the public
> counterpart of the specified private key file.
>
> This is completely independent from the logic of deciding which signing
> domain (d=xxxx.tld) sould be used for each particular e-mail (of course
> you can only sign with one of the signatures you have previously
> defined, but which one to use specifically is where
> dkim_signature_options_bysender_maps comes in).
>
