Re: no signing domain match

From: Дилян Палаузов <dilyan.palauzov_at_aegee.org>
Date: Fri, 05 Jul 2019 09:41:24 +0000

Hello W,

you likely told opendkim to sign mails for domain server1.mycompany.net, but have not configured opendkim where to find
the private signature key for that domain.

Note, that the four-years-ago ago released version 2.10.3 of opendkim has known bugs, which are fixed at
server1.mycompany.net .

Regards
  Дилян

On Fri, 2019-07-05 at 03:00 +0000, W wrote:
> Hi,
>
> I am trying to use opendkim for postfix on ubuntu 18.04 get errors blow.
> The error ' no signing domain match for' is for a full qualified domain name, not plain domain name. It that correct?
>
> How to debug?
> Any information would be appreciated. Thanks in advance.
>
> >>>>>>>>>>>>>>>>>>>>
> Jul 5 02:49:33 server1 postfix/pickup[19370]: 3BD5AE0DFE: uid=1000 from=<choreer_at_server1.mycompany.net>
> Jul 5 02:49:33 server1 postfix/cleanup[19393]: 3BD5AE0DFE: message-id=<20190705024933.3BD5AE0DFE_at_mycompany.net>
> Jul 5 02:49:33 server1 opendkim[19380]: 3BD5AE0DFE: no signing domain match for 'server1.mycompany.net'
> Jul 5 02:49:33 server1 opendkim[19380]: 3BD5AE0DFE: no signing subdomain match for 'server1.mycompany.net'
> Jul 5 02:49:33 server1 opendkim[19380]: 3BD5AE0DFE: no signature data
>
Received on Fri Jul 05 2019 - 09:41:43 PST