On Wed, Jun 4, 2008 at 10:36 AM, Jonathan Gruber <[EMAIL PROTECTED]> wrote:
> Still having the same issue with shirevalleydesign.com and mail to 
> bellsouth.net.

  Hmmm.  I just tried running some test probes against the MXes for
<bellsouth.net>.  From a "real" ISP feed, I connected no problem, and
got immediate "OK" responses to MAIL
FROM:<[EMAIL PROTECTED]>.  I tried multiple probes
against both listed MXes.

  However, from my home Comcast feed, I get a hangup before HELO, with
the message that I'm blacklisted.  It's a 550 code.  I'm not sure if
Exchange will consider that a permanent failure or not.  If not, and
you're blacklisted by them, that would explain the delay-then-failure
you're seeing.  Try turning on SMTP protocol logging to record a
transcript of the SMTP session, and see if bellsouth is rejecting you.
 If you're not familiar with SMTP protocol logging, this article
explains it pretty well:

http://www.msexchange.org/tutorials/Exchange-Server-2003-Mailflow-Part-2.html

  You may want to check the IP address your mail server will be
sending from to see if it is on any blacklists.  I like the site
http://www.mxtoolbox.com/blacklists.aspx for doing that.  FWIW, I did
run the address your list post came from (24.229.89.2) and the one
returned for mail.{shirevalleydesign,moyersconstruction,sealcoatmydrive}.com
(67.91.139.138), and both came out clean.  Valid PTR records also
exist for both.

> The other 2 domains are moyersconstruction.com and sealcoatmydrive.com .

  DNS looks good to me.  The delegation chain is valid, and I get
consistent answers from all nameservers.  I also ran ZoneCheck
(http://www.zonecheck.fr) against them and it didn't find anything
serious.  It warned that postmaster@ the domains isn't working, which
isn't good, but if BellSouth was rejecting on that they would
presumably do so all the time.  (Still, you should probably fix your
postmaster mailbox.)

> Turns out in doing some more looking, we can't access the
> web sites internally either.

  Not being able to access the web sites probably isn't good, but may
or may not be related to your mail problems.  What happens when you
try the web sites?  Name resolution fails, connection times out, HTTP
server error, something else...?

-- Ben

~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to