|
Hello. I work for $COMPANY_NAME in the
$GENERAL_LOCATION. There is a problem with:
$DOMAIN_NAME_HERE
being on the DSN blacklist of:
http://www.rfc-ignorant.org/
We and possibly many other ISPs use the DSN blacklist to make sure
that mail servers contacting us follow the minimum requirements for
the functioning of mail over the Internet by adhering to RFC 2821
(and others), which requires that a mail server accept for the
purpose of error reporting the null email address ("<>") in the MAIL
FROM: command. See
- RFC 2821
-
section 4.1.1.2 MAIL (BNF grammar)
section 6.1 Reliable Delivery and Replies by Email (para. 2)
ftp://ftp.rfc-editor.org/in-notes/rfc2821.txt
- RFC 2505
-
section 2. Recommendations 6a)
section 2.6.1. "MAIL From: <>"
ftp://ftp.rfc-editor.org/in-notes/rfc2505.txt
- RFC 1123
-
section 5.2.9 Command Syntax: RFC-821 Section 4.1.2
ftp://ftp.rfc-editor.org/in-notes/rfc1123.txt
- RFC 821 (obsoleted by RFC 2821)
-
section 4.1.2
ftp://ftp.rfc-editor.org/in-notes/rfc821.txt
Your domain "$DOMAIN_NAME_HERE" no longer accepts <>. The need
for the null address ("<>") as an error reporting tool for mail server software is VERY
important to the correct functioning of mail over the Internet. It provides legitimate
users a means of find out if mail failed to arrive at its intended destination. Blocking
this for the purpose of spam control is unacceptable, because legitimate users will never
know that mail might have been rejected because they simply mistyped the destination address,
or that a mail box is full, or no longer active, etc.
We ask if you would kindly contact those responsible for the "
$DOMAIN_NAME_HERE" mail servers or if you have the means yourselves to resolve the
issue so that "$DOMAIN_NAME_HERE" remains RFC compliant with
respect to the use of the null address ("<>").
Thank you for your time and attention in this matter,
$SIGNATURE
$Id: letter-dsn-en-US.php,v 1.6 2008-10-13 14:07:53 dredd Exp $
| 
