Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Email Security Quick-links: ESA Product Support | SMA Product Support | Email Submission and Tracking Portal | Cisco SecurityHub
Current General Deployment (GD) Releases:
ESA: 11.0.0-264 WSA: 10.5.1-296 SMA: 11.0.0-115 Email Plug-in (Reporting): 1.0.1-048 Email Plug-in (Encryption): 1.0.0-036

New Member

Reason: 5.3.0 - Other mail system problem ('542'

Hello,

 

I have one Ironport C370 and when I send a message to an address I have this response

bounced by destination server. Reason: 5.3.0 - Other mail system problem ('542', ['5.7.1 Spiked: templates/60cde3022cf2c937.1.0.419.2522.2820.07090306040200..1/10'])

 
 
this recipient correctly receives these emails.

By performing tests still to the same destination but with a different address from our area I saw it functioned.
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

You would need to check

You would need to check directly with the recipient end as to why they are denying your connection.

5.3.0 --->

Mail system status

       X.3.0   Other or undefined mail system status

          The destination system exists and normally accepts mail, but
          something about the system has caused the generation of this
          DSN.

The '542' = Bad Connection

5.7.1 always means there is a permanent failure of "Delivery not authorized, message refused"

 

5.7.1   Delivery not authorized, message refused

          The sender is not authorized to send to the destination.
          This can be the result of per-host or per-recipient
          filtering.  This memo does not discuss the merits of any
          such filtering, but provides a mechanism to report such.
          This is useful only as a permanent error.

 

Hope this helps!

-Robert

 

(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

2 REPLIES
Cisco Employee

You would need to check

You would need to check directly with the recipient end as to why they are denying your connection.

5.3.0 --->

Mail system status

       X.3.0   Other or undefined mail system status

          The destination system exists and normally accepts mail, but
          something about the system has caused the generation of this
          DSN.

The '542' = Bad Connection

5.7.1 always means there is a permanent failure of "Delivery not authorized, message refused"

 

5.7.1   Delivery not authorized, message refused

          The sender is not authorized to send to the destination.
          This can be the result of per-host or per-recipient
          filtering.  This memo does not discuss the merits of any
          such filtering, but provides a mechanism to report such.
          This is useful only as a permanent error.

 

Hope this helps!

-Robert

 

(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

New Member

Thank you for your help. the

Thank you for your help. the problem actually came from distand server refused our message. the problem is resolut. is there a document that allows referencer the error code ironport?

4369
Views
0
Helpful
2
Replies