Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- From: jmastrom <jmastrom@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Jul 2006 07:37:02 -0700
FAIL --Connect to mail servers ERROR: I could not complete a connection to
one or more of your mailservers:
mail-queue.btitelecom.net: Timed out [Last data sent: [Did not connect]]
WARN -- Mail server host name in greeting WARNING: One or more of your
mailservers is claiming to be a host other than what it really is (the SMTP
greeting should be a 3-digit code, followed by a space or a dash, then the
host name). If your mailserver sends out E-mail using this domain in its EHLO
or HELO, your E-mail might get blocked by anti-spam software. This is also a
technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname
given in the SMTP greeting should have an A record pointing back to the same
server. Note that this one test may use a cached DNS record.
mail.denysesigns.com claims to be non-existent host
DSSERVER2.denysesigns.com:
220 DSSERVER2.denysesigns.com Microsoft ESMTP MAIL Service, Version:
6.0.3790.1830 ready at Mon, 17 Jul 2006 10:34:03 -0400
I ran that report from dnsreport.com. Above is the highlighted stuff I got
from the "mail" section.
(thanks for that site by the way! great resource!)
Should I just contact my ISP about that PTR report, or is some of this stuff
on my physical end??
Under the "Warn" area... What does that mean?? I didn't even know where to
start with that one...
"Ben Winzenz [Exchange MVP]" wrote:
Nope - relay settings don't affect outbound connections..
It would appear that RoadRunner is doing reverse DNS lookups, and you are
failing.
What you need to do is have your ISP register a PTR record for your outgoing
IP. Mostly, it's important just to have that PTR record. Some companies
(idiots) want that PTR record to match the name of your mail server as well.
It doesn't mean that what RR is doing is responsible - blocking connections
based on failed rDNS lookups is idiotic as well (in my opinon), but they are
free to do whatever they want.
Anyways, correct the missing PTR record, and see if that helps things with
RR. Going to dnsreport.com and running a report ought to point this out as
well.
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"jmastrom" <jmastrom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:75FED924-EAAA-40C4-BE6F-A76B514AC3C0@xxxxxxxxxxxxxxxx
Ben,
Telnet does not allow me to connect... This is what I get:
554-clmboh-mx-07.mgw.rr.com
554 #5.5.4 Relaying denied. IP name lookup failed for 69.15.212.122
when I parsed through the logfile, the only relevent entry (from what i
could tell)was:
2006-07-17 13:48:37 24.28.204.27 OutboundConnectionResponse SMTPSVC1
DSSERVER2 - 25 - - 554-hrndva-mx-08.mgw.rr.com 0 0 27 0 5187 SMTP - -
nothing immediately after or before that entry. I couldn't find anything
else with ...mgw.rr.com.
Is this a problem with my relay settings or something??
- Follow-Ups:
- Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- From: Ben Winzenz [Exchange MVP]
- Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- References:
- Re: NDR Outgoing mail to certain Domain (inexperienced exchange admin)
- From: Ben Winzenz [Exchange MVP]
- Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- From: Ben Winzenz [Exchange MVP]
- Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- From: Ben Winzenz [Exchange MVP]
- Re: NDR Outgoing mail to certain Domain (inexperienced exchange admin)
- Prev by Date: Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- Next by Date: Tell Outlook a default domain when using RPCoHTTP
- Previous by thread: Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- Next by thread: Re: NDR Outgoing mail to certain Domain (inexperienced exchange ad
- Index(es):
Relevant Pages
|
Loading