Difference between revisions of "Unresolvable Domain"

From Roaring Penguin
Jump to: navigation, search
Line 31: Line 31:
  
 
<div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div>
 
<div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div>
[[category:All]][[category:Management]]
+
[[category:All]][[category:Management]][[category:Best Practices]]

Revision as of 16:57, 11 January 2017

On Hosted CanIt, you may see logs similar to this:

5.1.8 <user@example.com>... Domain of sender address xyz@pqrst.example.com 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, xyz@pqrst.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 two options available:

  1. 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.
  2. Use the null return path <> as the envelope sender. This is useful for situations in which you don't care to receive failure notifications.

Can Roaring Penguin please make an exception?

No, sorry. It is an error to send mail from unresolvable domains and the onus is on the sender to fix the problem.

I run my own CanIt server. How can I allow unresolvable domains?

Please don't. Allowing unresolvable domains simply encourages bad Internet hygiene and substandard programming practices.

That said, if you want to ignore best current practices and allow such domains, see this Wiki page.