RE: [Declude.JunkMail] OT: RFC DNS Information
Hi Keith: By definition, a hostname with a private domain can not be validated by anyone outside your LAN (as it will no resolve through public DNS). When your client uses an private domain in the HELO string when contacting SMTP servers on the Internet, then those mail servers can not qualify the HELO string using the public DNS, thus it is not a 'valid' hostname in that context (because a lookup will not succeed). If your client insist on using a private domain in the HELO string, then I suggest they route their outbound traffic through their ISP's/access provider's SMTP server as a "smart host". Best Regards Andy Schmidt H&M Systems Software, Inc. 600 East Crescent Avenue, Suite 203 Upper Saddle River, NJ 07458-1846 Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 http://www.HM-Software.com/ -Original Message- From: Keith Johnson 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.localThanks 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 --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: RFC DNS Information
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: Declude.JunkMail@declude.com 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.localThanks 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+
[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.localThanks 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
