AOL and YAHOO emails undeliverable from Office365

%3CLINGO-SUB%20id%3D%22lingo-sub-1739376%22%20slang%3D%22en-US%22%3EAOL%20and%20YAHOO%20emails%20undeliverable%20from%20Office365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1739376%22%20slang%3D%22en-US%22%3E%3CP%3Esending%20to%20aol%20%26amp%3B%20yahoo%20are%20kicking%20back.%20Anyone%20else%20getting%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethis%20is%20the%20message%3A%3C%2FP%3E%3CP%3E%3CSPAN%3Eour%20message%20to%3C%2FSPAN%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B-%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Ecouldn't%20be%20delivered.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EWhen%20Office%20365%20tried%20to%20send%20your%20message%2C%20the%20receiving%20email%20server%20outside%20Office%20365%20reported%20an%20error.%3C%2FSPAN%3E%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3EHow%20to%20Fix%20It%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ECheck%20the%20%22Reported%20Error%22%20from%20the%20%22Error%20Details%22%20section%20shown%20below%20for%20more%20information%20about%20the%20problem.%20The%20error%20might%20tell%20you%20what%20went%20wrong%20and%20how%20to%20fix%20it.%20For%20example%2C%20if%20the%20error%20states%20that%20the%20message%20was%20blocked%20due%20to%20a%20potential%20virus%20or%20because%20the%20message%20was%20too%20large%2C%20try%20sending%20the%20message%20again%20without%20attachments.%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EIf%20you're%20not%20able%20to%20fix%20the%20problem%2C%20it's%20likely%20that%20only%20the%20recipient's%20email%20admin%20can%20fix%20it.%20Contact%20the%20recipient%20by%20some%20other%20means%20(by%20phone%2C%20for%20example)%20and%20ask%20them%20to%20tell%20their%20email%20admin%20about%20the%20problem.%20Give%20them%20the%20%22Reported%20Error%22%20from%20the%20%22Error%20Details%22%20section%20below.%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%3CBR%20%2F%3E%3CEM%3EWas%20this%20helpful%3F%20%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2Fp%2F%3FLinkID%3D717199%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ESend%20feedback%20to%20Microsoft%3C%2FA%3E.%3C%2FEM%3E%3C%2FP%3E%3CHR%20%2F%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%3EMore%20Info%20for%20Email%20Admins%3C%2FSPAN%3E%3CEM%3EStatus%20code%3A%20550%205.0.350%3C%2FEM%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EThe%20error%20reported%20by%20the%20receiving%20server%20wasn't%20specific%20enough%20to%20determine%20the%20exact%20nature%20of%20the%20problem.%20These%20errors%20often%20indicate%20the%20message%20violates%20a%20security%20or%20policy%20setting%20configured%20on%20the%20recipient's%20email%20servers.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EIf%20the%20sender%20is%20unable%20to%20fix%20the%20problem%20by%20modifying%20their%20message%2C%20then%20it's%20likely%20a%20problem%20that%20only%20the%20recipient's%20email%20admin%20can%20fix.%20Try%20the%20following%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3ECheck%20the%20error%20for%20information%20about%20the%20problem%20-%3C%2FSTRONG%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EThe%20%22Reported%20Error%22%20returned%20by%20the%20external%20email%20server%20can%20be%20found%20in%20the%20%22Error%20Details%22%20section%20below.%20This%20error%20might%20tell%20you%20what%20went%20wrong%20and%20provide%20clues%20for%20how%20to%20fix%20it.%20For%20example%2C%20if%20the%20error%20states%20the%20message%20was%20rejected%20due%20a%20Sender%20Policy%20Framework%20(SPF)%20issue%2C%20then%20you'll%20have%20to%20work%20with%20your%20domain%20registrar%20to%20correctly%20configure%20your%20domain's%20SPF%20records.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3ECheck%20the%20error%20for%20information%20about%20where%20the%20problem%20is%20happening%20-%3C%2FSTRONG%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EFor%20example%2C%20look%20for%20a%20domain%20name%20like%20contoso.com.%20A%20domain%20name%20in%20the%20error%20might%20suggest%20who%20is%20responsible%20for%20the%20error.%20It%20could%20be%20the%20recipient's%20email%20server%2C%20or%20it%20could%20be%20a%20third-party%20service%20that%20your%20organization%20or%20the%20recipient's%20organization%20is%20using%20to%20process%20or%20filter%20email%20messages.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3EIf%20you%20can't%20fix%20the%20problem%2C%20contact%20the%20responsible%20party's%20email%20admin%20-%3C%2FSTRONG%3E%3CSPAN%20class%3D%22Apple-converted-space%22%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EGive%20them%20the%20error%20code%20and%20error%20message%20from%20this%20non-delivery%20report%20(NDR)%20to%20help%20them%20troubleshoot%20the%20issue.%20For%20security%20or%20policy%20violation%20issues%2C%20it%20might%20be%20sufficient%20for%20them%20to%20just%20add%20your%20sending%20IP%20addresses%20or%20domain%20to%20their%20allowed%20senders%20list.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EIt's%20likely%20that%20only%20the%20recipient's%20email%20admin%20can%20fix%20the%20problem.%20Unfortunately%2C%20it's%20unlikely%20Office%20365%20Support%20will%20be%20able%20to%20help%20with%20these%20kinds%20of%20externally%20reported%20errors.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EOriginal%20Message%20Details%3C%2FSPAN%3E%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3ECreated%20Date%3A%3C%2FTD%3E%3CTD%3E10%2F2%2F2020%202%3A07%3A28%20PM%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ESender%20Address%3A%3C%2FTD%3E%3CTD%3E-%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ERecipient%20Address%3A%3C%2FTD%3E%3CTD%3E-%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ESubject%3A%3C%2FTD%3E%3CTD%3Etest%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%3EError%20Details%3C%2FSPAN%3E%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3EReported%20error%3A%3C%2FTD%3E%3CTD%3E%3CEM%3E550%205.0.350%20Remote%20server%20returned%20an%20error%20-%26gt%3B%20554%20Message%20not%20allowed%20-%20%5BPH01%5D%20Email%20not%20accepted%20for%20policy%20reasons.%20Please%20visit%20%3CA%20href%3D%22https%3A%2F%2Fpostmaster.verizonmedia.com%2Ferror-codes%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fpostmaster.verizonmedia.com%2Ferror-codes%3C%2FA%3E%3C%2FEM%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EDSN%20generated%20by%3A%3C%2FTD%3E%3CTD%3EBL0PR14MB3617.namprd14.prod.outlook.com%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3ERemote%20server%3A%3C%2FTD%3E%3CTD%3Emtaproxy225.aol.mail.ne1.yahoo.com%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1804707%22%20slang%3D%22en-US%22%3ERe%3A%20AOL%20and%20YAHOO%20emails%20undeliverable%20from%20Office365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1804707%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F817899%22%20target%3D%22_blank%22%3E%40peterlVD%3C%2FA%3E%26nbsp%3BI%20have%20two%20clients%20who%20have%20been%20getting%20these%20over%20the%20last%20few%20days.%20from%20Yahoo%20and%20AOL%20email%20accounts.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20error%20reported%20in%20both%20of%20their%20cases%20has%20been%3A%3C%2FP%3E%3CP%3E%22237%20temporarily%20deferred%20due%20to%20unexpected%20volume%20or%20user%20complaints%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20also%20refers%20to%20a%20link%3A%20%3CA%20href%3D%22https%3A%2F%2Fpostmaster.verizonmedia.com%2Ferror-codes%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpostmaster.verizonmedia.com%2Ferror-codes%3C%2FA%3E%3C%2FP%3E%3CP%3EOn%20this%20site%2C%20you%20can%20get%20some%20good%20information%20and%20also%20this%20link%20in%20order%20to%20set%20up%20a%20CFL(Complaint%20Feedback%20Loop)%20request%20for%20your%20domain%20which%20will%20allow%20you%20to%20get%20notifications%20when%20your%20domain's%20emails%20get%20flagged%20as%20spam.%26nbsp%3B%3C%2FP%3E%3CP%3EYahoo%20CFL%20request%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fio.help.yahoo.com%2Fcontact%2Findex%3Fpage%3Dcontactform%26amp%3Blocale%3Den_US%26amp%3Btoken%3DZh%2FBBVqXzLHlIbokbUqVWTUbuuQeXGkGnZzhKR2JQ4O6mMQdy9JSWdtWFXvjthcYCRj9bUIFfycOfG%2B4GOHPHoOGa8HwDO2%2B0kYRtTcdR8Nja5P9HWkKh3VWfS3pyu4UdjhvwG%2BBCvnYFl5dToDK%2Fw%3D%3D%26amp%3BselectedChannel%3Demail-icon%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EYahoo!%20Help%20-%20Submit%20a%20Form%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%20the%20CFL%20setup%20will%20send%20an%20authentication%20code%20to%20%22Postmaster%40%22%20for%20the%20domain%20you%20are%20requesting%20the%20CFL%20for%20so%20have%20that%20configured%20prior%20to%20attempting%20to%20submit%20this%20form.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

sending to aol & yahoo are kicking back. Anyone else getting this issue?

 

this is the message:

our message to - couldn't be delivered.
When Office 365 tried to send your message, the receiving email server outside Office 365 reported an error.

How to Fix It
Check the "Reported Error" from the "Error Details" section shown below for more information about the problem. The error might tell you what went wrong and how to fix it. For example, if the error states that the message was blocked due to a potential virus or because the message was too large, try sending the message again without attachments.
If you're not able to fix the problem, it's likely that only the recipient's email admin can fix it. Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin about the problem. Give them the "Reported Error" from the "Error Details" section below.


Was this helpful? Send feedback to Microsoft.



More Info for Email AdminsStatus code: 550 5.0.350 

The error reported by the receiving server wasn't specific enough to determine the exact nature of the problem. These errors often indicate the message violates a security or policy setting configured on the recipient's email servers.

If the sender is unable to fix the problem by modifying their message, then it's likely a problem that only the recipient's email admin can fix. Try the following:

Check the error for information about the problem - The "Reported Error" returned by the external email server can be found in the "Error Details" section below. This error might tell you what went wrong and provide clues for how to fix it. For example, if the error states the message was rejected due a Sender Policy Framework (SPF) issue, then you'll have to work with your domain registrar to correctly configure your domain's SPF records.

Check the error for information about where the problem is happening - For example, look for a domain name like contoso.com. A domain name in the error might suggest who is responsible for the error. It could be the recipient's email server, or it could be a third-party service that your organization or the recipient's organization is using to process or filter email messages.

If you can't fix the problem, contact the responsible party's email admin - Give them the error code and error message from this non-delivery report (NDR) to help them troubleshoot the issue. For security or policy violation issues, it might be sufficient for them to just add your sending IP addresses or domain to their allowed senders list.

It's likely that only the recipient's email admin can fix the problem. Unfortunately, it's unlikely Office 365 Support will be able to help with these kinds of externally reported errors.

Original Message Details

Created Date:10/2/2020 2:07:28 PM
Sender Address:-
Recipient Address:-
Subject:test


Error Details

Reported error:550 5.0.350 Remote server returned an error -> 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit https://postmaster.verizonmedia.com/error-codes
DSN generated by:BL0PR14MB3617.namprd14.prod.outlook.com
Remote server:mtaproxy225.aol.mail.ne1.yahoo.com
1 Reply

@peterlVD I have two clients who have been getting these over the last few days. from Yahoo and AOL email accounts. 

The error reported in both of their cases has been:

"237 temporarily deferred due to unexpected volume or user complaints"

 

It also refers to a link: https://postmaster.verizonmedia.com/error-codes

On this site, you can get some good information and also this link in order to set up a CFL(Complaint Feedback Loop) request for your domain which will allow you to get notifications when your domain's emails get flagged as spam. 

Yahoo CFL request: Yahoo! Help - Submit a Form

 

Note: the CFL setup will send an authentication code to "Postmaster@" for the domain you are requesting the CFL for so have that configured prior to attempting to submit this form.