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.
Barracuda ESG flaws exploited, gaining root access
Apple, SAP, and Ivanti Patch Critical flaws Affecting Messaging, Bluetooth, and Enterprise Systems
Jailbroken DeepSeek AI Agent Conducts Two-Week Cyberattack on European Telecom
Daily Cyber security update for 10.11. 2026
IBM fixes 208 API Connect vulnerabilities, 47 critical
89 New ransomware groups emerge in 2026, claiming over 2,200 victims
Daily Cyber security update for 08.11. 2026
Japan banking crisis
Outage causes disruption at 128 japan banks: preventing ATM transaction
Daily Cyber security update for 06.11. 2026
Cyber attack causes French bank Credit Mutuel Arkea €100 million missing
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.
