InfoSecBulletin Cybersecurity for mankind
Microsoft recently issued a warning to Microsoft 365 email senders. They advised them to authenticate outbound messages. This action was prompted by Google’s recent announcement of stricter anti-spam rules for bulk senders.
“By setting up email authentication for your domain, you can ensure that your messages are less likely to be rejected or marked as spam by email providers like Gmail, Yahoo, AOL, Outlook.com,” the Microsoft Defender for Office 365 team said.
Hacker claim to access Rajasthan Police data: 70,000 records allegedly exposed
Update now! PHP2Shell: Critical PHP vulnerabilities patched
Trump says data centres should pay dividends to local community
Hackers Actively Exploiting Palo Alto VPN Flaw Via CVE-2026-0257
DeepSeek AI banned by U.S. Government; federal agencies must remove all related tools
CISA, NSA and NIST Publish New 10 AI Agent Control Guidelines
Claude AI Cracks 25-Year NSA Cryptography Number Mystery in Just 30 Minutes
Bypassing firewalls, AI Agents Accessed Indian ‘ Data Without Permission: CERT-In
MITRE ATT&CK v20 Unveils 9 New Attack Techniques On AI Exploits, MFA Bypass, and CAPTCHA Evasion
Hackers Exploit Fortinet Flaws to Deploy Stealthy PEERSTITCH Malware on FortiGate Firewalls
ALSO READ:
EC summoned Lands Ministry’s IT team and vendor intelligence clearence report
“This is especially important when sending bulk email (large volume email), as it helps maintain the deliverability and reputation of your email campaigns.”
Not following new email authentication standards can cause emails to be rejected or marked as spam.
Microsoft has cautioned against using Microsoft 365 for sending large amounts of emails. If emails exceed the sending limits, they may be blocked or sent to special delivery pools identified as high risk by the outbound spam controls in Exchange Online Protection (EOP).
Organizations that want to deliver bulk emails through EOP will have to abide by this outbound spam protection guidance:
- Exercise caution not to exceed the sending limits in the service by sending emails at a high rate or volume. This includes refraining from sending emails to a large list of BCC recipients.
- Refrain from using addresses in your primary email domain as senders for bulk emails, as it may impact the delivery of regular emails from senders within the domain. Instead, consider utilizing a custom subdomain exclusively for bulk email.
- Ensure that any custom subdomains are configured with email authentication records in DNS, including SPF, DKIM, and DMARC.
Microsoft warns that following their recommendations does not guarantee delivery. If your email is rejected as bulk, they suggest sending it through on-premises or a third-party provider.
