Keith, you've got 3 things going on here: 1) RFC compliance. Maybe it's a requirement, maybe not. I think RFC compliance is a red herring. Both sides are not playing nice.
2) .local isn't a legitimate Internet domain; there are legitimate extensions recognized as being private, like .test 3) Why not just change the customer's HELO? It's a simple change, but it comes up a lot. If you're using MS SMTP to deliver the mail, go to SMTP Connector Properties, go to the Delivery tab, and click on the Advanced button. Type in the PTR name in the "Fully-qualified domain name" field. You can click on the Help button for actual honest-to-goodness help (unlike the fluff that recites the labels you've already read that is so common in help pages). Andrew 8) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith Johnson Sent: Monday, March 07, 2005 1:48 PM To: [email protected] Subject: [Declude.JunkMail] OT: RFC DNS Information Does the following break in RFC compliance issues with servers required to accept email? Customer has proper PTR Records for IP, however, domain name is a private one, i.e. customer.local Thanks for the aid. Denied Message Reads: Our mail system now 'requires' that your outgoing mail servers identify with a valid hostname. The only requirement is that it exist in DNS publicly. -Keith NfÆçëyu u×dj)jgr[xÆf)+Nrz;uj)r[yjwÊËmr[xÆ8jqyÖf+
