DMARC support in Wild Apricot emails
SPF alignment requires the Return-Path: to match our custom domain. Alas, WA forces it to firstname.lastname@example.org, causing 100% SPF failure. Amazon SES solves this with "Mail From Domain" settings, which require us setting the proper DNS records to have a subdomain MX to SES and they get their bounces this way and we get SPF management.
At present we're having a lot of SPAM/silent deletions of our emails due to SPF misalignment (We are 100% DKIM aligned), and this would help that issue.
Roger Brooks commented
We too have a lot of mail to members marked as spam, delivered to spam folders or even just deleted despite correct DKIM and SPF implementation.
This will only get more and more important as people (and organizations) get more security-conscious!
P.S. Since Syd Weinstein talks about an address at wildapricot.org, I presume he doesn't have his own domain. We do, but the lack of DMARC support is still a problem, as is the lack of flexibility in DKIM and SPF!
This will be addressed when we implement DMARC support for Wild Apricot emails. This is on our radars now, but no exact plans.
I'll post updates about it as we have any