550 550 5.7.1 Requested action not taken: message refused (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Message Routing



Message


Need help -> 550 550 5.7.1 Requested action not taken: message refused (8.Jun.2009 3:33:40 PM)

Hi All,

I was hoping for some advice on how to go about and fix this error that a person is getting when sending to one of my users:

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    user@domain.us

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.7.1 Requested action not taken: message refused (state 18).


I also have a Mail backup hop with a cost of 20. As of now, this is the only user in my environment that is having the problem with random senders sending him emails. All other email is flowing to and from my server with no problems.

Any help is much appreciated,

Need Help :)




ravisha_22 -> RE: 550 550 5.7.1 Requested action not taken: message refused (8.Jun.2009 11:09:23 PM)

Need more info on whether there are any SPAM agents installed and confiugred. What does the conversation look like in SMTP protocol log?

Is it happening randomly for google or is it consistent?




Need help -> RE: 550 550 5.7.1 Requested action not taken: message refused (9.Jun.2009 4:33:19 PM)

IMF might be in use, but I doubt it. If I go into EMS, global, delivery settings, there is no IMF tab. (I'm running Exchange 2003 SP2) The SMTP log looks clean, but I'm not sure. Is there a specific detail that I can look for?




Need help -> RE: 550 550 5.7.1 Requested action not taken: message refused (9.Jun.2009 4:54:45 PM)

Here is a new NDR that the another sender gets when sending to my user:

The following message to <user@domain.us> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'5.7.1 Requested action not taken: message refused'
Reporting-MTA: dns; smtp06.bis.na.blackberry.com

Final-Recipient: rfc822;user@domain.us
Action: failed
Status: 5.0.0 (permanent failure)
Remote-MTA: dns; [76.79.171.45]
Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'5.7.1 Requested action not taken: message refused' (delivery attempts: 0)

And it appears to only happen to this user and in addition, when he sends an email to the person trying to send him and that person replies, it gets through with no problem.




ravisha_22 -> RE: 550 550 5.7.1 Requested action not taken: message refused (9.Jun.2009 10:02:45 PM)

Is there any server that sits between the Exchange environment and internet?

And when i mentioned about SMTP protocol log i meant about the specific conversation when the message is rejected.

Also the problem looks to be on with the server that receivs message from internet, as the NDR is being generated by the servers attempting to connect to it.




Need help -> RE: 550 550 5.7.1 Requested action not taken: message refused (10.Jun.2009 6:12:53 PM)

Outgoing,there is no server.
Incoming, we have a Mail Backup Hop services handled by DynDNS

Again, the problem is a friend sending to my user. I posted the bounce back the friend gets.

I feel the problem is on the 'friends' end since he got the NDR. However, I'm making sure it's not on my end.

In addition, I have 2 more users that are telling me that individuals sending my users emails are getting bounce backs. It's sporadic though.




ravisha_22 -> RE: 550 550 5.7.1 Requested action not taken: message refused (10.Jun.2009 9:16:40 PM)

If the mails are not being received by Exchange directly, then i suggest having a look at the the system/application that does, as in most of the cases, it could be a un-updated local database used by the app to ward off spam.




Need help -> RE: 550 550 5.7.1 Requested action not taken: message refused (16.Jun.2009 1:14:30 PM)

I have a question submitted to our Mail HOP backup provider. I'm now convinced that there service needs to be 'tweaked'. The problem started happening ever since we started using them.

I hope that is all to it.




Page: [1]