Thanks for all this super-useful info! With some help from the folks at fastmail and the folks at the forwarding domain, we were able to sort this out!
This was all beyond my technical expertse, but my understanding is that the forwarding domain had set up something that broke dmarc for *some* domains (including lastpass, the example used below_. They wrote:
Quote:
|
We recently implemented something called postsrsd with postforward to solve an SPF problem with mail forwarding; however, with certain hosts this has seemingly broke DMARC validation... ). We used lastpass as a test and were able to recreate the issue. Reverting gregtest@XXX.net back to the old forwarding system fixed the DMARC validation, but now SPF fails (with lastpass) - despite SPF failing mail is still delivered and not completely rejected, which is a little better. I reverted your account to the old method now.
|