To Whom It May
Concern:
Currently the system is
blocking IP 216.133.162.187 from sending mail to certain sites under your
control. I’ll assume for a moment here that the site’s owners are using
your built-in spam filtering without fully realizing the implications of said
filters. While your tools are showing a “bogus helo”, a failed “rDNS”, and
bogus “rcpt to” command for our mail server, I must point out that the error is
in fact on your end.
To begin, I must point
to a very old, yet very simple, tool commonly found on all major computers
today: the telnet tool. If you are to type in “telnet 216.133.162.187 25”
you will get this: “220 mail.mnjtech.com Microsoft ESMTP MAIL Service, Version:
6.0.3790.1830 ready at <date and time here>”. Next type a “helo”
command and you will be greeted with “250 mail.mnjtech.com Hello [YOUR IP
HERE]”. That’s about as simple as I can make it, but it’s as clear as day
that IP 216.133.162.187 on port 25 (THE standard SMTP port) is in fact
responding as mail.mnjtech.com.
If you were to actually
look at the emails being sent from our system through IP 216.133.162.187 you
will see a fully functional reverse DNS (rDNS) for this IP. The IP
216.133.162.187 corresponds with mail.mnjtech.com and can be found using a
variety of tools, my favorite being the “host <IP>” command found on every
flavor of linux.
Now, with regards to
the “rcpt to” being off, I’d like to point out the standard headers from an
email coming from IP 216.133.162.187 show ALL of the proper information in
accordance with normal internet emailing procedures. Here is a brief
summary, edited for our use:
Return-Path:
<jjonelis@mnjtech.com>
X-Original-To:
USER@DOMAIN
Delivered-To:
USER@DOMAIN
Received:
from mail.mnjtech.com (mail.mnjtech.com
[216.133.162.187])
by INCOMING EMAIL SERVER (Postfix) with ESMTP id
A2B4D139BFE
for <USER@DOMAIN>; Fri, 15 Dec 2006 13:48:50 -0800
(PST)
Content-class:
urn:content-classes:message
MIME-Version:
1.0
Content-Type:
multipart/related;
type="multipart/alternative";
boundary="----_=_NextPart_001_01C72092.CC2CFA91"
Subject:
SUBJECT
X-MimeOLE:
Produced By Microsoft Exchange V6.5
Date:
Fri, 15 Dec 2006 15:48:43 -0600
Message-ID:
<8E4054ECFAFC834E8F5E092271D96059C0D087@MNJSERVER8.mnjtech.com>
X-MS-Has-Attach:
yes
X-MS-TNEF-Correlator:
Thread-Topic:
SUBJECT
Thread-Index:
AccgksonPErZVAaDRtGFKM5Ko+AVMQ==
From:
"
To:
<USER@DOMAIN>
Unless your spam filter
is looking at the message-ID of *@MNJSERVER8.mnjtech.com, which
besides being a bad practice to have (you’ll probably redirect a bunch of false
positives in terms of emails received), if you look at mnjserver8.mnjtech.com
you will see that it resolves to the same IP address as mail.mnjtech.com
(216.133.162.187).
I hope this concludes
any issues regarding the delisting of our mail server from your spam
filters. If you have any further questions or comments please feel free to
respond to this email and I’ll get to them as soon as I
can.
Thanks
again,
800-870-4340 ext.
8323
jjonelis@mnjtech.com
AIM:
windowsisavirus
From:
unblock@godaddy.com [mailto:unblock@godaddy.com]
Sent: Monday, December 18, 2006 11:33
AM
To:
Subject: Update [Incident ID: 1424158] -
Unblock request 216.133.162.187
| |||||||
© 2006. All
rights reserved. |