cvs2svn
b7ce19d71a
Sprout from bmsi 2005-05-31 18:23:49 UTC Stuart Gathman <stuart@gathman.org> 'Development changes since 0.7.2' Cherrypick from master 2005-07-20 14:56:38 UTC Stuart Gathman <stuart@gathman.org> 'Handle corrupt ZIP attachments': COPYING CREDITS MANIFEST.in Milter/__init__.py Milter/dsn.py Milter/dynip.py NEWS TODO bms.py faq.html milter.cfg milter.html milter.spec miltermodule.c mime.py setup.cfg setup.py softfail.txt spf.py spfquery.py strike3.txt test/zip1 test/zip2 test/zip3 test/ziploop testmime.py
67 lines
2.4 KiB
Plaintext
67 lines
2.4 KiB
Plaintext
Subject: Critical mail server configuration error
|
|
|
|
This is an automatically generated Delivery Status Notification.
|
|
|
|
THIS IS A WARNING MESSAGE ONLY.
|
|
|
|
YOU DO *NOT* NEED TO RESEND YOUR MESSAGE.
|
|
|
|
Delivery to the following recipients has been delayed.
|
|
|
|
%(rcpt)s
|
|
|
|
Subject: %(subject)s
|
|
|
|
Someone at IP address %(connectip)s sent an email claiming
|
|
to be from %(sender)s.
|
|
|
|
If that wasn't you, then your domain, %(sender_domain)s,
|
|
was forged - i.e. used without your knowlege or authorization by
|
|
someone attempting to steal your mail identity. This is a very
|
|
serious problem, and you need to provide authentication for your
|
|
SMTP (email) servers to prevent criminals from forging your
|
|
domain. The simplest step is usually to publish an SPF record
|
|
with your Sender Policy.
|
|
|
|
For more information, see: http://openspf.com
|
|
|
|
I hate to annoy you with a DSN (Delivery Status
|
|
Notification) from a possibly forged email, but since you
|
|
have not published a sender policy, there is no other way
|
|
of bringing this to your attention.
|
|
|
|
If it *was* you that sent the email, then your email domain
|
|
or configuration is in error. If you don't know anything
|
|
about mail servers, then pass this on to your SMTP (mail)
|
|
server administrator. We have accepted the email anyway, in
|
|
case it is important, but we couldn't find anything about
|
|
the mail submitter at %(connectip)s to distinguish it from a
|
|
zombie (compromised/infected computer - usually a Windows
|
|
PC). There was no PTR record for its IP address (PTR names
|
|
that contain the IP address don't count). RFC2821 requires
|
|
that your hello name be a FQN (Fully Qualified domain Name,
|
|
i.e. at least one dot) that resolves to the IP address of
|
|
the mail sender. In addition, just like for PTR, we don't
|
|
accept a helo name that contains the IP, since this doesn't
|
|
help to identify you. The hello name you used,
|
|
%(heloname)s, was invalid.
|
|
|
|
Furthermore, there was no SPF record for the sending domain
|
|
%(sender_domain)s. We even tried to find its IP in any A or
|
|
MX records for your domain, but that failed also. We really
|
|
should reject mail from anonymous mail clients, but in case
|
|
it is important, we are accepting it anyway.
|
|
|
|
We are sending you this message to alert you to the fact that
|
|
|
|
Either - Someone is forging your domain.
|
|
Or - You have problems with your email configuration.
|
|
Or - Possibly both.
|
|
|
|
If you need further assistance, please do not hesitate to
|
|
contact me again.
|
|
|
|
Kind regards,
|
|
|
|
postmaster@%(receiver)s
|