>Alessandro Vesely wrote: >> For example, Lucio's server could have matched the bad MX 20 >> of domain.com, unable to recognize its own IP address because it sits >> behind a NAT, and unable to recognize its own name since the DNS hid >> it. If it had used the good MX record by default, it would have >> violated the SMTP prohibition to relay to a host at the same >> preference level.
On 26.06.12 23:16, Lucio Crusca wrote: >I don't quite get why (and it's crucial I understand it before I tell the >other domain tech contact it's his fault). Pointing the MX to an IP address _IS_ his fault. MX points to a domain name and IP address is _not_ a domain name. RFC 1035, section 3.3.9. I don't see any reason why you should not contact/blame domain admin when the MX is clearly broken -- Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. BSE = Mad Cow Desease ... BSA = Mad Software Producents Desease ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
