60278-2106261320579920738 | Failed DMARC - brit.org does not include: _custspf.clickandpledge.cc in SPF record |
60278-2106261200307415819 | "Message not accepted for policy reasons. See https://postmaster.verizonmedia.com/error-codes" |
60278-2106221249266638928 | no record - possibly too long since it was attempted |
60278-2106280954421820643 | Failed DMARC - brit.org does not include: _custspf.clickandpledge.cc in SPF record |
60278-2106221212129341079 | no record - possibly too long since it was attempted |
If you provide the Best Practices to Ensure Email Receipt Delivery article to whomever manages your email server, they can add an "SPF" record to your mail server that authorizes C&P to send email on your behalf. That will correct the DMARC failures.
The others may be resolved by the change you made to the email address. Using the same email for "Reply To: " that you do for the "From: " is not as likely to cause an issue - that would be the default behavior you would expect anyway. It's more of a spam flag if the "From: " address is the same as the Internal Notifications - since this can function as a "CC: ", essentially sending from and to the same email.
But getting the SPF record set up correctly is the most important step to smooth things out.
Leave a comment: