Based on the headers of the message you sent here (to mailop), you have yet to actually publish a public key in DNS.
https://tools.wordtothewise.com/dkim/check/warwickri/1677852725 laura > On 3 Mar 2023, at 14:12, Salvatore Jr Walter P via mailop <mailop@mailop.org> > wrote: > > We are in the final stages of migrating our exchange server from 2013 to 2019. > I found out we had no SPF, DMARC, DKIM etc setup on our domains. > > Trying to get us setup properly and have SPF and DMARC working, DKIM is > another story. > Setup on the server, sent the key to our ISP for the DNS to be added. > Headers show the signature is being included. > > DKIM-Signature: v=1; a=rsa-sha256; d=redacted.gov <http://redacted.gov/>; > s=1; c=relaxed/relaxed; > t=1677851456; h=from:subject:to:date:message-id;(rest of key) > > > Also from the headers: > > Authentication-Results: inbound.redacted.net <http://inbound.redacted.net/>; > spf=pass smtp.mailfrom=redacted@ redacted.gov <http://redacted.gov/>; > dkim=fail header.d= redacted.gov <http://redacted.gov/>; > dmarc=pass (policy=none; pct=100; status=pass); > arc=none > > Any suggestion where to go from here? We are having all emails blocked by > AT&T, no idea why so trying to get all our ducks in a row and make sure we > are doing everything the “right” way. > _______________________________________________ > mailop mailing list > mailop@mailop.org <mailto:mailop@mailop.org> > https://list.mailop.org/listinfo/mailop -- The Delivery Experts Laura Atkins Word to the Wise la...@wordtothewise.com Email Delivery Blog: http://wordtothewise.com/blog
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
