550 5.0.350 Remote server returned an error
-
I have one domain that we send to that is giving us kickbacks and returns this error:
550 5.0.350 Remote server returned an error -> 571 Delivery not authorized, message refused
I have looked at all my stuff and sent emails to other domains with no issues.
The tech at that location said it is on my end, and of course, I said it can't be because you're domain is the only one kicking back emails.
Any ideas? The research he did said I should change my domain in exchange to Internal Relay but that doesn't make sense as we aren't sharing a domain or in a hybrid state with that domain.
-
This is recipient side. There is nothing for you to do. 500 Errors means that the issue is on their side. Ask him to whitelist you as a test. Should make it work.
-
@scottalanmiller said in 550 5.0.350 Remote server returned an error:
This is recipient side. There is nothing for you to do. 500 Errors means that the issue is on their side. Ask him to whitelist you as a test. Should make it work.
He has said he has done so.
-
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
571 Delivery not authorized, message refused
That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).
-
@dbeato said in 550 5.0.350 Remote server returned an error:
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
571 Delivery not authorized, message refused
That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).
It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.
So, just to be clear, this is 100% not on my end, correct?
-
Use this site to check your domain
-
@Dashrender said in 550 5.0.350 Remote server returned an error:
Use this site to check your domain
Looks good to me...
-
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
@dbeato said in 550 5.0.350 Remote server returned an error:
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
571 Delivery not authorized, message refused
That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).
It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.
So, just to be clear, this is 100% not on my end, correct?
Sure looks to be the case. How could this be on your end? That's not even clear to be possible.
-
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
@dbeato said in 550 5.0.350 Remote server returned an error:
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
571 Delivery not authorized, message refused
That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).
It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.
So, just to be clear, this is 100% not on my end, correct?
It shouldn't be on your end, the message is coming from the recipient's end server.
-
@dbeato said in 550 5.0.350 Remote server returned an error:
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
@dbeato said in 550 5.0.350 Remote server returned an error:
@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:
571 Delivery not authorized, message refused
That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).
It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.
So, just to be clear, this is 100% not on my end, correct?
It shouldn't be on your end, the message is coming from the recipient's end server.
Right, which means that they received it.
