Search the Archives

RFC 1123: Ref. to RFC 1123 sec 5.2.5Please consider allowing a...

Reader comments:

Comment by Max Davis
Submitted on 2/19/2004
Related RFC: RFC 1123
Rating: Not yet rated	Rate this comment:
Ref. to RFC 1123 sec 5.2.5Please consider allowing a receiving SMTP MTA to refuse to accept a message based on the fact that the sending host IP number dose not match the HELO domain (FQDN) DNS "A" record of the name given.The sending host IP number is required to have a DNS PTR record (FQDN) and the HELO/EHELO domain name give is required to be the FQDN of the sending host. Therefore this should be an OPTION of the receiving SMTP MTA to refuse acceptance of a message at the SMTP level.Approximately one half (1500 to 2000) of the SPAM received daily on my network will have a PTR record for the connecting Host IP number (some DSL circuit) and the HELO/EHELO domain will be forged FQDN (ex. something.AOL.com, ect.) but the connection host IP number WILL NOT match the DNS “A” record of the HELO/EHELO domain and will be obliviously different networks.I believe that allowing receiving MTA to refuse messages base on this check will do the following:1. Reduce a significant amount of SPAM on the Internet and will force SPAMers into the open.2. Will insure the traceblity of messages by insuring the sending SMTP host is who it says it is.3. Easily reduce a significant amount of SPAM at the receiving SMTP MTA at the SMTP connection without further loading the MTS’s host with filtering software.Sincerely,Max Davis edavis@CairoNet.comOnLine

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 1123