Category Archives: Fraud and Phishing

Getting Rejected at Microsoft with 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)

Reports are that Microsoft appears to have quietly launched a new DMARC policy that requires all senders, regardless of volume, to publish DMARC, SPF and DKIM records for email acceptance. If you are receiving the message:

550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)

when you send email to Outlook.com, Hotmail, MSN or Live email addresses, you need to update your email configuration quickly to maintain email delivery.

Note: As of November 12th, Microsoft has indicated that this was a misconfiguration of spam rules and rolled back to previous configurations. The suggestions here are still valid to help with your email reputation, just not a requirement to make the inbox at Microsoft’s email services.

What does 550 5.7.1 Message rejected mean?

For Business Senders to Microsoft Email Services

As of November 4th-5th, 2026, it appears that Microsoft now requires DMARC, SPF and DKIM records for delivery acceptance at the server level. This means that email sent to Microsoft email services could be rejected entirely at the server, i.e. not even allowed on the servers, much less the spam folder, without valid SPF, DKIM and DMARC records. While this effect has been reported to be sporadic, including some rejected messages with headers indicating “dmarc=pass” that later proved to be missing a DMARC record, it’s best to assume that Microsoft is increasing their security against spam, phishing and scammers. By becoming fully DMARC compliant, you can protect your valuable business email like invoices, orders, password resets, marketing campaigns, etc.

For Recipients on Microsoft Email Services

If you are an email recipient hosting your inboxes at a Microsoft service (Hotmail, Outlook.com, Office365, etc.) this is beneficial, despite the temporary loss of some email. Your email address is not being blocked. Microsoft is protecting the email you receive from potentially bad actors, reducing spam and the risk of fraud and phishing. If legitimate senders are having trouble reaching your inboxes or saying something like “emails to hotmail are bouncing”, they have some configuration work to do to achieve DMARC authentication (see below) and get to your inbox. Forward this post to help them out.

What do senders need to do?

First, SPF, DKIM and DMARC are all interacting pieces of DMARC compliance: SPF and DKIM each prove a message is legitimate, and, at the recipient, DMARC checks that they match the From address and tells Microsoft what to do when they don’t. It is important to verify the validity of your SPF, DKIM and DMARC records:

  • An SPF record defines IP addresses that can send on your behalf. Check your SPF with our free SPF Lookup Tool.
  • A DKIM record provides a digital key to verify your emails’ digital signature. By DKIM signing outbound email you can claim ownership. Check your DKIM Record(s) with our free DKIM Lookup Tool.
    (Note: you need to know your DKIM selector(s) for each sender you are using.)
  • A DMARC record enables you to define email addresses to receive feedback on your email and a policy for how to treat non-compliant email. Check your DMARC record with our free DMARC Lookup Tool.

Second, if any of your records are missing or incorrect, make updates to your records. Our lookups provide specific errors and detailed descriptions of the problem. Follow the problem details recommendations provided to correct your SPF, DKIM or DMARC records, these will help improve your email delivery. MxToolbox also provides free tools to help you generate new records:

Next, confirm everything with MxToolbox’s free Outlook Compliance tool to test your email configuration’s compliance with Microsoft, Google and Yahoo bulk sender rules, including SPF, DKIM and DMARC compliance. Test each of your internal and 3rd party email sources to ensure all are properly configured.

Finally, DMARC is not a “set and forget” technology. To maintain DMARC compliance, you need to receive and analyze DMARC XML reports about the email coming from your domain. DMARC XML reports are sent daily from each inbox provider and contain details of that day’s individual sender. You can review them individually in our free DMARC XML tool to check on email delivery. Problems could affect your email delivery, including:

  • New senders missing from your SPF records.
  • Senders missing DKIM signatures.
  • Senders attempting to use your domain in Fraud and Phishing emails.

DMARC requires on-going management and maintenance in order to achieve the best email delivery and managing individual XML reports on a daily basis becomes cumbersome.

MxToolbox provides a complete email delivery suite designed to protect your email delivery reputation, including SPF, DKIM and DMARC management, and get your email to the inbox. MxToolbox Delivery Center has:

  • Adaptive Blacklist monitoring to alert you to issues with your senders’ reputation
  • DMARC Compliance reporting and monitoring to maintain compliance with Microsoft, Google and Yahoo bulk sender requirements
  • Step-by-step workflows to achieve DMARC Enforcement and protect your domain from being used in fraud and phishing
  • BIMI Management and hosting to get your logo in the Inbox.
  • Inbox Placement analysis with Google Postmaster Spam rates to analyze the potential inbox performance of your campaigns and your spam rates, so you can get your message to the inbox.

Get ahead of email delivery issues with MxToolbox.

DMARC Policy Enforcement – the Value

Last week, we discussed three myths that hold businesses back from configuring DMARC for policy enforcement. In this article, we will highlight all the advantages of DMARC policy enforcement and why these greatly offset the risk discussed last week.

Benefit 1 – BIMI

Would your marketing department love to have your logo next to your email campaigns? Of course! BIMI does that for you at many inbox providers worldwide! To adopt BIMI and get your corporate logo next to your email, you first need a strict DMARC policy at 100% quarantine or reject. Learn more about BIMI to understand the additional requirements to adopt BIMI.

Benefit 2 – BEC prevention and cyber-attack insurance

Business Email Compromise (BEC) often occurs through email that appears to come from a trusted internal source. When a business lacks DMARC policy enforcement on inbound and outbound email, BEC fraud becomes simpler for scammers; all they need to do is spoof the existing domain without the need to use a look-alike domain. By adopting a strict DMARC policy for outbound mail and a receiving policy that rejects or quarantines inbound mail failing DMARC, businesses make BEC more difficult. Many cyber insurers now ask about DMARC enforcement during underwriting, and it can affect eligibility and premiums.

Benefit 3 – Reputation Improvements

Inbox Providers like Google, Yahoo and Microsoft leverage proprietary acceptance algorithms based upon sender domain reputation and content reputation as well as meeting certain bulk sender requirements. DMARC policy enforcement is a clear trust statement by a business, that puts your domain ahead of bulk sender requirements.

Benefit 4 – Government Compliance

Government agencies across the world (US, UK, Canada, the Netherlands, Australia and others) require DMARC policy enforcement on their own domains and some require the same of contractors. Since governments and government contractors are major targets for compromise, DMARC policy enforcement helps protect sensitive communication and important governmental data.

Benefit 5 – SOC2, ISO27001 and other standards

Many standards like SOC2, ISO27001 and PCI-DSS require methods to protect and secure sensitive business communications. While not specifically required by SOC2 and ISO27001, DMARC policy enforcement supports and evidences the controls necessary for the standard. PCI-DSS cites DMARC, DKIM and SPF specifically in the guidance to meet the standard. Learn more about PCI-DSS.

How can MxToolbox help?

MxToolbox has over 20 years experience in Email Delivery with Blacklist, DMARC and Inbox Placement solutions designed to improve your email delivery and get your email to the inbox. DMARC policy enforcement is an integral piece of the email delivery puzzle and our tools make it easy to adopt DMARC and migrate to a strict enforced DMARC policy. Learn more about how MxToolbox Delivery Center can help with DMARC policy enforcement.

DMARC Policy Enforcement – the Myth

Policy enforcement can be one of the most valuable aspects of DMARC. Unfortunately, only 80% of businesses are taking advantage of it, primarily due to misunderstandings of the technology that lead to fear. Let’s investigate some of the myths and payoffs to adopting restrictive DMARC policies.

Myth 1 – DMARC Policy enforcement is complicated

Truthfully, it is more complicated that simply adopting DMARC. Many companies simply created a DMARC record to comply with Google and Yahoo bulk sender requirements. However, with DMARC policy enforcement, businesses need to iteratively adopt strict policies, monitor the outcomes and then designate someone to actively monitoring DMARC compliance rates. While this appears more complex, you can easily accomplish this with a service, like MxToolbox Delivery Center, that integrates iterative policy adoption, monitors your SPF, DKIM and DMARC compliance rates and alerts you to possible issues.

Myth 2 – DMARC policy won’t improve my email campaign performance

While a strict DMARC policy does not appear to aid email campaign delivery directly, it actually affects your spam rate. Google, Yahoo and Microsoft have adopted Bulk Sender requirements that mandate a maximum spam rate, the percentage of emails from a domain marked as spam by their users. With an open DMARC policy spammers and fraudsters can send email that appears to come from your domain and is likely to be marked as spam. By adopting a strict DMARC policy, you are filtering out that poor quality email from spammers and fraudsters before it could be marked as spam. By reducing your apparent spam rate, setting up a strict DMARC policy will actually improve your inbox performance.

DMARC enforced email indicates that a business takes ownership of its email delivery.

Myth 3 – A strict DMARC policy might block legitimate email

Unfortunately, this is the most pervasive belief in the industry. While there is some truth to this belief, when properly configured and monitored, there is minimal risk of losing legitimate email to strict DMARC policy enforcement. Using a DMARC management, reporting and monitoring tool like MxToolbox’s Delivery Center, businesses will have all the tools necessary to set a strict DMARC policy, monitor senders for DMARC compliance and alert when a sender is non-compliant. With proper setup, the only email you might lose to strict DMARC enforcement:

  • New senders not authorized in the SPF record lacking correct DKIM setup. Monitoring tools will quickly alert to missing senders like this.
  • Forwarded or mailing list emails that improperly modify the header and break the DKIM signature. While ARC was intended to address this issue, most forwarders now respect the DKIM signature, so this problem is vanishing.
  • DKIM Key rotation errors. This issue should be quickly discovered and short lived.

How can MxToolbox help?

MxToolbox has over 20 years experience in Email Delivery with Blacklist, DMARC and Inbox Placement solutions designed to improve your email delivery and get your email to the inbox. DMARC policy enforcement is an integral piece of the email delivery puzzle and our tools make it easy to adopt DMARC and migrate to a strict enforced DMARC policy. Learn more about MxToolbox Delivery Center.

The SPF Struggle is real – What happened at reddit?

We’ve talked about SPF Limits and SPF Flattening in the past. There is simply too much demand to get into the SPF record. Whether it’s adding a new sender or an existing sender updating and include, senders sometimes necessarily and sometimes lazily add too many lookups into your SPF record. In fact, one well-known CRM goes so far as to write dynamic macros in their SPF record to avoid hitting the 10 include limit.

What is the issue?

Currently, reddit has published an SPF record with too many includes, meaning that during email delivery, the last includes to be checked are dropped. This could leave one or more of reddit’s legitimate senders appearing to be spam or phishing because email from these senders will fail SPF Authentication.

In addition, reddit is running a DMARC policy of “reject”. While it is up to the individual Inbox Provider, a DMARC reject policy instructs the recipient systems to reject email that is not DMARC compliant, which means trashing any email that fails SPF Authentication. Essentially, there is an unknown amount of email from reddit that cannot be delivered, potentially affecting accounts, customers, purchases, etc.

What can they do?

There are several ways to get your SPF record below the 10 lookup threshold:

  • Manual or Automatic SPF Flattening as discussed in our blog.
  • Reducing the number of senders.
  • Splitting email sending across multiple domains or subdomains with separate SPF records.

All of these options have pros and cons. Many senders do not want to lose the cache of their primary domain, some cannot consolidate vendors to reduce SPF complexity, and some SPF records cannot be easily manually flattened. Even if you get below the threshold today, vendors may add new includes to their SPF records tomorrow pushing you over the threshold again.

What’s going to happen?

With a proper DMARC reporting and management system, like MxToolbox Delivery Center, they should already be seeing SPF failures and working to fix their SPF record. In the short-term, reddit will see some of their email bounce, in the long-term, this could cause their domain to have serious reputation issues.

How can MxToolbox help?

You first need to know if you have a problem before solving it.  MxToolbox offers a Free SPF Lookup Tool where you can check your real-time SPF configuration for errors, including the risk of “Too Many Includes”.  We also have a suite of Email Delivery tools to help you manage DMARC, SPF and DKIM and get your email to the Inbox.

DMARC Compliant but still going to Spam?

Many emailers consider DMARC compliance to be an end goal. This is only partially true. Adopting DMARC and sending DMARC compliant email is an important part of maintaining good email delivery, but DMARC is not the end of that journey. Let’s examine a few other things you need to be doing.

Adopting DMARC “Reject” policies

DMARC works best when your DMARC policy is 100% Reject for emails that are not DMARC compliant. 100% DMARC Reject indicates to Inbox Providers that you are confident that legitimate email from your domain is DMARC compliant and anything that is not compliant is spam, phishing or otherwise risky. 100% Reject policies are required to adopt BIMI and maintain compliance with Google, Yahoo! and Outlook.com bulk email sender policies.

Monitoring DMARC compliance

Your email configuration is not “set and forget”. Every time you change a technology provider, you will need to update your SPF record to send email from that system: CRMs, order management systems, Support, Marketing Automation, etc. all require an entry in your SPF records. Even if you do not change systems every few years, these companies will change their sending IP addresses or undergo mergers, forcing changes on you. You need to monitor your DMARC compliance or you may miss when email is rejected.

Adopting BIMI

BIMI can get your brand directly in front of your customers and prospects, within the Inbox. But, to adopt BIMI, you must be at 100% DMARC Reject policy. A Reject Policy requires monitoring of your DMARC compliance to prevent loss of legitimate email through misconfiguration.

Monitoring Inbox Placement

Even with 100% DMARC compliant email, you could be rejected from the Inbox. Inbox Providers maintain the equivalent of internal blocklists using customer sentiment and algorithms that judge similarity to spam to place email in Spam, Junk or Quarantine folders. If you are not monitoring your email for this, you will only find out after important email is turfed to the Junk folder.

Managing Email Senders

Your 3rd party email senders are an important part of your email delivery hygiene. A sender that mixes your email in with other clients’ email may cause issues due to the poor reputation of these other senders. If a shared IP address is blacklisted, your email may be blocked simply because some of it came from that server. Purchasing a dedicated sending IP space may reduce the risk, but it is always prudent to monitor your 3rd party senders for compliance and blocklist issues. If frequent blacklisting occurs, it might be time to look at new senders.

How can MxToolbox Help?

MxToolbox has been building email delivery management and monitoring tools for over 20 years. Our Experts know that email delivery is not static but an ever-changing arms race between spammers and Inbox Providers. Our MxToolbox Delivery Center tools are constantly updated to provide you with the latest in Email Delivery technologies:

  • Setup, Maintain and Monitor DMARC compliance
  • Adopt DMARC reject policies with confidence
  • Get your logo in the Inbox with our BIMI tools
  • Regularly test your Inbox Placement to quickly detect internal blocklisting
  • Get insight into your senders’ reputations with Adaptive Blacklist Monitoring

If this sounds complicated, MxToolbox also offers Managed Services team that can help you setup DMARC, DKIM, SPF, BIMI and get your domain aligned with Google, Yahoo! and Outlook.com bulk sender policies.

Google to support Common Mark Certificates for BIMI

We’ve discussed the value and difficulties of BIMI in the past, but it appears that there is some growing support for the standard that might make it more relevant to small and medium businesses – Google has announced that it will support Common Mark Certificates and display the BIMI logo for companies opting this route.

What is BIMI?

BIMI is an Internet standard for taking ownership of email and securing your outbound brand that also provides clear indication of trust by displaying the Brand Owner’s Logo in the UI of the email client. To have your Brand Logo displayed by your email, you need:

  • To be DMARC compliant
  • To have DMARC policy of Reject
  • To have a compatible BIMI logo in DNS
  • To have certified ownership of that brand logo

The big value of BIMI is that the logo in the UI provides reassurance that the email does indeed come from you and that you are a trusted sender.

Why is this a big deal?

Until this announcement, the only type of certification for brand ownership was a Verified Mark Certificate (VMC). VMC’s initially cost between $1000 and $1500 per year, per domain and required the owner to obtain an official government trademark on the logo and branding. If you broke your email across multiple domains or manage multiple sending brands, a VMC could get expensive quickly. In addition, many smaller businesses would find governmental registration of their trademark difficult, and the expense might price them out of the verification altogether.

Common Mark Certificates (CMC) are another method of certifying your logo and protecting your brand from being used in fraud and phishing, while providing the benefit of display in the recipients’ inboxes. Because CMC’s do not require official trademark, the hope is that CMC’s will reduce the cost of certification and broaden support and use of BIMI.

The Caveat

Don’t rush out today and grab a CMC. Why? Because you can’t. The BIMI workgroup only announced support recently and vendors have yet to define the product and pricing for a CMC. Most likely pricing will be very similar to that of a VMC, so even with the “greater flexibility” to obtain a mark certificate, the cost might be prohibitive.

How can MxToolbox Help?

Regardless of whether or not you are adopting BIMI, adopting DMARC and getting DMARC to a strict policy is imperative for good email delivery.  MxToolbox Delivery Center has everything you need to improve your email delivery:

  • Manage SPF, DKIM, DMARC to improve compliance and reduce the threat of fraudsters and phishing campaigns using your domain. DMARC will get you prepared for BIMI.
  • Review daily volume and SPF, DKIM, and DMARC compliance rates to ensure the best email deliverability.
  • Gradually move your DMARC policy to “Reject” to enable better inbox placement opportunities and reduce the risk of phishing and fraud using your domain. Also, it is the next step to become BIMI compatible
  • Check and maintain your BIMI setup, including certificate configuration and alerts to when certificates will age out.

We also provide free tools!  To get started with BIMI, check out our Knowledge Base and free BIMI Lookup tool.

Business Email Compromise (BEC) Fraud on the Rise

Cybercriminals are a major threat to business email. Through various business email compromise (BEC) scams, these fraudsters can cause irreparable financial and reputational damage to your company. With BEC on the rise, protecting your inbound (and outbound) messages is vital to your company’s success and longevity of its brand.

What Is Business Email Compromise (BEC)?

BEC attacks are financial in nature and target organizations of all sizes. The gist of a BEC scam is a fraudster pretends to be someone at the executive level, then convinces an unsuspecting employee to help them wire funds outside of the company. BEC compromises often use publicly available information, phone calls and emails from domains that are similar in nature to the target company. For example: targeting MxToolbox.com with an email from MxTooŀbox.com. Look closely.

Loss numbers are frequently significant, and it’s a very appealing tactic for scammers looking to get rich quick.

Unreported BEC (Needed?)

Many instances of BEC fraud go unreported because few companies want to admit that they fell victim to a scam. As a result, cases are typically hidden until court proceedings. It’s difficult to gauge how much money is actually lost to BEC scams per year, but the estimates are astronomical.

Common Types of BEC Attacks

According to the FBI, there are five common types of BEC scams:

Email Account Compromise

In an email account compromise attack, an employee’s email account is hacked and used to request payments from vendors. The money is then sent to attacker-controlled bank accounts.

Vendor Email Compromise

Companies with foreign suppliers are common targets of vendor email compromise. Attackers pose as suppliers, request payment for a fake invoice, then transfer the money to a fraudulent account.

CEO Fraud

Scammers impersonate the CEO or executive of a company. As the CEO, they request that an employee within the accounting or finance department transfer funds to an attacker-controlled account.

Lawyer Impersonation

Fraudsters pose as a lawyer or legal representative, often via email. The common targets of these attacks are lower-level employees who might not have the knowledge or experience to question the validity of an urgent legal request.

Data Theft

Data theft attacks typically target HR personnel to obtain personal information about a company’s CEO or other high-ranking executives through emails. The attackers can then use the received data in other future attacks, such as CEO fraud.

Tips to Avoid BEC Scams

Because email is such a critical aspect of your business, a single compromised account is all it takes to financially damage your company and its brand. Here are some tips on how to stay protected and secure:

  • Carefully scrutinize all emails. Be wary of irregular emails that are sent from C-suite executives, as they are used to trick employees into acting with urgency. Review emails that request transfer of funds to determine if the requests are irregular.
  • Educate and train staff. While employees are a company’s biggest asset, they’re also usually its weakest link when it comes to security. Commit to training them according to the company’s best practices. Remind all that adhering to company policies is one thing, but developing good security habits is another.
  • Confirm any changes in vendor payment location by using a secondary sign-off by company personnel.
  • Stay updated on your customers’ habits, including the details and reasons behind payments.
  • Verify requests for transfer of funds when using phone verification as part of two-factor authentication.
  • If you suspect that you’ve been targeted by a BEC email, immediately report the incident to law enforcement or file a complaint.

How Can MxToolbox Help? (DMARC)

DMARC helps secure your company’s email platform and fights to protect against BEC scams. By implementing DMARC checks on inbound email and educating employees, the prevalence of online fraudsters and their BEC cons can be minimized. In addition, Implementing DMARC on outbound email will reduce of your brand being used in a BEC scam, potentially damaging your business reputation.

At MxToolbox, our email experts have created several tools and services to safeguard your business and increase its email deliverability. Check out our various products to help protect your company’s email reputation.

Google expands support for BIMI: Is it time to dive in?

Google recently rolled out additional support for BIMI through their Gmail.com webmail application and mobile apps.  Since Google is one of the largest Inbox Providers in the world, this should be an exciting step forward for BIMI and for Marketers wanting to reach potential customers.  (For more information on BIMI, click here.)

Google’s Implementation

On Gmail.com and Google mobile applications, users will see a checkmark and BIMI logo next to an opened email as in the image below.  In addition, Google mobile applications will display the logo next to the sender in the Inbox view by the subject line.  BIMI logos should lead to an uptick in Open Rates and Click-through Rates because of additional confidence in the “certified” origins of these emails.

In order to have your logo displayed, Google requires you to:

  1. Setup SPF, DKIM and DMARC
  2. Have a DMARC Policy set to 100% Reject for email failing DMARC
  3. Generate and post a correct BIMI logo
  4. Have a Verified Mark Certificate (VMC)

The first two steps will dramatically improve a sender’s email delivery and email reputation.  Adopting DMARC gives Inbox Providers more assurance that your email is legitimate and not spam, while a strict DMARC policy prevents your email domain from being used in phishing and fraud attacks.  A VMC is designed to protect both Google and your brand by certifying the owner of the logo and domain.  Unfortunately, a VMC costs roughly $1100-$1500 annually per Email Sending Domain, which makes it expensive for many small businesses.

What other Inbox Providers support BIMI?

The BIMI working group has a list of all current Inbox Providers that support BIMI.  The good news is that big, global Inbox Providers like Apple, Yahoo!, and now, Google support BIMI as do several smaller or local providers like Fastmail and LaPoste.  This list appears to be growing.

Unfortunately, consistent logo display is an issue.  Many Inbox Providers only have partial support for BIMI or support different rules for displaying BIMI logos online vs via mobile applications.  In addition, many providers do not support BIMI logos in the Inbox view, where most people make the decision on whether or not to open the email.  This reduces the impact to Open Rates and subsequent downstream effects, like Click-through rates and Sales.  

MxToolbox Expert Take

Increased support for BIMI is a great sign for the technology.  After over four years of moving glacially forward, we’re hopeful that this will increase the pace of BIMI adoption.  To a Marketer, the idea of having your logo proudly displayed next to your verified email in the Inbox both increases the chance of the recipient opening the email and improves the reputation of the brand. 

There are Drawbacks

However, the current level of support does not entirely live up to that promise: few Inbox Providers display the logo in the Inbox where Open Rates will be affected. In addition, the extra expense associated with a Verified Mark Certificate might be considered burdensome for many small businesses, leaving gains to the larger businesses and brands.  While the extra security from a VMC is like that of an SSL certificate for ecommerce, the additional value BIMI provides may not be there for every brand yet.  

There are Alternatives

Finally, both Google and Microsoft already have other ways to display user images or logos in the message view of an individual email.  If the sender is a Google Workspace user, their preferred image will be displayed in the same spot as the BIMI logo.  Microsoft offers Microsoft Business Profile program to create a unique identifier card. Office Web Apps in Office 365 and Outlook.com use the verified icon provided to Microsoft when a company joins the program.  A savvy marketer might be able to get much of the BIMI effect from these alternatives.

MxToolbox Recommendation

Focus on the basics of Email Delivery: Technologies like SPF, DKIM and DMARC, and Best Practices in email list management and content relevance. Once your DMARC configuration is really set, then think about icing the cake with BIMI.  To get started with BIMI, check out our Knowledge Base and free BIMI Lookup tool.

Adopting DMARC and getting DMARC to a strict policy is imperative for good email delivery and adopting BIMI. Get started today with MxToolbox Delivery Center.

Google’s Recent SMTP Relay Exploit and DMARC Policies

In April, Google began to see an uptick in spoofing attacks that utilized their SMTP Relay system and compromised Google accounts. They have closed the loophole by May, however, at least 30,000 malicious emails were detected in a two-week period. While this is an extremely small chunk of Google’s email traffic, similar exploits can affect other outbound email providers, requiring patches and constant vigilance.

What is the SMTP Relay exploit?

Google has a great reputation as an outbound sender so email coming from their servers is generally accepted. Google allows their customers to leverage that reputation to send bulk or large quantities of email through the SMTP Relay connection. Before the fix, this enabled any Google customer to send email that looked like another Google customer by simply putting their domain in the “From:” field. For example, SmallCompany.com gets hacked by a scammer and begins to send email that looks like GreatBrand.com, a well respected company also hosted at Google.

  • Blacklists – Google rotates sending IP addresses to minimize the affects of blacklists so a blacklist will not generally catch this issue.
  • SPF Authentication – Both SmallCompany.com and GreatBrand.com have Google’s servers in the SPF record, so it passes Authentication. This might be enough to make the inbox.
  • SPF Alignment – The “From:” address says GreatBrand.com. The <ReturnPath> is SmallCompany.com so it fails SPF Alignment.

So, unless the recipients servers are configured to check SPF Alignment, the Spoofing email may make the inbox. Any brand could then be compromised by a hack to another company in the same outbound email provider.

How do you protect your brand from spoofing?

First, you might think to bring all email in-house. This just compounds your risk. Google and other outbound email providers have more security experts and experience than even most large companies can ever hope to bring to bear. A small or medium business should leverage that experience to protect their brand and get their emails delivered.

Second, adopt DMARC and SPF, and DKIM. A properly configured SPF, DKIM and DMARC setup will help prevent spoofing of your brand and give you insight into potential spoofing issues.

Finally, adopt DMARC “Reject” policies. A DMARC “Reject” policy instructs recipient providers to highly scrutinize in-bound email and reject anything that fails SPF Alignment or Authentication. A “reject” policy would immediately fail email that arrived using the recent SMTP Relay exploit.

Why are few companies adopting “Reject” Policies?

If “reject” policies are great, why aren’t companies adopting them immediately? Unfortunately, there is a lot of fear and misunderstanding about “reject” policies. Our Experts receive push-back every day from our clients. Let’s look at a few examples:

“My legitimate email might be rejected”

While it is possible for legitimate email to be rejected, it is far more likely to be accepted if you have a “reject” policy in place. Inbox providers are looking for relevant content from senders with good reputations. By telling setting up DMARC with a “reject” policy you are telling them that you value your reputation. In addition, the “reject” policy is telling them to throw out emails that might harm your reputation.

“I won’t know if a legitimate source comes online”

Maintaining good email delivery means ensuring that all your legitimate email sources are managed actively. Each source should be included in your SPF record to ensure SPF Authentication. While it is possible for a department to bring in a new 3rd party email source without telling you, these vendors will have detailed information about proper SPF configuration as part of their on-boarding process. If it still slips by, then is it really valid email? Could that rogue department be hurting your brand? Regardless, a comprehensive DMARC reporting tool, like MxToolbox Delivery Center, will alert you that a potential Verified Email Source is missing.

“I won’t know if a phishing attack occurs”

The beauty of DMARC is that by publishing a DMARC record with RUA and RUF tags, you are asking for information about the compliance of emails that come “from” your domain. Inbox providers will tell you through an XML email report. Regular reviews of these reports will give you insight into legitimate sources that fail as well as emerging email threats from phishing attacks using your brand. While you can manually parse these XML files, most companies rely on a reporting tool, like MxToolbox Delivery Center, to process and distill these files into actionable insights.

“It seems complicated…”

While it can take some time to verify your outbound email sources, ensure that SPF and DKIM configurations are correct and monitor DMARC reports to ensure that everything is properly tuned, moving to a “reject” policy is not very complicated. MxToolbox Delivery Center uses our experience with DMARC to make recommendations on when to move to a “quarantine” or “reject” policy and how much of your mail to send under that policy.

If you still find it complicated, you can leverage our Expert Managed Services to help you with your configuration.

What do MxToolbox Experts recommend?

Our team of Experts is always evaluating the newest email technologies – DMARC “reject” policies are a necessity to help improve your brand reputation by stopping phishing attacks using your brand. If more brands adopted DMARC “reject” policies, phishing attacks would be greatly reduced. It’s time for all companies to be DMARC compliant – Get Started Today!

It’s time to adopt MTA-STS

Inbox Providers like Google, Yahoo! and Outlook.com are in a constant arms race trying to protect their users from spammers, spoofers and irrelevant content. Since the late 90’s dozens of new technologies have been proposed and adopted, including: Blacklists, TLS Encryption, SPF, DKIM, DMARC, BIMI and, now, MTA-STS. With the continued progression of MTA-STS, it is now time for all domains to adopt the technology to secure inbound email and reduce the threat of spam.

What is MTA-STS?

MTA-STS is an update to TLS Encryption that allows an Inbox Provider to specify a list of secure servers to receive email and mandates a secure TLS connection to these servers. Insecure connections will not be accepted. This corrects a few of the short-comings of TLS alone: Expired TLS Security Certificates, Man-in-the-Middle Attacks and attacks that downgrade to no encryption.

How does MTA-STS Work?

When a sender wants to connect to an inbox provider or domain’s email servers to deliver email, they first query the MTA-STS DNS entry which contains the location of a policy file. The policy file is accessed via HTTPs and contains information about the correct servers to use, which must match the MX records exactly, the TLS encryption requirements, the MTA-STS policy mode and the maximum length to cache this information. Senders then encrypt communication with the servers and transmit the email.

Since the sender is required to verify the connection and it is encrypted to known servers, the sender has a slightly higher level of trust. Any sender that fails this mini test can be considered a threat.

What does MxToolbox recommend?

MxToolbox recommends that all companies setup MTA-STS for their receiving domains to inform senders that their email servers and providers accept secure message delivery using SMTP over TLS and also require that email should not be delivered using an insecure SMTP connection. When MTA-STS is enabled for your receiving domain, it requests external servers to send messages to your domain only when the SMTP connection is authenticated with a valid public certificate AND encrypted with TLS 1.2 or higher. This is a higher level of security for incoming email and should reduce spam to your domain.

In addition, you should ensure that all your domain’s email senders support MTA-STS. This includes your email server software, email marketing, and any other potential email senders: CRM, Order Management, Support, etc. Once you select a provider’s MTA-STS policy, messages sent from your domain to external servers will also comply with the standard and improve delivery.

Test Your MTA-SLS setup with MxToolbox

To help all our users get a head start with MTA-STS, we’ve created a free lookup tool as part of our SuperTool. Check your MTA-STS policy setup as well as any email sender!