Menu

#22 KeyTable not working

2.8.2
closed
nobody
None
5
2014-03-14
2014-03-14
Mike Daoust
No

Ive been working at having multiple signatures and have pretty much ran into a wall. The SigningTable seems fine however the KeyTable returns: dkimf_db_get(): record not found when doing

opendkim -Q
refile:/etc/opendkim/KeyTable
technicallyoverated.com\3

KeyTable is as follows No extra spaces or lines are present

default._domainkey.technicallyoverated.com technicallyoverated.com:default:/etc/opendkim/keys/technicallyoverated.com/default.private

SigningTable

*@technicallyoverated.com default._domainkey.technicallyoverated.com

opendkim.conf

LogWhy Yes
Syslog yes
SyslogSuccess yes
Socket inet:8891@localhost
ReportAddress postmaster@appriver.com
SendReports yes
UserID opendkim:opendkim
PidFile var/run/opendkim/opendkim.pid

Mode s
Canonicalization relaxed/relaxed
Statistics /var/lib/opendkim/stats.dat

InternalHosts /etc/opendkim/TrustedHosts
ExternalIgnoreList /etc/opendkim/TrustedHosts

SigningTable refile:/etc/opendkim/SigningTable
KeyTable refile:/etc/opendkim/KeyTable

Discussion

  • Murray S. Kucherawy

    • status: open --> pending
     
  • Murray S. Kucherawy

    You're asking the KeyTable to return an entry for "technicallyoverrated.com\3", which is not in that table. The output looks right to me.

    Querying the SigningTable for "user@technicallyoverrated.com/1" should hit, returning "default._domainkey.technicallyoverated.com".

    Querying the KeyTable for "default._domainkey.technicallyoverated.com/3" should hit, returning the three obvious values from the KeyTable file.

     
  • Mike Daoust

    Mike Daoust - 2014-03-14

    Ah I see. Misunderstanding on how this should work on my part.
    This is my first go at setting up for multi domain signing.

    Thanks!

     
  • Murray S. Kucherawy

    • status: pending --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB