Yesterday, I started to have e-mails to an Outlook.com friend being rejected as per others below. I am using a Windows 11 PC with Outlook 365. I phoned Plus.net's technical support service and the chap I spoke with suggested e-mailing my friend using plus.nets webmail service as a test. My friend received the e-mail OK.
This suggests that the server used for webmail is configured OK and the one used in the account setup in Outlook isn't.
I have Googled the issue this evening and found the following information regarding Microsoft's recent tightening up on spam controls. I have sent the information to the technical services chap in the hope that their e-mail server can be configured correctly:
The error "sending domain doesn't meet the required" indicates that emails sent from the domain are being rejected by the recipient's mail server due to a failure to meet the sender's email authentication requirements. Specifically, this likely means the domain is missing or has improperly configured SPF, DKIM, or DMARC records. Microsoft, among others, has recently implemented stricter email authentication requirements for bulk senders, and failing to meet these standards can lead to email rejections.
Here's a breakdown of the issue and how to address it:
-
Rejection, not spam:
The error message "550; 5.7. 515 Access denied, sending domain [SenderDomain] doesn't meet the required authentication level" means that your email was rejected outright, not simply moved to the spam folder.
-
Failed authentication:
The recipient's mail server is rejecting the email because it doesn't trust that the email genuinely originates from the domain mgrburnells.plus.com. This is usually due to missing or incorrect email authentication records.
-
Bulk sender policy:
This error is common for bulk senders (those sending 5,000 or more emails per day) and is part of a broader effort by email providers like Microsoft, Google, and Yahoo to combat spam and phishing.
-
1. Verify SPF, DKIM, and DMARC Records:
- SPF (Sender Policy Framework): Ensure your domain has a valid SPF record that correctly lists the authorized mail servers for your domain.
- DKIM (DomainKeys Identified Mail): Set up DKIM signing for your outgoing emails, which adds a digital signature to verify the message hasn't been tampered with.
- DMARC (Domain-based Message Authentication, Reporting & Conformance): Configure a DMARC record that specifies how receiving servers should handle emails that fail SPF or DKIM checks.
-
2. Check for errors in your DNS records:
Double-check that all your DNS records are correctly configured, paying close attention to syntax, spacing, and capitalization.
-
3. Monitor your email traffic:
Use DMARC reports to monitor your email traffic and identify any issues with your authentication setup.
-
4. Consider using a third-party service:
If you're struggling to configure these records yourself, consider using a third-party service to help manage and monitor your email authentication.
-
5. Consult with your email provider:
Reach out to your email hosting provider or domain registrar for assistance in setting up or troubleshooting your email authentication.
By taking these steps, you can ensure your emails are properly authenticated and delivered to your recipients' inboxes, avoiding the "550; 5.7. 515 Access denied" error.
