> > Your only option is to turn off BOFHCHECKDNS, which turns off ALL dns > checking, letting in all sorts of crap. > > It's much better to tell the sender to fix their dns. >
Okay, I'll do that. In this case, the DNS hosting firm is local, so I should be able to do this. I'm curious, though -- and I'm sure this has been hashed out before -- what is the problem with having a raw IP address in an MX record? I understand it's a technical violation of RFC 1035, but I've never been able to fathom just what vulnerability it opens up or other problem it causes. My ignorance here makes it hard to convince other firms just why they should "fix" their DNS. The response typically is "Okay, it's a technical violation. So what?" Regards, Carey ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
