Hey @Sami O'Shaughnessy! I'll second what @Mark Hany said. SPF, DKIM, and DMARC work together to authenticate your emails and instruct inbox providers on what to do with unauthenticated sources of mail. So, even if your SPF record has been fixed, a faulty DKIM or DMARC record could also produce the spam placement issues you mentioned in your original post. It sounds like you're specially seeing problems with Yahoo, AOL, and Microsoft based inboxes. If your organization hasn't done this yet, I'd recommend setting up the Yahoo Sender Hub. This can give you specific insights into any Yahoo related deliverability issues. Microsoft has a similar tool called Microsoft SNDS but it only works if your organization uses a dedicated IP. AOL doesn't really have an equivalent tool. And they are a notoriously difficult inbox provider to work with from a sender perspective. However, Google has a great deliverability suite called Google Postmaster Tools. It's sort of like a very stripped down version of Google Analytics for email marketers. Even if you aren't noticing problems with Google inboxes, I'd suggest setting it up and monitoring it anyways. Another good diagnostic tool you can use to quickly find technical issues that might cause deliverability problems is called About My Email. They give you a test address, you send an email to it, and it breaks down your compliance with all of the important technical sender guidelines. Technical deliverability problems are the easiest to find and fix. But like Mark said above, your sender reputation plays a much bigger role when it comes to inbox / spam placement. If you're still experiencing problems after you audit and fix your technical configuration, feel free to send me a message here. Let me know if you have any other questions or concerns about this. Deliverability is a pretty opaque topic. And I'm always happy to help someone in @Kate Guillen's community! 🙌🏼