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.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 --- [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.
