Difference between revisions of "Unresolvable Domain"
(Created page with "On Hosted CanIt, you may see logs similar to this: <code>5.1.8 <email@example.com>... Domain of sender address firstname.lastname@example.org does not exist</code> Hosted CanIt ...")
Revision as of 16:42, 11 January 2017
On Hosted CanIt, you may see logs similar to this:
5.1.8 <email@example.com>... Domain of sender address firstname.lastname@example.org does not exist
Hosted CanIt always rejects messages where the domain of the envelope sender (in the example above,
pqrst.example.com lacks an A or an MX record. This policy is absolutely firm.
Why do we reject unresolvable domains?
If there is a delivery problem, the Internet standards require that a failure
notification be sent to the envelope sender (in this example,
email@example.com). If that domain does not exist, then obviously no failure notification can be sent.
How can I make this work?
Only the sender of the email can fix the problem. There are several options available:
- Make sure the domain of the envelope sender address is resolvable. That is, whatever comes after the
@sign in the sender address must have an A record, an MX record, or both.
- Use the null return path
<>as the envelope sender. This is useful for situations in which you don't care to receive failure notifications.
But won't Roaring Penguin please make an exception and allow an unresolvable domain through?