Home All Groups Group Topic Archive Search About
Author
26 Sep 2007 4:40 PM
Bruce D
Can't figure this one out.

This is an SBS 2003 R2 server with 14 users that has been running for about
6 weeks.  All of the users, frequently but irregularly (several times a day),
get DELAY messages, and then UNDELIVERABLE messages.  The undeliverable
messages are similar to the following:

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

      Subject:    <subject>
      Sent:    9/6/2007 10:57 AM

The following recipient(s) could not be reached:

      <recipient_name>@verizon.net on 9/8/2007 10:58 AM
            Could not deliver the message in the time limit specified. 
Please retry or contact your administrator.
            <<sender's_domain_name> #4.4.7>

Verizon is not the only receiving domain name to do this, but it's certainly
the most frequent. Not all messages bound for Verizon fail, nor is it
specific to certain users or recipients.

Any ideas?  'Cause I'm out of them.  Thanks!

Author
26 Sep 2007 6:08 PM
Michael Dragone
What kind of connectivity to the Internet is in place (DSL, cable modem, T1,
etc.)?
If it's a DSL connection or cable modem, which ISP (many, if not all, will
block outbound port 25 to everywhere except their own mail servers in which
case you'd need to rerun the CEICW and set up a smarthost)?

Can you telnet to port 25 on the receiving mail server and connect
successfully? See http://support.microsoft.com/kb/153119 for instructions on
how to do so.

Finally, have you had this problem for all 6 weeks since the server has been
installed?

Show quote
"Bruce D" <Bru***@discussions.microsoft.com> wrote in message
news:5D11D613-43C9-49FB-B676-5EBFA50921EC@microsoft.com...
> Can't figure this one out.
>
> This is an SBS 2003 R2 server with 14 users that has been running for
> about
> 6 weeks.  All of the users, frequently but irregularly (several times a
> day),
> get DELAY messages, and then UNDELIVERABLE messages.  The undeliverable
> messages are similar to the following:
>
> Your message did not reach some or all of the intended recipients.
>
>      Subject: <subject>
>      Sent: 9/6/2007 10:57 AM
>
> The following recipient(s) could not be reached:
>
>      <recipient_name>@verizon.net on 9/8/2007 10:58 AM
>            Could not deliver the message in the time limit specified.
> Please retry or contact your administrator.
>            <<sender's_domain_name> #4.4.7>
>
> Verizon is not the only receiving domain name to do this, but it's
> certainly
> the most frequent. Not all messages bound for Verizon fail, nor is it
> specific to certain users or recipients.
>
> Any ideas?  'Cause I'm out of them.  Thanks!
Author
26 Sep 2007 8:20 PM
Bruce D
Verizon is the ISP. It's allegedly "Business Class DSL", meaning they charge
more BUT they also allow us to run our own email/http/etc servers.  Further,
as far as I know, they do not provide a smart host for relaying.

Thank you for the suggestion about telnetting; I hadn't thought of that. I
can telnet to some of the hosts - that is, those where I actually know the
name of the mail server. ( I can connect, but not successfully send.)  I have
not been able to find the exact mail server name for either Verizon or Yahoo,
si don't know what the deal is with those two.

And yes, this problem has been going on for the entire six weeks.  I should
note also that this is a replacement server for an older SBS 2000 box. The
2000 box did NOT have these issues.

Thanks again!





Show quote
"Michael Dragone" wrote:

> What kind of connectivity to the Internet is in place (DSL, cable modem, T1,
> etc.)?
> If it's a DSL connection or cable modem, which ISP (many, if not all, will
> block outbound port 25 to everywhere except their own mail servers in which
> case you'd need to rerun the CEICW and set up a smarthost)?
>
> Can you telnet to port 25 on the receiving mail server and connect
> successfully? See http://support.microsoft.com/kb/153119 for instructions on
> how to do so.
>
> Finally, have you had this problem for all 6 weeks since the server has been
> installed?
>
> "Bruce D" <Bru***@discussions.microsoft.com> wrote in message
> news:5D11D613-43C9-49FB-B676-5EBFA50921EC@microsoft.com...
> > Can't figure this one out.
> >
> > This is an SBS 2003 R2 server with 14 users that has been running for
> > about
> > 6 weeks.  All of the users, frequently but irregularly (several times a
> > day),
> > get DELAY messages, and then UNDELIVERABLE messages.  The undeliverable
> > messages are similar to the following:
> >
> > Your message did not reach some or all of the intended recipients.
> >
> >      Subject: <subject>
> >      Sent: 9/6/2007 10:57 AM
> >
> > The following recipient(s) could not be reached:
> >
> >      <recipient_name>@verizon.net on 9/8/2007 10:58 AM
> >            Could not deliver the message in the time limit specified.
> > Please retry or contact your administrator.
> >            <<sender's_domain_name> #4.4.7>
> >
> > Verizon is not the only receiving domain name to do this, but it's
> > certainly
> > the most frequent. Not all messages bound for Verizon fail, nor is it
> > specific to certain users or recipients.
> >
> > Any ideas?  'Cause I'm out of them.  Thanks!
>
Author
27 Sep 2007 6:09 PM
Michael Dragone
You can do an nslookup for the MX record(s) of the destination mail
server(s) and telnet to those.

Any errors in the event log?

Show quote
"Bruce D" <Bru***@discussions.microsoft.com> wrote in message
news:F0AF1530-B415-4D4C-82BD-71E4D2162050@microsoft.com...
> Verizon is the ISP. It's allegedly "Business Class DSL", meaning they
> charge
> more BUT they also allow us to run our own email/http/etc servers.
> Further,
> as far as I know, they do not provide a smart host for relaying.
>
> Thank you for the suggestion about telnetting; I hadn't thought of that. I
> can telnet to some of the hosts - that is, those where I actually know the
> name of the mail server. ( I can connect, but not successfully send.)  I
> have
> not been able to find the exact mail server name for either Verizon or
> Yahoo,
> si don't know what the deal is with those two.
>
> And yes, this problem has been going on for the entire six weeks.  I
> should
> note also that this is a replacement server for an older SBS 2000 box. The
> 2000 box did NOT have these issues.
>
> Thanks again!
>
>
>
>
>
> "Michael Dragone" wrote:
>
>> What kind of connectivity to the Internet is in place (DSL, cable modem,
>> T1,
>> etc.)?
>> If it's a DSL connection or cable modem, which ISP (many, if not all,
>> will
>> block outbound port 25 to everywhere except their own mail servers in
>> which
>> case you'd need to rerun the CEICW and set up a smarthost)?
>>
>> Can you telnet to port 25 on the receiving mail server and connect
>> successfully? See http://support.microsoft.com/kb/153119 for instructions
>> on
>> how to do so.
>>
>> Finally, have you had this problem for all 6 weeks since the server has
>> been
>> installed?
>>
>> "Bruce D" <Bru***@discussions.microsoft.com> wrote in message
>> news:5D11D613-43C9-49FB-B676-5EBFA50921EC@microsoft.com...
>> > Can't figure this one out.
>> >
>> > This is an SBS 2003 R2 server with 14 users that has been running for
>> > about
>> > 6 weeks.  All of the users, frequently but irregularly (several times a
>> > day),
>> > get DELAY messages, and then UNDELIVERABLE messages.  The undeliverable
>> > messages are similar to the following:
>> >
>> > Your message did not reach some or all of the intended recipients.
>> >
>> >      Subject: <subject>
>> >      Sent: 9/6/2007 10:57 AM
>> >
>> > The following recipient(s) could not be reached:
>> >
>> >      <recipient_name>@verizon.net on 9/8/2007 10:58 AM
>> >            Could not deliver the message in the time limit specified.
>> > Please retry or contact your administrator.
>> >            <<sender's_domain_name> #4.4.7>
>> >
>> > Verizon is not the only receiving domain name to do this, but it's
>> > certainly
>> > the most frequent. Not all messages bound for Verizon fail, nor is it
>> > specific to certain users or recipients.
>> >
>> > Any ideas?  'Cause I'm out of them.  Thanks!
>>

AddThis Social Bookmark Button