Access Keys:
Skip to content (Access Key - 0)
Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

554 5.7.1 Delivery not authorized

Question

I tried to send MIT email and got the following error, what does it mean?

554 5.7.1 Delivery not authorized

Answer

Our Spam filter (Symantec Brightmail) can block various messages for various reasons.

Symantec's official answer to the topic is here:
http://www.symantec.com/docs/TECH169847

Informally, one of the most common situations we've seen at the Help Desk are in cases where Reverse DNS is not configured properly. Loosely speaking, the problem is that server contacting MIT does not have its own hostname. (The loose description, is not technically correct - the correct technical question is whether there is a PTR record for the IP address.)

Diagnosing this can be difficult, because mail errors do not always give a good report of IP addresses. For best diagnosis, forward the error bounce as an attachment, do not merely forward its text.

Alternately, ask the sender to send test email to mrhalp@gmail.com, and then go to gmail.com and use "show original" to view the Received headers.

If DNS reverse-resolving is the issue, the sender or the sender's mail administrators would need to add a PTR record for the IP address of their server that is trying to contact MIT.

Example of error message

Here is an example of this kind of mail error

----- The following addresses had permanent fatal errors
-----<username@mit.edu> <username@mit.edu>
(reason: 554 5.7.1 Delivery not authorized)

----- Transcript of session follows -----
... while talking to dmz-mailsec-scanner-3.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
... while talking to dmz-mailsec-scanner-7.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
... while talking to dmz-mailsec-scanner-4.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
... while talking to dmz-mailsec-scanner-5.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
... while talking to dmz-mailsec-scanner-2.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
... while talking to dmz-mailsec-scanner-8.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
... while talking to dmz-mailsec-scanner-1.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
... while talking to dmz-mailsec-scanner-6.mit.edu.:
<<< 554 5.7.1 Delivery not authorized
554 5.0.0 Service unavailable

Reporting-MTA: dns; xxxxx.yyyyy.zzz
Received-From-MTA: DNS; www.xxxxx.yyyyy.zzz
Arrival-Date: Thu, 2 Feb 2012 14:01:15 -0500 (EST)

Final-Recipient: RFC822; username@mit.edu
Action: failed
Status: 5.5.0
Diagnostic-Code: SMTP; 554 5.7.1 Delivery not authorized
Last-Attempt-Date: Thu, 2 Feb 2012 14:01:16 -0500 (EST)

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Last Modified:

page-info: unable to locate page


Get Help

Request help
from the Help Desk
Report a security incident
to the Security Team
Feedback
This product/service is:
Easy to use
Average
Difficult to use

This article is:
Helpful
Inaccurate
Obsolete
Adaptavist Theme Builder (4.2.3) Powered by Atlassian Confluence 3.5.13, the Enterprise Wiki