Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am getting this message when I send an email to a corporate email address from my google-apps account:

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.4.1 Relay Access Denied (state 14).

Maybe it just means the address is bad, but if I try a definite bad email I get:

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.4.1 @.com: Recipient address rejected: Access Denied (state 14).

Can anyone suggest why the slightly different responses?

share|improve this question
    
A relay error means that the destination domain is not on the permitted relay list on the SMTP server you are sending through. Were both emails in the same domain? – Paul Oct 19 '11 at 21:09
up vote 3 down vote accepted

550 Relay Access Denied is often a catch-all response for when mail is rejected, commonly due to falling into a spam filter.

Reasons could include actual spam detection (bulk mailing, or perhaps an overzealous spam filter setting), or a misconfiguration on your Google Apps domain settings where your domain's MX records don't match what IP the server is connecting from (seems unlikely).

I would definitely mention it to the mail administrator of your corporation. You may have uncovered a configuration issue that is also preventing a bunch of other people's email from arriving properly, possibly losing your company business.

share|improve this answer

This could also happen if your exchange server happens to fill up with logs that have not truncated. If you have an application that does your back ups of Microsoft Exchange and those back ups fail then they won't truncate. Your server well essentially fill up with logs and you'll run out of Disc space and then your server will stop receiving / sending emails. Careful though- The reaction on our exchange server is not always the same some the times will allow intra-emails and other times not. Sometimes after four attempts we can send an outbound but we cannot receive an inbound or vice versa.

Thought it would be a good idea to post this incase any of you out there ends up doing with an attorney that doesn't understand how to Google these error messages in order to see if an opposing client ends up dealing with an attorney that doesn't understand how to Google these error messages prior to making inaccurate accusations that are intentionally blocking their clients emails.

I'm sure this probably happens all the time. Forinsic IT attornys are hard to come by.
I'm neither am atty or in forinsics. But I did discover the issue on our server recently.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.