Re: what controls received from address?

Thus said francis drake on Mon, 22 Feb 2016 23:09:52 +0000:

> Remote_host_said:_553_We_don't_accept_mails_from_MX_with_missing_DNS_A_or_PTR_RR

Perhaps it is because you give out strange records for your DNS:

$ dnsq any a.mx.theorb.net 104.131.146.81
255 a.mx.theorb.net:
323 bytes, 1+4+2+4 records, response, authoritative, noerror
query: 255 a.mx.theorb.net
answer: a.mx.theorb.net 86400 28 &\004\250\200\000\001\000\040\000\000\000\000\002O\040\001
answer: a.mx.theorb.net 86400 A 162.243.143.26
answer: a.mx.theorb.net 86400 PTR 1.0.0.2.f.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.8.a.4.0.6.2.ip6.arpa
answer: a.mx.theorb.net 86400 PTR 26.143.243.162.in-addr.arpa
authority: theorb.net 86400 NS a.ns.theorb.net
authority: theorb.net 86400 NS b.ns.theorb.net
additional: a.ns.theorb.net 86400 A 104.131.146.81
additional: a.ns.theorb.net 86400 28 &\004\250\200\000\001\000\040\000\000\000\000\002\005`\000
additional: b.ns.theorb.net 86400 A 162.243.143.26
additional: b.ns.theorb.net 86400 28 &\004\250\200\000\001\000\040\000\000\000\000\002O\040\000

Why are you returning PTR records for a.mx.theorb.net? Do you think that
some DNS resolver is ever going to make a query for PTR a.mx.theorb.net?

Also, there is much gluelessness  in your in-addr.arpa zone? Perhaps the
MTA that  is rejecting  your MTA  is unable  to effectively  resolve the
PTR  record for  26.143.243.162.in-addr.arpa  due to  the  number or  NS
delegations it must traverse before finally getting an answer? It may be
that there is little you can do about this if this is the case.

You really need  to contact the owner  of the MTA that  is returning the
error because only they know what impositions they are making.

553_We_don't_accept_mails_from_MX_with_missing_DNS_A_or_PTR_RR

What was  the domain  name of  the MAIL  FROM that  came from  your mail
server? Perhaps  they are  checking that  an MX  record exists  for that
address?

> (note: I'm not really sir francis drake. That is an email throw away)

Well, if we're to believe your signature, you're Mike Write. :-)

Thanks,

Andy
-- 
TAI64 timestamp: 4000000056cdcf34