Email bounce back 550 5.1.1 recipient rejected

Question

My data model object will support both XML and JSON. Now I am able to get JSON (Accept: application/json) object but for XML (Accept: application/xml) getting below exception: Example: [com.sun.istack.internal.SAXException2: A cycle is detected in the object graph. This will cause infinitely deep XML: ....

I have fixed the recursive loop for JSON fixed by using @JsonIdentityInfo. But how to fix for XML. ? My data model classes are:

Enterprise Class:

@Entity
@Table(name = "enterprise")
@XmlAccessorType(XmlAccessType.FIELD)
@XmlRootElement
@JsonIdentityInfo(generator = ObjectIdGenerators.PropertyGenerator.class, 
property = "enterpriseId", scope = Enterprise.class)
public class Enterprise extends BaseEntity implements Serializable {
//setters and getter for properties
}

Organization Class:

@Entity
@Table(name = "organization")
@XmlAccessorType(XmlAccessType.FIELD)
@XmlRootElement
@JsonIdentityInfo(generator = ObjectIdGenerators.PropertyGenerator.class, 
property = "organizationId", scope = Organization.class)
public class Organization extends BaseEntity implements Serializable {
//setters and getter for properties
}

Can anyone please help me to resolve this ? Thanks.

Solution 1

550 5.1.1 means that the recipient email server believes that the email address does not exist at the destination domain, and therefore has no way to deliver it.

Unless you simply made a typo in the email address, this is not something that you can fix, and must be addressed at the other end.

Solution 2

Tell the IT guy to add the following records to their domain DNS Zone file supposing that their domain is client.org:

A record

Host: mail

Points to: [put here the ip address of client.org without brakets]

MX record

Priority: 0

Host: @

Points To: mail.client.org

Solution 3

A Spam filter may also be the cause if emails are passing through it and the email address is not registered on it as yet

Comments

[Admin]

Of course you're not being blocked because the NDR states "recipient rejected", not "sender rejected". I can think of a few things that might be wrong (on the recipient's end): 1. The recipient's server isn't authoritative for the domain you're sending to. 2. The recipient doesn't have the email address that you're sending to. 3. Some other configuration error on the recipient's end.

[Admin]

Did the MX record change for your client? I've seen similar errors (although User Unknown errors) where the sender had stale DNS records and was attempting to resolve their MX to an IP that no longer hosted it. If this is the case that would mean that your DNS records are stale and need to be refreshed.

[Admin]

@Stan - That sounds about right. If you're replying to an email then the recipient email address should be OK. It may be a problem with DNS (the MX record) as DKNUCKLES stated or it may be a problem with the Exchange configuration. If the Accepted Domains in Exchange is incorrectly configured then internal to internal email would work but external to internal email would not.

[Admin]

simple-talk.com/sysadmin/exchange/… Please refer the above link...This helped me to resolve the issue..

[Jenny D]

It may also be rejected for policy reasons, e.g. because the server is configured to not accept mail for that combination of sender and recipient addresses.

[Michael Hampton]

@JennyD If that's the case, then the mail server is blatantly lying about the rejection reason. Which isn't helpful to anyone.

[Jenny D]

RFC5321 §7.9 "When mail is rejected for these or other policy reasons, a 550 code SHOULD be used in response to EHLO (or HELO), MAIL, or RCPT as appropriate." I'll agree that it's not helpful, though.

[Michael Hampton]

@JennyD Wrong RFC. This is an RFC 3463 extended status code. Where, 5.1.1 means "user doesn't exist" and 5.7.1 means "I don't want your junk, go away".

[Jenny D]

You make me very happy that I'm not longer having email systems as a major part of my job.

[ScottC]

I'm curious why this is down voted? It would be nice to have an explanation along with the -2 so we know why this isn't valid. I came here because I got the 550 5.1.1 (user unknown in the relay table) which kind of sounds like its possible an intermediary server is rejecting the message. It's possible that its the users exchange server too, but with no explanation the down votes are very unhelpful.