|
Home > Archive > microsoft.public.exchange2000.admin > October 2002 > Urgent Help needed:user mailing not being delivered
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Urgent Help needed:user mailing not being delivered
|
|
|
| My user mails to some domain names,
especially "aol.com" are not being delivered.
There is no restriction on the "address space"
configuration page of the exchange server. Since the NDR
seems to be generated by our Exchange Server, where
should I look again.
ao
| |
|
| On the Exchange server, are you able to do an nslookup of the mx record for
the domain aol.com ? Can you paste the details in to your reply ?
On the Exchange server, if you telnet manually to the aol.com, mx server,
can you send an email manually ?
What is the full text of the NDR? Can you paste that in to your reply?
Perhaps your server is on a blacklist?
Perhaps the mails being sent are over the size limit, either on your end, or
on AOL's end?
Thanks
Rob
"ao" <oke@paramaze.com> wrote in message
news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
> My user mails to some domain names,
> especially "aol.com" are not being delivered.
>
> There is no restriction on the "address space"
> configuration page of the exchange server. Since the NDR
> seems to be generated by our Exchange Server, where
> should I look again.
>
> ao
>
| |
|
| Rob,
Here is the NDR message:
"From: System Administrator
Sent: Samstag, 31. August 2002 20:24
To: Hunt Ayele (E-mail)
Subject: Undeliverable: FW: Money for Grandma
Your message did not reach some or all of the intended
recipients.
Subject: FW: Money for Grandma
Sent: 29.08.2002 20:22
The following recipient(s) could not be reached:
Hunt Ayele (E-mail) on 31.08.2002 20:24
Could not deliver the message in the time
limit specified. Please retry or contact your
administrator.
<RONH-S01.rohner.local #4.4.7"
I will try the nslookup when I am on the server.
ao
>-----Original Message-----
>On the Exchange server, are you able to do an nslookup
of the mx record for
>the domain aol.com ? Can you paste the details in to
your reply ?
>
>On the Exchange server, if you telnet manually to the
aol.com, mx server,
>can you send an email manually ?
>
>What is the full text of the NDR? Can you paste that in
to your reply?
>
>Perhaps your server is on a blacklist?
>
>Perhaps the mails being sent are over the size limit,
either on your end, or
>on AOL's end?
>
>Thanks
>Rob
>
>"ao" <oke@paramaze.com> wrote in message
> news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
>> My user mails to some domain names,
>> especially "aol.com" are not being delivered.
>>
>> There is no restriction on the "address space"
>> configuration page of the exchange server. Since the
NDR
>> seems to be generated by our Exchange Server, where
>> should I look again.
>>
>> ao
>>
>
>
>.
>
| |
|
| And this is the your server right ? RONH-S01.rohner.local
It looks like the message has sat in the queue waiting to be delivered to
that address for over a week, and the default expiry time is about 7 days I
think.
Do you have other old messages sat in the queue ? Do you have messages
queued for any other domains?
Thanks
Rob
"ao" <oke@paramaze.com> wrote in message
news:eaea01c2582b$e97ce670$a5e
62ecf@tkmsftngxa07...
> Rob,
>
> Here is the NDR message:
>
> "From: System Administrator
> Sent: Samstag, 31. August 2002 20:24
> To: Hunt Ayele (E-mail)
> Subject: Undeliverable: FW: Money for Grandma
>
> Your message did not reach some or all of the intended
> recipients.
>
> Subject: FW: Money for Grandma
> Sent: 29.08.2002 20:22
>
> The following recipient(s) could not be reached:
>
> Hunt Ayele (E-mail) on 31.08.2002 20:24
> Could not deliver the message in the time
> limit specified. Please retry or contact your
> administrator.
> <RONH-S01.rohner.local #4.4.7"
>
> I will try the nslookup when I am on the server.
>
> ao
>
>
> >-----Original Message-----
> >On the Exchange server, are you able to do an nslookup
> of the mx record for
> >the domain aol.com ? Can you paste the details in to
> your reply ?
> >
> >On the Exchange server, if you telnet manually to the
> aol.com, mx server,
> >can you send an email manually ?
> >
> >What is the full text of the NDR? Can you paste that in
> to your reply?
> >
> >Perhaps your server is on a blacklist?
> >
> >Perhaps the mails being sent are over the size limit,
> either on your end, or
> >on AOL's end?
> >
> >Thanks
> >Rob
> >
> >"ao" <oke@paramaze.com> wrote in message
> > news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
> >> My user mails to some domain names,
> >> especially "aol.com" are not being delivered.
> >>
> >> There is no restriction on the "address space"
> >> configuration page of the exchange server. Since the
> NDR
> >> seems to be generated by our Exchange Server, where
> >> should I look again.
> >>
> >> ao
> >>
> >
> >
> >.
> >
| |
| Chad Smith, CNA, CompTIA N+ 2002-10-05, 8:21 pm |
| Is this Exchange server new to your organization? Do you have a firewall?
--
Chad Smith
Director of Information Services
Condley and Company, L.L.P.
Abilene, TX
www.condley.com
ao wrote:
> My user mails to some domain names,
> especially "aol.com" are not being delivered.
>
> There is no restriction on the "address space"
> configuration page of the exchange server. Since the NDR
> seems to be generated by our Exchange Server, where
> should I look again.
>
> ao
| |
|
| Rob,
The problem is only with aol.com address, other domain
names seem to be delivered. The NDR is actually
generated 2 days after the mail was sent by the user.
ao
>-----Original Message-----
>And this is the your server right ? RONH-
S01.rohner.local
>
>It looks like the message has sat in the queue waiting
to be delivered to
>that address for over a week, and the default expiry
time is about 7 days I
>think.
>
>Do you have other old messages sat in the queue ? Do
you have messages
>queued for any other domains?
>
>Thanks
>Rob
>
>"ao" <oke@paramaze.com> wrote in message
> news:eaea01c2582b$e97ce670$a5e
62ecf@tkmsftngxa07...
>> Rob,
>>
>> Here is the NDR message:
>>
>> "From: System Administrator
>> Sent: Samstag, 31. August 2002 20:24
>> To: Hunt Ayele (E-mail)
>> Subject: Undeliverable: FW: Money for Grandma
>>
>> Your message did not reach some or all of the intended
>> recipients.
>>
>> Subject: FW: Money for Grandma
>> Sent: 29.08.2002 20:22
>>
>> The following recipient(s) could not be reached:
>>
>> Hunt Ayele (E-mail) on 31.08.2002 20:24
>> Could not deliver the message in the time
>> limit specified. Please retry or contact your
>> administrator.
>> <RONH-S01.rohner.local #4.4.7"
>>
>> I will try the nslookup when I am on the server.
>>
>> ao
>>
>>
>> >-----Original Message-----
>> >On the Exchange server, are you able to do an nslookup
>> of the mx record for
>> >the domain aol.com ? Can you paste the details in to
>> your reply ?
>> >
>> >On the Exchange server, if you telnet manually to the
>> aol.com, mx server,
>> >can you send an email manually ?
>> >
>> >What is the full text of the NDR? Can you paste that
in
>> to your reply?
>> >
>> >Perhaps your server is on a blacklist?
>> >
>> >Perhaps the mails being sent are over the size limit,
>> either on your end, or
>> >on AOL's end?
>> >
>> >Thanks
>> >Rob
>> >
>> >"ao" <oke@paramaze.com> wrote in message
>> > news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
>> >> My user mails to some domain names,
>> >> especially "aol.com" are not being delivered.
>> >>
>> >> There is no restriction on the "address space"
>> >> configuration page of the exchange server. Since the
>> NDR
>> >> seems to be generated by our Exchange Server, where
>> >> should I look again.
>> >>
>> >> ao
>> >>
>> >
>> >
>> >.
>> >
>
>
>.
>
| |
|
| Chad,
It is a new installation which is being use with ISA
server. But only mails addressed to aol.com are having
problems.
ao
>-----Original Message-----
>Is this Exchange server new to your organization? Do you
have a firewall?
>
>
>--
>Chad Smith
>Director of Information Services
>Condley and Company, L.L.P.
>Abilene, TX
>www.condley.com
>
>
>ao wrote:
>> My user mails to some domain names,
>> especially "aol.com" are not being delivered.
>>
>> There is no restriction on the "address space"
>> configuration page of the exchange server. Since the
NDR
>> seems to be generated by our Exchange Server, where
>> should I look again.
>>
>> ao
>
>
>.
>
| |
| Lanwench 2002-10-05, 8:21 pm |
| Is there a reverse-lookup record in your domain's DNS? AOL is particularly
fussy about requiring this.
"ao" <oke@paramaze.com> wrote in message
news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
> My user mails to some domain names,
> especially "aol.com" are not being delivered.
>
> There is no restriction on the "address space"
> configuration page of the exchange server. Since the NDR
> seems to be generated by our Exchange Server, where
> should I look again.
>
> ao
>
| |
|
| There is reverse-lookup which only for the Internal IP
range(domain) configuration. The Exch is not fully
connected to the Internet, it goes through a dial-up ISDN
router that is connected to a second nic and the router
gets dynamic IP from our ISP.
This work fine for every other outgoing mails except
aol.com
ao
>-----Original Message-----
>Is there a reverse-lookup record in your domain's DNS?
AOL is particularly
>fussy about requiring this.
>
>"ao" <oke@paramaze.com> wrote in message
> news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
>> My user mails to some domain names,
>> especially "aol.com" are not being delivered.
>>
>> There is no restriction on the "address space"
>> configuration page of the exchange server. Since the
NDR
>> seems to be generated by our Exchange Server, where
>> should I look again.
>>
>> ao
>>
>
>
>.
>
| |
| Lanwench 2002-10-05, 8:21 pm |
| If you have a dynamic IP, you obviously can't have a reverse lookup. If this
is the core of the problem with AOL, you may not be able to get around it.
You could try contacting their support, or repeatedly hitting your head with
a rubber mallet (I've found the latter to be just about as helpful,
frankly). Sorry I can't be of more help.
"ao" <oke@paramaze.com> wrote in message
news:edbc01c25841$2e9943b0$a5e
62ecf@tkmsftngxa07...
> There is reverse-lookup which only for the Internal IP
> range(domain) configuration. The Exch is not fully
> connected to the Internet, it goes through a dial-up ISDN
> router that is connected to a second nic and the router
> gets dynamic IP from our ISP.
>
> This work fine for every other outgoing mails except
> aol.com
>
> ao
> >-----Original Message-----
> >Is there a reverse-lookup record in your domain's DNS?
> AOL is particularly
> >fussy about requiring this.
> >
> >"ao" <oke@paramaze.com> wrote in message
> > news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
> >> My user mails to some domain names,
> >> especially "aol.com" are not being delivered.
> >>
> >> There is no restriction on the "address space"
> >> configuration page of the exchange server. Since the
> NDR
> >> seems to be generated by our Exchange Server, where
> >> should I look again.
> >>
> >> ao
> >>
> >
> >
> >.
> >
| |
|
| Lawench,
I guess you got me wrong. I only have dynamic IP on the
ISDN router. The reverse-lookup is on the internal DNS
that has unpublished IP range and Exchange is not
parmanent on the Internet. We do not have any published
IP within the LAN.
ao
>-----Original Message-----
>If you have a dynamic IP, you obviously can't have a
reverse lookup. If this
>is the core of the problem with AOL, you may not be able
to get around it.
>You could try contacting their support, or repeatedly
hitting your head with
>a rubber mallet (I've found the latter to be just about
as helpful,
>frankly). Sorry I can't be of more help.
>
>"ao" <oke@paramaze.com> wrote in message
> news:edbc01c25841$2e9943b0$a5e
62ecf@tkmsftngxa07...
>> There is reverse-lookup which only for the Internal IP
>> range(domain) configuration. The Exch is not fully
>> connected to the Internet, it goes through a dial-up
ISDN
>> router that is connected to a second nic and the router
>> gets dynamic IP from our ISP.
>>
>> This work fine for every other outgoing mails except
>> aol.com
>>
>> ao
>> >-----Original Message-----
>> >Is there a reverse-lookup record in your domain's DNS?
>> AOL is particularly
>> >fussy about requiring this.
>> >
>> >"ao" <oke@paramaze.com> wrote in message
>> > news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
>> >> My user mails to some domain names,
>> >> especially "aol.com" are not being delivered.
>> >>
>> >> There is no restriction on the "address space"
>> >> configuration page of the exchange server. Since the
>> NDR
>> >> seems to be generated by our Exchange Server, where
>> >> should I look again.
>> >>
>> >> ao
>> >>
>> >
>> >
>> >.
>> >
>
>
>.
>
| |
| Lanwench 2002-10-05, 8:28 pm |
| No, if this is the case, you do have a dynamic IP with regard to your FQDN.
Exchange is represented by the public IP on the router. Having a static IP
with NAT in use is not really relevant... you need to be able to set
mailserver.yourdomain.com to xxx.xxx.xxx.xxx (valid public IP specified in
your MX record reference).
"ao" <oke@besonet.ch> wrote in message
news:d05701c25897$e42940d0$37e
f2ecf@TKMSFTNGXA13...
> Lawench,
>
> I guess you got me wrong. I only have dynamic IP on the
> ISDN router. The reverse-lookup is on the internal DNS
> that has unpublished IP range and Exchange is not
> parmanent on the Internet. We do not have any published
> IP within the LAN.
>
> ao
>
>
> >-----Original Message-----
> >If you have a dynamic IP, you obviously can't have a
> reverse lookup. If this
> >is the core of the problem with AOL, you may not be able
> to get around it.
> >You could try contacting their support, or repeatedly
> hitting your head with
> >a rubber mallet (I've found the latter to be just about
> as helpful,
> >frankly). Sorry I can't be of more help.
> >
> >"ao" <oke@paramaze.com> wrote in message
> > news:edbc01c25841$2e9943b0$a5e
62ecf@tkmsftngxa07...
> >> There is reverse-lookup which only for the Internal IP
> >> range(domain) configuration. The Exch is not fully
> >> connected to the Internet, it goes through a dial-up
> ISDN
> >> router that is connected to a second nic and the router
> >> gets dynamic IP from our ISP.
> >>
> >> This work fine for every other outgoing mails except
> >> aol.com
> >>
> >> ao
> >> >-----Original Message-----
> >> >Is there a reverse-lookup record in your domain's DNS?
> >> AOL is particularly
> >> >fussy about requiring this.
> >> >
> >> >"ao" <oke@paramaze.com> wrote in message
> >> > news:f38201c25824$5803dbb0$9ee
62ecf@tkmsftngxa05...
> >> >> My user mails to some domain names,
> >> >> especially "aol.com" are not being delivered.
> >> >>
> >> >> There is no restriction on the "address space"
> >> >> configuration page of the exchange server. Since the
> >> NDR
> >> >> seems to be generated by our Exchange Server, where
> >> >> should I look again.
> >> >>
> >> >> ao
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
|
|
|
|
|