Re: NDR delivery delayed errors keep coming, any advice?

Les,

Thanks for the response. I will try your suggestions. Since I sent this
note this morning, I have had another user tell me they are getting the same
issue. This is sending to some of the free e-mails out there, i.e. yahoo,
msn, hotmail. All e-mails from my Exchange server to yahoo seem to be going
into junk/bulk mail in the recipient's folder. I don't think I have any
control over that, do I? When I send to my personal gmail account and back,
no issues.

I will post after I have tried what you suggested. I've got to get this
fixed!

Mike


"Les Connor [SBS MVP]" wrote:

Hi Mike,

You need to determine whether the entire recipient domain is affected, or
only certain users you send to at that domain. Here are a few
troubleshooting steps you can take.

Check your exchange queues, and see if you can determine the reason why the
emails are queued.
Use this kb article to send an email via command line to see if it succeeds:

153119 XFOR: Telnet to Port 25 to Test SMTP Communication
http://support.microsoft.com/?id=153119

You can also turn up logging in Exchange, to view the SMTP conversation:

In Exchange System Manager, right click your Server object and select
properties.
On the Diagnostics Logging tab, click on MSExchangeTransport, and SMTP
Protocol, and set logging to maximum.
Expand Protocols, SMTP, default SMTP VS properties, and on the general tab
enable logging.


--
Les Connor [SBS MVP]


"Mike" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7890A798-E082-4A06-9103-7D92078A4EF1@xxxxxxxxxxxxxxxx
Hi folks,

I am getting more of these messages:

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@xxxxxxxxxx

The following recipient(s) could not be reached:

user@xxxxxxxxxx on 9/16/2007 9:54 AM
Could not deliver the message in the time limit specified.
Please retry or contact your administrator.
<domain.com #4.4.7>

googling and searching MS only leads me to believe that the problem is on
the receiver's end, but we weren't getting these errors before we moved to
Exchange four weeks ago, so does that make sense?
Is there a way to suppress my users getting these bounce messages? Any
settings I should check on my end?

How would you debug this? Should I simply contact the receiver's end, try
to find someone doing their IT work and see if they can tell me what's
going
on?

Just looking for advice..

Mike



.

Relevant Pages

  • Re: NDR delivery delayed errors keep coming, any advice?
    ... I tried to send a note to my home account via the telnet commands ... But that in no way afffects mail delivery, ... All e-mails from my Exchange server to yahoo seem to be ... Telnet to Port 25 to Test SMTP Communication ...
    (microsoft.public.windows.server.sbs)
  • Re: NDR delivery delayed errors keep coming, any advice?
    ... Generally, your ISPs mail server may be more 'trusted' than yours, so handing off mail this way for delivery can circumvent some delivery issues. ... But let's be clear here - if your email *are* arriving at the destination servers, but getting junked - then SMTP is working fine and smarthost may not change a thing. ... All e-mails from my Exchange server to yahoo seem to be ...
    (microsoft.public.windows.server.sbs)
  • Re: NDR delivery delayed errors keep coming, any advice?
    ... Unless you've got a complete set of DNS records, including reverse MX and SPF, you may have trouble sending via DNS to some domains. ... Check your exchange queues, and see if you can determine the reason why the ... Telnet to Port 25 to Test SMTP Communication ... On the Diagnostics Logging tab, click on MSExchangeTransport, and SMTP ...
    (microsoft.public.windows.server.sbs)
  • Re: POP3 Connector : Lost messages
    ... The mapping from the FAI email and Exchange is ok ... The way that mail is delivered to servers usually is by SMTP. ... servers deliver to POP mailboxes, and the POP mailboxes strip out all ... switch your mail to SMTP delivery if you can. ...
    (microsoft.public.windows.server.sbs)
  • RE: delivery restrictions and foreward to external address
    ... I've a problem with the restriction I setted up in my smtp connector and the ... foreward field in user's AD properties (exchange general->delivery options). ... exch full started and clients still in pop3/smtp ... I suppose the problem is due to the delivery restriction on my smtp ...
    (microsoft.public.exchange.admin)