Hey Carl, I think this refers to emails originating within the Salesforce Marketing Cloud (ExactTarget) platform, but the SPF missing IP and DKIM failure touch on something that I think is happening to the mail after it leaves our system. I've spun up a support case to reach out to the client and ask them if they'd like us to update the SPF record as indicated and suggesting that they review the potential DKIM configuration issue.
If a Comcast person sees this and wants to coordinate, feel free to reach out to me. Thanks for the heads up. Cheers, Al Iverson On Mon, Jun 25, 2018 at 12:12 PM Carl Byington <c...@five-ten-sg.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > bounce.care.comcast.com has > > "v=spf1 include:cust-spf.exacttarget.com ip4:76.96.68.101 > ip4:76.96.68.102 ip4:76.96.68.103 ip4:69.252.76.7 ip4:69.252.76.8 > ip4:69.252.76.9 -all" > > Note the -all, but at least some mail is arriving here via resqmta-po- > 04v.sys.comcast.net == 96.114.154.163 not listed in the above spf > record. You might want to fix that. > > Also, the DKIM signature from mdp.comcast.net is broken - > reason="signature verification failed". > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iEYEAREKAAYFAlsxE2YACgkQL6j7milTFsHZlQCfQ7i8CCsnP+Jy5R1lrFjw7A// > VyQAn3yFmOu5o/0HTCDnMUWHyH78DS48 > =XKZW > -----END PGP SIGNATURE----- > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- al iverson // 312-725-0130 // miami http://www.aliverson.com http://www.spamresource.com _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
