You actually got me on right track. Peeled back the onion abit to how OpenDkim was being started
I looked in more depth at start up script used by rc.cof. It was looking for a opendkim.conf in /usr/local/etc/mail not /usr/local/etc/opemdkim Copied opedkim.conf back that and all is good There is a mystery how opendkim started with out its conf file but ai issue it used defaults and thus the fault Thanks to all and sorry for polluting the mailing list Jason > On Oct 25, 2019, at 4:12 PM, Fazzina, Angelo <angelo.fazz...@uconn.edu> wrote: > > Hi again, > Maybe this will help you trouble shoot where the misconfiguration is ? > > Hi, here's my signing table > [root@mta5 opendkim]# more SigningTable |grep -v "#" > > > *@appmail.uconn.edu dkim1._domainkey.mta5.uits.uconn.edu > <http://domainkey.mta5.uits.uconn.edu/> > *@uconn.edu dkim1._domainkey.mta5.uits.uconn.edu > <http://domainkey.mta5.uits.uconn.edu/> > *@uits.uconn.edu dkim1._domainkey.mta5.uits.uconn.edu > <http://domainkey.mta5.uits.uconn.edu/> > *@mta5.uits.uconn.edu dkim1._domainkey.mta5.uits.uconn.edu > <http://domainkey.mta5.uits.uconn.edu/> > *@localhost dkim1._domainkey.mta5.uits.uconn.edu > <http://domainkey.mta5.uits.uconn.edu/> > >
