Sorry I'm seeing this late, SPF doesn't align here because the notifications are sent from bounces.google.com. this means a dkim DNS failure will cause this issue.
I'm not sure if it's correct to use the bounces.google.com address, so I'll file a bug to look into that. Also, we could add more info to the SMTP error message, I'll have to see how feasible that is. On Dec 7, 2016 6:24 AM, "Denis Salicetti via dmarc-discuss" < [email protected]> wrote: > Hi Guys, > the problem with the 2048-bit DKIM key has been resolved. Now I can see it > valid and Google calendar notifications have been resolved as well. > > Thank you very much. > > *Denis Salicetti* <http://linkedin.salicetti.it/> > > Avviso di riservatezza <http://goo.gl/zS2xL> | Inviami messaggi protetti > <http://goo.gl/LbhIoi> > > 2016-12-06 22:01 GMT+01:00 Sim via dmarc-discuss <[email protected]> > : > >> Hi Denis, >> >> Am 06.12.2016 um 20:58 schrieb Denis Salicetti via dmarc-discuss: >> > >> > I tried to verify if all the DNS records of my domain (SPF, DKIM and >> > DMARC) were good and I found out that the 2048-bit DKIM key was no >> > longer valid. This is strange because it was good so far, so I decided >> > to contact my DNS provider. >> That's odd. [Protodave's >> keychecker](https://protodave.com/tools/dkim-key-checker/?se >> lector=google&domain=galeati.it) >> is still showing the string 'CEji' while I cannot find it in here. >> >> $ dig +short google._domainkey.galeati.it txt @ns1.acantho.net|grep CEji >> $ dig +short google._domainkey.galeati.it txt @ns3.acantho.net|grep CEji >> >> It is a valid pubkey without the 'i': >> -----BEGIN PUBLIC KEY----- >> MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkx5rG60SwrFaFctJVHSF >> JRxylWDdjj3KMo8uDLoVn1CEjB5FbeJKE1I0huUA3m5GLaTyXEr8d61G9kTiQUpr >> uCCyKm83dIPv1gerCNivnBs0keWTBt8oaQzXEkxfFN9IFvS1/okcSOz5GwqKHsFZ >> BKSQE+VPpXcMwsgY5ECKlByKjE9LEi2jxud1R5p8GFCUHHYICGOvNwOk0K0eCC7v >> K6rNWxuP86nuYWSYaKTJIfZgCp7FanUg3DuyTSOiN9vwfUceexEk3H2Zn242/pi2 >> HYozvTLY7Gw2MtQ7YVNvmfivbc1p2hwrbLnZkW3mKvBDofo08K76US66c2qyVn4z >> cQIDAQAB >> -----END PUBLIC KEY----- >> >> I guess caching is playing tricks and you fixed it already? >> >> Simon >> _______________________________________________ >> dmarc-discuss mailing list >> [email protected] >> http://www.dmarc.org/mailman/listinfo/dmarc-discuss >> >> NOTE: Participating in this list means you agree to the DMARC Note Well >> terms (http://www.dmarc.org/note_well.html) >> > > > _______________________________________________ > dmarc-discuss mailing list > [email protected] > http://www.dmarc.org/mailman/listinfo/dmarc-discuss > > NOTE: Participating in this list means you agree to the DMARC Note Well > terms (http://www.dmarc.org/note_well.html) >
_______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
