Hi, It's definitely a problem with the current spamassassin from github v4. I went back to an old version I built on May 29th and it immediately starts reporting DKIM normally again.
I just built the latest version and it's still exhibiting the same problem. Based on my logs, it started happening on or around June 14th. DMARC is not working with my version from May 29th. I wonder if I could drop in the DMARC.pm that was updated at the end of June into the May 29th version and see if now they both work? btw, I previously mentioned github, but meant svn.apache.org. svn checkout http://svn.apache.org/repos/asf/spamassassin/trunk Mail-SpamAssassin-4.0.0 On Sat, Jun 25, 2022 at 3:07 PM Alex <mysqlstud...@gmail.com> wrote: > Hi, > I've been having problems with DMARC failing over the past few weeks using > the latest SA, even on sites I know have passed. It appears to have > coincided with an update to DMARC.pm related to timing. I just now happened > to notice that maybe the problem is with DKIM, or there's a separate DKIM > problem or something I simply don't understand. Installing v3.4.6 over the > latest v4 fixes the problem instantly. > > It appears DKIM is loading in amavis: > Jun 25 00:13:09 mail03 amavis[4119158]: Module Mail::DKIM::Signer > 1.20200907 > Jun 25 00:13:09 mail03 amavis[4119158]: Module Mail::DKIM::Verifier > 1.20200907 > Jun 25 00:13:09 mail03 amavis[4119158]: DKIM code loaded > Jun 25 00:13:18 mail03 amavis[4119158]: SpamAssassin loaded plugins: ASN, > AskDNS, AutoLearnThreshold, BTCBL, Bayes, BodyEval, Check, ClamAV, DCC, > DKIM, DMARC, DNSEval, DecodeShortURLs, FreeMail, FromNameSpoof, HTMLEval, > HTTPSMismatch, HashBL, HeaderEval, ImageInfo, Levenshtein, MIMEEval, > MIMEHeader, OLEVBMacro, PDFInfo, PhishTag, Phishing, Pyzor, Razor2, > RecipientMsgID, RelayCountry, RelayEval, ReplaceTags, SPF, SendGrid, > Shortcircuit, SpamCop, TextCat, TxRep, URIDNSBL, URIDetail, URIEval, > URILocalBL, VBounce, WLBLEval, WelcomeListSubject, iXhash2 > > Yet it never fires. The only references to DKIM in emails are > from DKIM_ADSP_ALL. What could I be missing, or is this possibly a bug? > > You might also recall from my previous reports that DKIM succeeds on an > email where it otherwise failed when running it through SA directly. > > $ spamassassin --version > SpamAssassin version 4.0.0-r1901426 > running on Perl version 5.34.1 > > This is on fedora35. Installing the stock 3.4.6 immediately starts > triggering DKIM hits. > > Is there a backport of RaciallyCharged, Esp and ExtractText (although I > don't really use that anymore) that's available for v3.4.6, so my > welcomelist entries work in the meantime? > > >