RE: Slow mail flow...no mail flow...

  • From: "Marvin Cummings" <marvc@xxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Sun, 14 Mar 2004 12:41:49 -0500

Sorry for the delay but I can't seem to do an nslookup to anything on the
outside. Anytime I try to get my public IP. I can telnet to my mail server
mail.nusolutions.biz but that's it. 

 

Thanks 

 

  _____  

From: Chris Wall [mailto:Chris.Wall@xxxxxxxxxxxxxxxxxxx] 
Sent: Saturday, March 13, 2004 8:23 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Slow mail flow...no mail flow...

 

http://www.MSExchange.org/

From your primary SMTP server that sends your mail, do an NSLookup on one of
the domains that your mail is failing to.

 

Get the MX Records from the domains and tell us if you can telnet to them
(from your SMTP) server.

 

These errors tell me that your mail is not finding the domain and is not
leaving your server.  This could be a DNS issue.  If you can do an NSLookup
on one of the domains and resolve the MX Records, this will eliminate that
theory.


Chris

 

  _____  

From: Marvin Cummings [mailto:marvc@xxxxxxxxxxxxx] 
Sent: Saturday, March 13, 2004 8:18 AM
To: [ExchangeList]
Subject: [exchangelist] Slow mail flow...no mail flow...

 

http://www.MSExchange.org/

Is there anyone monitoring the list today who can help me figure out what's
wrong with my exchange setup? I'm running exchange 2003 on my home DSL
connection using the TZO dynamic service behind a linksys router and I find
that I can receive some mail but cannot send without it being rejected. I
usually end up getting one of the two messages below: 

 

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.

 

       user@xxxxxxxxxxxxx

 

or 

 

Your message did not reach some or all of the intended recipients.

 

      Subject:             Test

      Sent:                 2/23/2004 4:17 PM

 

The following recipient(s) could not be reached:

 

      user@xxxxxxxxxxx on 2/25/2004 4:31 PM

            Could not deliver the message in the time limit specified.
Please retry or contact your administrator.

            <mail.nusolutions.biz #4.4.7>

 

 

 Is this just a curse of DLS or is there something I can do to prevent this?
I'd appreciate any response in regards to this.

 

Thanks

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------ 

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------ 

Other related posts: