How to Set Up SPF Records for Office 365

Office 365 SPF record setup for email security.

For many businesses, Office 365 is the backbone of their email communication. But to ensure those emails consistently reach their destination and to protect your brand from impersonation, you need to look at email authentication, starting with SPF records for Office 365. An SPF record is essentially your domain's way of telling the world, "These are the only servers allowed to send email for me." This simple but powerful DNS entry plays a huge role in preventing email spoofing, which can damage your reputation, and in improving your overall email deliverability. If you want your important messages to avoid the spam folder and maintain trust with your recipients, understanding and correctly implementing SPF is a non-negotiable first step.

Key Takeaways

Set up your Office 365 SPF record correctly in your DNS: This tells other email servers your messages are legitimate, helping them land in inboxes and protecting your domain from spoofing.
Keep your SPF record accurate through regular checks: Make sure all your sending services are included, you're within the 10-lookup limit, and there are no typos, so your emails keep getting delivered reliably.
Strengthen your email defenses by adding DKIM and DMARC: These work with SPF to provide much stronger protection against email fraud, giving you more control over how your domain is used.

What Are SPF Records and Why Do They Matter for Office 365?

If you're using Office 365 for your business emails, you're likely sending out a good number of messages – from client communications to marketing outreach. But have you ever worried if those important emails are actually landing in inboxes, or worse, if someone could be misusing your domain to send fake emails? This is where SPF records come into play, and they're a pretty big deal for keeping your email game strong and secure. Think of an SPF record as a digital bouncer for your email domain; it stands at the virtual door, checking IDs to make sure only legitimate senders get through using your domain's name. It helps receiving mail servers verify that emails appearing to come from you are actually from you, and not from a spoofer trying to impersonate your brand.

For Office 365 users, getting your SPF record right is a key step in protecting your domain's reputation, improving your email deliverability, and ensuring your legitimate messages don't get flagged as spam. Without a properly configured SPF record, your emails are more likely to be treated with suspicion, potentially ending up in spam folders or being rejected outright. This can significantly impact your communication effectiveness and even damage your sender reputation over time, making it harder for your genuine messages to reach your audience. It’s a fundamental piece of the email authentication puzzle that you really don’t want to overlook, especially when you rely on email for critical business operations and want to ensure efficient delivery for your high-volume campaigns.

What is SPF in Email Authentication?

So, what exactly is this SPF thing? SPF stands for Sender Policy Framework. At its core, it's an email authentication method designed to stop spammers from sending messages that look like they're coming from your domain – a sneaky tactic known as spoofing. How does it work its magic? Well, as a domain owner, you get to specify exactly which mail servers are authorized to send emails on behalf of your domain. You do this by publishing a special type of DNS record, called a TXT record. This record is like a public list that other mail servers can check. It’s a straightforward way to identify valid email sources for your domain, making it harder for unauthorized parties to misuse your good name.

How SPF Stops Email Spoofing

SPF is a real hero when it comes to preventing email spoofing, a common trick used in phishing attacks to deceive recipients. By clearly stating which servers are allowed to send emails for your domain, SPF helps receiving email systems validate the source of incoming messages. When an email arrives, the recipient's mail server checks your domain's SPF record. If the email came from a server that isn't on your approved list, it’s a red flag! That email might then be marked as spam or even rejected completely, never reaching the intended inbox. While SPF is a fantastic start, it’s even more powerful when teamed up with other authentication methods like DKIM and DMARC. Together, they provide a much more robust defense against email fraud.

How to Set Up SPF Records for Office 365: Your Step-by-Step Guide

Alright, let's talk about something super important for making sure your emails actually get where they need to go: Sender Policy Framework, or SPF records. If you're using Office 365 for your business emails, getting your SPF record set up correctly is a non-negotiable step for solid email deliverability. Think of it like this: an SPF record is your domain's official declaration, telling the world which mail servers are authorized to send emails on your behalf. Why does this matter so much? Well, it's a key player in preventing email spoofing – that nasty trick where someone fakes your email address to send spam or phishing emails. When your SPF record is in place and accurate, receiving email servers can check if an incoming email claiming to be from you is legitimate. This significantly improves your sender reputation and reduces the chances of your important messages ending up in the dreaded spam folder.

For businesses relying on email for outreach, customer communication, or running high-volume campaigns – which I know many of you using services like ScaledMail are – a properly configured SPF record is foundational. It’s one of the first things you should tackle to ensure your communication efforts are effective. It might sound a bit technical, but I'm here to walk you through it step by step. Getting this right means more of your emails land in the inbox, protecting your brand's credibility and making sure your messages are seen. So, grab a cup of coffee, and let's get your Office 365 SPF record set up!

Access Your DNS Settings

First things first, you'll need to get into your Domain Name System (DNS) settings. It's a common point of confusion, but you actually manage SPF records through your domain registrar, not directly within your Microsoft 365 admin center. Your domain registrar is the company where you purchased your domain name – popular ones include GoDaddy, Namecheap, or Google Domains.

Log in to your account with your domain registrar. Once you're in, look for a section typically labeled "DNS Management," "Manage DNS," "Advanced DNS Settings," or something similar. This is the control panel where you can add or edit various DNS records, including the TXT record needed for SPF. While the exact layout and naming can vary a bit from one registrar to another, the core function is the same. If you have trouble locating it, a quick search in your registrar’s help section should guide you.

Create and Configure Your SPF Record

Now that you've found your DNS settings, it's time to either create a new SPF record or, if one already exists, modify it. SPF information is published as a TXT record within your domain's DNS zone. If you're using a custom domain with Office 365 (like yourcompany.com), you'll definitely need to create or update this TXT record to include Microsoft's mail servers.

The standard syntax for an SPF record is v=spf1 <valid mail sources> <enforcement rule>. For Office 365, the essential part you need to include is include:spf.protection.outlook.com. So, a basic SPF record for Office 365 would look like this: v=spf1 include:spf.protection.outlook.com -all. The v=spf1 part identifies it as an SPF record. The include:spf.protection.outlook.com tells receiving servers to check Microsoft's SPF record for their authorized sending IPs. The -all at the end is an enforcement rule, which we'll discuss more next. If you use other third-party services to send email (like marketing platforms or CRMs), you'll need to add their specific SPF mechanisms to this single record.

Verify Your SPF Configuration

After you've added or updated your SPF record in your DNS settings, it's really important to verify that it's configured correctly. A small typo can lead to big delivery problems! As mentioned, the -all (which signifies a "hard fail") is generally the recommended enforcement rule, especially when you're also implementing DKIM and DMARC for a more robust email authentication setup. This tells receiving mail servers to reject messages that fail the SPF check.

A critical rule to remember is that a domain (or subdomain) must only have one SPF record. If you accidentally create multiple SPF TXT records, it can cause validation errors and render your SPF setup ineffective. Also, pay attention to the TTL (Time To Live) value for your record; a common recommendation is 3600 seconds (which is 1 hour). This tells DNS servers how long to cache your SPF information before checking for an update. Once you save your changes, allow some time for DNS propagation, which can take anywhere from a few minutes to 48 hours, though it's often much faster. You can use various online SPF record checker tools to confirm your record is visible and correctly formatted.

Solve Common Office 365 SPF Record Challenges

Setting up SPF records is a fantastic step towards better email security for your Office 365 accounts, but let's be real, sometimes you might hit a few snags. Don't worry, though! These are usually common issues with straightforward fixes. Think of it like baking your favorite cake – sometimes you might accidentally add too much flour or forget the vanilla extract, but with a little adjustment, you can still end up with something delicious. Similarly, when you're working to ensure your important emails reach the inbox and not the spam folder, getting your SPF record configured correctly for Office 365 is a key ingredient. This little text record is powerful; it tells receiving email servers that your messages are genuinely from you, which is absolutely crucial for building trust with recipients and maintaining a strong sender reputation, especially when you're conducting high-volume outreach.

However, things like accidentally creating multiple records, those sneaky little syntax mistakes, or even the sheer number of third-party services you use to send email can throw a wrench in the works, leading to frustrating delivery problems. We're going to walk through some of the typical hurdles you might encounter with Office 365 SPF records and, more importantly, how to clear them. With a little know-how and these actionable steps, you'll have your SPF record working perfectly. This means your legitimate emails get the green light, your domain's reputation stays solid, and your outreach campaigns can achieve their full potential. Let's get these challenges sorted!

Handle Multiple SPF Records

One of the golden rules of SPF is that your domain, or even a subdomain you use for sending, should only have one SPF record. It might seem logical to add separate records for different email services, but this actually confuses the email servers trying to verify your messages. When a receiving server checks your domain and finds multiple SPF TXT records, it can lead to validation failures. This means your carefully crafted emails might get flagged as spam or not delivered at all – a real setback for any outreach effort.

The solution is to consolidate. If you use various services to send emails, like Office 365 plus a marketing platform, you need to combine all their required SPF mechanisms into a single TXT record in your DNS settings. Microsoft Learn offers clear guidance on how to set up SPF to identify valid email sources for your Microsoft 365 domain, highlighting this single-record rule.

Fix Syntax Errors

Think of your SPF record as a tiny, but very precise, piece of code. Like any code, a small typo or incorrect formatting can prevent it from working correctly. Syntax errors are a common reason why SPF validation might fail, stopping your emails from being properly authenticated. This could be a missing space, an incorrect character, or using the wrong mechanism (like ip: instead of ip4:).

When an email server can't properly read your SPF record due to these errors, it can't validate your emails, potentially leading to rejections or spam placement. The best way to avoid this is to be meticulous. Double-check your SPF record for any typos or formatting mistakes before you publish it to your DNS. AutoSPF offers a useful guide to fix SPF validation errors that can point out common mistakes.

Manage DNS Lookup Limits

Here’s a slightly more technical, but crucial, detail: your SPF record has a hard limit of 10 DNS lookups. Certain SPF mechanisms like include:, a:, mx:, and redirect= require the receiving email server to perform a DNS query to determine authorized IP addresses. Each query counts as one lookup. If your SPF record triggers too many of these, it will exceed the 10-lookup limit, causing SPF validation to fail even with perfect syntax.

This is common for businesses using multiple third-party email services, as each include: adds lookups. To stay within this limit, you need to be strategic. You might need to simplify your SPF record by, for example, using direct IP address mechanisms (ip4: or ip6:) when possible, as these don’t count towards the lookup limit.

Integrate Third-Party Services Correctly

Many businesses rely on various third-party services to send emails – think of your marketing automation platforms, customer support tools, or even billing systems. If these services are sending emails using your domain name (e.g., from support@yourcompany.com), they absolutely must be authorized in your SPF record. If they aren't, emails sent from these platforms on your behalf are highly likely to be flagged as suspicious or rejected by receiving mail servers because they won't pass SPF authentication.

This can seriously undermine your communication efforts. To integrate them correctly, you'll need to find out what SPF information each third-party service requires. Usually, they provide an include: mechanism (like include:servicename.com) or specific IP addresses. You then carefully add their IP address or server details into your single, consolidated SPF record for your domain.

Optimize Your SPF Record for Better Email Delivery

When you're serious about your email outreach, especially if you're sending messages at scale, making sure those emails actually land in the inbox is priority number one. That's where optimizing your Sender Policy Framework (SPF) record comes into play. Think of your SPF record as a digital bouncer for your email domain; it meticulously checks who's allowed to send emails using your domain name. By fine-tuning this record, you're essentially telling receiving mail servers, "Yes, this email is legitimately from us, and you can trust it." This simple step can dramatically improve your email deliverability rates, ensuring your carefully crafted messages don't get mistakenly flagged as spam.

Beyond just getting your emails delivered, a well-optimized SPF record is crucial for protecting your brand's reputation. Email spoofing, where attackers send malicious emails pretending to be from your domain, can severely damage your credibility and trust with your audience. A strong SPF setup acts as a frontline defense against such activities. It helps receiving servers verify the authenticity of emails, making it much harder for fraudsters to impersonate you. For businesses that rely on email for customer communication, marketing campaigns, or sales outreach, maintaining a pristine sender reputation is non-negotiable. Optimizing your SPF record is a foundational element in building and preserving that trust, ensuring your domain remains a reliable source of communication. We'll walk through exactly how to get your SPF record in top shape.

Include All Authorized Senders

First things first, let's make sure your SPF record knows about everyone who's legitimately sending emails for you. This means listing all the IP addresses and any third-party services—like your email marketing platform, CRM, or even helpdesk software—that dispatch emails using your domain. Your SPF record is a TXT record in your DNS settings, and it acts like an approved sender list. When you accurately identify all valid email sources and list them here, you make it much harder for anyone to spoof your domain. This is a key step in keeping your sender reputation clean and ensuring your important messages reach their destination.

Choose the Right SPF Mechanisms

Next up is using the correct 'language' or mechanisms in your SPF record to define these approved senders. The basic format usually starts with v=spf1, followed by the mechanisms that list your sources, and an enforcement rule at the end. For example, you'll use ip4: or ip6: for specific IP addresses and the include: mechanism for third-party services (this tells receiving servers to check that service's SPF record too). Getting these mechanisms right is vital because it helps email servers correctly interpret your policy. You can learn the specifics of SPF syntax to ensure you're clearly defining who can send on your behalf, which helps prevent your genuine emails from being incorrectly filtered as spam.

Implement a Hard Fail Policy

For an extra layer of security, think about using a 'hard fail' policy. This is done by adding -all at the end of your SPF record. Essentially, this tells receiving mail servers, "If an email claims to be from my domain but isn't from one of the sources I've explicitly listed, reject it outright." It's a firm stance, but it's incredibly effective at shutting down email spoofing and phishing attempts. When you combine this strong SPF policy with DKIM and DMARC, you create a powerful trio that significantly protects your domain's integrity and helps ensure your legitimate emails are trusted and delivered.

Must-Have Tools and Resources for SPF Record Management

Alright, so you've put in the effort to understand and set up your SPF records for Office 365. That’s a fantastic step! But here’s a little secret from someone who’s seen it all: SPF management isn't a "set it and forget it" kind of deal. Think of it more like tending to a garden; it needs regular attention to flourish. To keep your email deliverability high and your domain secure, you'll want to have a few key tools and resources in your back pocket. These aren't just nice-to-haves; they're pretty essential for making sure everything runs smoothly and for catching any little hiccups before they turn into big headaches.

The good news is, you don’t need to be a DNS wizard to stay on top of things. There are some incredibly helpful online tools that can simplify the testing and validation process. Plus, official documentation, especially from Microsoft, can be a goldmine of accurate information. Knowing how to use these resources effectively will empower you to manage your SPF records with confidence. It’s all about having the right information and the right tools at your fingertips so you can act decisively, whether you're doing a routine check-up or troubleshooting an unexpected issue. Let's look at some of my go-to resources that can make your life a whole lot easier.

Tools to Test and Validate Your SPF Record

Once your SPF record is live, or if you're trying to figure out an issue with an existing one, you absolutely need to check its validity. This is where SPF record checker tools are invaluable. These online utilities let you examine your SPF record just as a recipient's mail server would. Using a checker regularly helps you catch syntax errors, confirm all your legitimate sending sources are listed, and ensure you haven’t accidentally gone over the DNS lookup limit—a common pitfall! If a tool flags an error, it's wise to address it quickly. And remember, if you're not entirely comfortable making DNS changes yourself, there's no shame in asking your IT team or a seasoned professional for a hand.

Use Microsoft's Official SPF Configuration Guide

When you're working with Office 365, it always pays to consult the mothership. Microsoft provides a comprehensive guide on how to correctly set up SPF records for your custom domain within their ecosystem. This document is your best friend because it clearly explains how Microsoft 365 uses SPF to bolster email security and, crucially, to help prevent email spoofing—a tactic often exploited in phishing schemes and other cyberattacks. Following their specific instructions ensures your SPF configuration is in harmony with their systems, which is key for both security and deliverability. I highly recommend bookmarking this page; it’s a resource you’ll likely return to.

Interpret and Resolve SPF Failures

Even with careful setup, SPF validation failures can sometimes pop up. Understanding why these occur is the first step toward fixing them. Typically, an SPF validation error indicates a mismatch: what your email server is actually doing doesn't line up with what your domain's DNS records say is authorized. This kind of discrepancy can, unfortunately, make it easier for spoofed emails—those pretending to be from your domain—to appear legitimate, thereby increasing your vulnerability to phishing. When you encounter an SPF failure, it's important to investigate the root cause. This could be anything from a simple typo in your record to missing IP addresses or exceeding those pesky DNS lookup limits. Once identified, you can then correct your SPF record to get things back on track.

Strengthen Email Security: Go Beyond SPF in Office 365

You've done a great job setting up your SPF records in Office 365 – that’s a solid move for protecting your domain! But if you're looking to really lock down your email security and ensure your messages hit the inbox, SPF is just the starting point. Think of it like this: SPF lays the foundation, but for a truly robust defense against spoofing and phishing, you’ll want to add DKIM and DMARC into the mix. These work together with SPF to create a much stronger shield for your emails.

Implement DKIM (DomainKeys Identified Mail)

So, SPF verifies that an email came from an authorized server, but what about the email's content? That’s where DKIM (DomainKeys Identified Mail) steps in. DKIM adds a unique digital signature to your outgoing emails. This signature is tied to your domain and is verified by the recipient's email server using a public key that you publish in your DNS records. It’s like putting a tamper-proof seal on your messages.

It's a key thing to remember that "SPF alone isn't enough. You also need DKIM and DMARC for the best email security." So, once your SPF is in place, the next logical step is to configure DKIM. This process ensures that the email genuinely originated from your domain and, crucially, that its contents haven't been altered en route. This adds a significant layer of trust and authenticity to your communications.

Use DMARC for Full Protection

Now that you have SPF checking the sender's server and DKIM verifying the message's integrity, DMARC (Domain-based Message Authentication, Reporting, and Conformance) acts as the enforcer. DMARC is a policy you publish in your DNS that tells receiving email servers what to do if an email claims to be from your domain but fails either the SPF or DKIM checks (or both). You can instruct them to simply monitor these emails, send them to the spam folder (quarantine), or reject them outright.

"Understanding how SPF, DKIM, and DMARC work together is essential for strong email security." DMARC also provides incredibly valuable reports, giving you visibility into who is sending email using your domain—both legitimate and fraudulent. This feedback loop helps you fine-tune your setup and identify any unauthorized activity. For the most "complete email authentication, you should use DKIM and DMARC" alongside a robust SPF record, ideally one that uses the -all (hard fail) enforcement rule. This trio forms a powerful defense against email impersonation.

Keep Your SPF Records Working: Long-Term Best Practices

Getting your SPF record set up for Office 365 is a brilliant move, but it’s not quite a "set it and forget it" task. Think of it more like tending to a garden; it needs a bit of ongoing attention to truly thrive and keep your email flowing smoothly. As your business grows, the tools and services you use for sending emails might change, and even email standards themselves can get updates. To make sure your important messages consistently reach those inboxes and your domain stays secure, adopting some long-term best practices for managing your SPF records is key. This proactive approach helps you sidestep future delivery headaches and keeps your email authentication in top shape. It’s all about regularly checking in on your SPF setup, staying in the loop with email security trends, and understanding how SPF fits into the bigger picture of email authentication. This way, you maintain that sweet spot where your legitimate emails sail through, and those pesky unauthorized senders are stopped in their tracks.

Conduct Regular Audits and Monitor Performance

Think of regular SPF audits as a routine check-up for your email deliverability. It’s a smart habit to periodically check your SPF record using an online validation tool. These handy tools can help you catch any syntax slip-ups, confirm that all your authorized sending services are correctly listed, and make sure you haven’t accidentally gone over the DNS lookup limit.

Keeping an eye on your email delivery rates and any bounce messages can also give you early warnings if something’s not quite right with your SPF configuration. If you notice an unexpected dip in how many emails are getting through, or an uptick in SPF-related bounces, it’s a signal to take a closer look. And if you're not entirely comfortable diving into these technical details yourself, there's no shame in reaching out to an IT professional or a service that specializes in email authentication for a helping hand.

Stay Informed About SPF Updates

The email security landscape is always evolving, so keeping yourself informed is pretty important. While the SPF standard itself is fairly stable, the best ways to implement it and how it works with other authentication methods like DKIM and DMARC can shift over time. Truly understanding how SPF, DKIM, and DMARC work together is fundamental for maintaining robust email security.

It's a good idea to watch for updates from Microsoft concerning Office 365 email practices, and also to follow general email security news from trusted sources. Misconfigured SPF records, especially when you add new sending services or remove old ones, can cause real email delivery headaches. A little ongoing learning can go a long way in preventing these kinds of problems and keeping your email flowing smoothly.

Balance Security with Email Deliverability

While SPF is a fantastic tool for helping prevent email spoofing, it’s good to remember that it’s one important piece of a larger email authentication puzzle. For the most effective protection and the best chance at optimal deliverability, SPF really shines when used alongside DKIM and DMARC. Microsoft's own guidance often points out that SPF alone isn't enough for top-tier email security.

When you're setting up your SPF record, particularly if you're also implementing DMARC, using the -all (hard fail) mechanism is generally the recommended approach. This tells receiving email servers to reject messages that fail SPF checks and don't align with your DMARC policy. This strong stance helps protect your domain's reputation, but it hinges on your SPF, DKIM, and DMARC records all being configured accurately to avoid unintentionally blocking your own legitimate emails.

Troubleshoot Your Office 365 SPF Records

Even with the most careful setup, you might hit a few bumps with your Office 365 SPF records. It happens to the best of us! The great thing is, most of these issues are quite solvable. Let's walk through how to spot and fix common problems, and figure out when it might be a good idea to bring in an expert.

Identify Common SPF Errors

One of the more frequent snags you might encounter are SPF validation errors. These usually mean there’s a disconnect between your email server's settings and what’s recorded in your domain's DNS (Domain Name System). Imagine your email server trying to send mail, but it's not on the "approved senders" list that receiving servers check – that's when a validation error can occur. This kind of misalignment can, unfortunately, make it easier for others to send emails that falsely appear to come from you, which is a risk for phishing and spoofing. Keeping these records accurate is a big step in protecting your domain and making sure your genuine emails get through.

Resolve SPF-Related Delivery Issues

If you think an SPF record is causing trouble with your email delivery, the first thing to do is take a close look at the record itself. Check the syntax very carefully; even a tiny typo or a bit of incorrect formatting can throw things off. It’s like proofreading an important message – every detail matters! Next, ensure you remove any senders from the record that are no longer authorized to send on your behalf or are simply invalid. Your SPF record should be a clean list of only the email servers that have your explicit permission to send emails for your organization. This helps receiving mail servers trust your emails, which is key for good email deliverability.

Know When to Ask for Professional Help

Sometimes, even after trying your best, an SPF issue can be a bit stubborn, or you might just not feel entirely comfortable making changes to your DNS settings. And that's completely fine! If you've gone through the troubleshooting steps and are still facing issues, or if the thought of adjusting DNS records feels a bit daunting, it’s a smart move to get some expert help. Professionals who specialize in email configuration and DNS management can often spot and fix complex SPF problems more quickly. If you find yourself in this spot and need that kind of support, you can always book a call with us at ScaledMail. We’re here to help make sure your email setup is running just as it should.

Frequently Asked Questions

I'm using Office 365 for my emails. Do I really need to worry about SPF records? Absolutely! Think of your SPF record as your email's official ID badge. It helps other email systems confirm that messages appearing to come from your business are genuinely from you, and not from someone trying to fake your address. Getting this right means more of your important emails land in inboxes instead of getting lost in spam folders, and it really helps protect your brand's good name from misuse.

Okay, I get that SPF is important for Office 365. But what if I also use a marketing tool to send emails? How does that fit in? That's a super common scenario, and a great question! The key thing to remember is that your domain can only have one single SPF record. So, you'll need to make sure that this one record includes all your authorized sending services – Office 365, your marketing tool, any customer service platforms, and so on. Each service usually provides the specific bit of text you need to add to your record.

I've heard SPF records can be tricky. What's a common pitfall I should watch out for when setting mine up? One of the most frequent hiccups I see is people accidentally creating more than one SPF record for their domain. It might seem logical to have separate ones if you use different services, but this actually confuses the email servers trying to verify your messages. Always aim to have just one, carefully crafted SPF record that lists all your legitimate senders.

Once my SPF record is set up for Office 365, am I all good with email security, or is there more to it? Getting your SPF record sorted is a fantastic and really important first step towards better email security! For an even stronger defense, you'll want to look into setting up DKIM and DMARC as well. These two work hand-in-hand with SPF to provide a more complete shield against email spoofing and phishing, giving your emails an extra layer of trust and authenticity.

Setting up my SPF record felt like a big step. Is it something I can just set and forget, or do I need to revisit it? It's definitely a big, positive step! While you don't need to be checking it daily, it's not quite a "set it and forget it" kind of thing. It’s wise to review your SPF record periodically, especially if you add new services that send email on your behalf, change email providers, or if you notice any delivery issues. A quick check-up now and then ensures everything is still working correctly to keep your emails delivering smoothly.