Dkim - no signing domain match


I am very pleased to have spun up my first freepbx server with the help of crosstalk solutions youtube and this forum. I am using office365 for email and the guide here was very helpful to get email going: How+to+setup+FreePBX+to+work+with+Office+365+Exchange+Email

I am running FreePBX CENTOS and freepbx is up to date

Working through this DKIM wiki How-to+Enable+SPF+DKIM+DMARC+on+FreePBX I have hit a roadblock. messages are not being signed with the error: no signing domain match for ‘mydomain_com’

mypbx postfix/cleanup[4378]: 7EF5B61A9DFF: message-id=<[email protected]_com>
mypbx opendkim[4105]: 7EF5B61A9DFF: no signing domain match for ‘mydomain_com’
mypbx opendkim[4105]: 7EF5B61A9DFF: no signing subdomain match for ‘mydomain_com’
mypbx opendkim[4105]: 7EF5B61A9DFF: no signature data
mypbx postfix/qmgr[4201]: 7EF5B61A9DFF: from=<[email protected]_com>, size=545, nrcpt=1 (queue active)

[[email protected] keys]# cat /etc/opendkim.conf
PidFile /var/run/opendkim/
Mode sv
UserID opendkim:opendkim
Socket inet:[email protected]
Umask 002
SoftwareHeader yes
Canonicalization relaxed/simple
Domain mydomain_com
Selector freepbx
MinimumKeyBits 1024
KeyFile /etc/opendkim/keys/freepbx.private
#KeyTable /etc/opendkim/KeyTable
#SigningTable refile:/etc/opendkim/SigningTable
#ExternalIgnoreList refile:/etc/opendkim/TrustedHosts
#InternalHosts refile:/etc/opendkim/TrustedHosts
OversignHeaders From

[[email protected] keys]# cat /etc/postfix/generic
[email protected] [email protected]_com
[email protected]_com [email protected]_com
[email protected]_com [email protected]_com
@mypbx.mydomain_com @mydomain_com

I see the message id is *@mypbx.mydomain_com and the from field is [email protected]_com. my preference is to have the messages sending as [email protected]_com which matches the mailbox and presumably sign the messages, but I have not been able to accomplish this.

Any guidance is appreciated. thank you for taking a look.

[had to butcher this since new users are not allowed to post links]strong text

I was able to finally resolve this by configuring the SigningTable and enabling in the opendkim.conf.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.