Exchange Server Forums

delivery fails

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> General >> delivery fails

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

delivery fails - 16.Jan.2002 10:27:00 AM

jasmin

Posts: 24
Joined: 14.Nov.2001
Status: offline

I have exchange with sp2. Some (not all)external emails are not being delivered. They are to different domains as well - so no link there. Anyway when the email is sent the following day the sender will receive the delay message and the day after that they will get the following message:

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

Subject: Contract 1/119 - Tech Query RYTQF008
Sent: 20/12/2001 16:20

The following recipient(s) could not be reached:

npd@mm-mose.mottmac.com on 22/12/2001 16:24
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<XXX.XXX #4.4.7>

(obviously I have replaced our domain name with XXX.XXX)

Anyway according to the MS website error 4.4.7 means:

Numerical Code: 4.4.7
Possible Cause: The message in the queue has expired. The sending server tried to relay or deliver the message but the action was not completed before the message expiration time occurred. This message can also indicate that a message header limit has been reached on a remote server or some other protocol timeout occurred while communicating with the remote server.
Troubleshooting: This message usually indicates an issue on the receiving server. Check the validity of the recipient address, and determine if the receiving server is configured to receive messages correctly. It may be necessary to reduce the number of recipients in the header of the message for the host to which you are receiving this error. If you resend the message, it is placed in the queue again. If the receiving server is up, the message is delivered.

Using NSlookup on the domains gets the correct response. Basically I need to know whether it it our fault with exchange or the other domains (as microsoft suggest) If it is our side is there a fix..

Many thanks in advance

Post #: 1

Featured Links*

RE: delivery fails - 21.Jan.2002 4:17:00 PM

jamesjarder

Posts: 12
Joined: 31.Oct.2001
From: riyadh
Status: offline

This is exactly our problem too. It happened only when we upgraded to Exch2000 from exch5.5. The problem is on our side not the recepient.

I have no fix yet. So please guys help us out here!

James

(in reply to jasmin)

Post #: 2

RE: delivery fails - 22.Jan.2002 1:33:00 PM

jamesjarder

Posts: 12
Joined: 31.Oct.2001
From: riyadh
Status: offline

help

(in reply to jasmin)

Post #: 3

RE: delivery fails - 24.Jan.2002 8:59:00 AM

pankaj

Posts: 38
Joined: 11.Sep.2001
Status: offline

apply latest service pack which might solved your problem

take care

pankaj

(in reply to jasmin)

Post #: 4

RE: delivery fails - 24.Jan.2002 4:51:00 PM

jasmin

Posts: 24
Joined: 14.Nov.2001
Status: offline

we have the latest service pack on our exchange 2000 server (sp2)

(in reply to jasmin)

Post #: 5

RE: delivery fails - 27.Jan.2002 7:19:00 AM

jamesjarder

Posts: 12
Joined: 31.Oct.2001
From: riyadh
Status: offline

i thought e2k sp2 would solve the problem too--- but it didn't.

(in reply to jasmin)

Post #: 6

RE: delivery fails - 30.Jan.2002 1:03:00 PM

Guest

I have this problem also, it only happened after SP2 was installed.
Have tried
reinstalling EXCH and SP1 no joy
reinstalling EXCH and SP2 no joy.
SMTP activity is OK on internal and receipt of external.
I think the problem lies in the routing engine.

Will post if I solve it.

(in reply to jasmin)

Post #: 7

RE: delivery fails - 30.Jan.2002 6:05:00 PM

britney

Posts: 5
Joined: 17.Jan.2002
Status: offline

I got the same problem here too.
Exchange 2000 with SP2, published behind ISA Server. Second Server, Exchange 5.5 with sp4 behind the same firewall (same ISA Server). When user on E2k Server sent mail to exchange 5.5 domains, we got a error message 4.4.7.
any help will be appreciated.

britney

(in reply to jasmin)

Post #: 8

RE: delivery fails - 31.Jan.2002 7:11:00 PM

britney

Posts: 5
Joined: 17.Jan.2002
Status: offline

Hi guys,

I did some more testing:

1. do nslookup at both exchange serve (5.5 and 2000), the query was sucessful. I tried both "MX" record query and "A" record query

2. when i do telnet with port 25 /110 from e2k to e5.5 server. It gave me a "connection to host lost" error message.
Same problem on the E5.5 server side

3. Try to play around with administrative group in Exchange 2000, but I can't add exchange 5.5 there.

any idea or suggestion will be appreciated.
thanks in advance.

Britney

(in reply to jasmin)

Post #: 9

RE: delivery fails - 2.Feb.2002 4:25:00 PM

jamesjarder

Posts: 12
Joined: 31.Oct.2001
From: riyadh
Status: offline

Actually, mine started when i installed E2K with SP1. When i'm still using Exch 5.5, everything works fine. I'm sure it's something on E2K settings, just can't get what it is.

One of our pals here in the list mentioned about KB 303889 which is not yet publicly available. Can anyone please check this with Microsoft.

When i get it working first, i will post here.

Thanks people.

(in reply to jasmin)

Post #: 10

RE: delivery fails - 4.Feb.2002 3:37:00 PM

pankaj

Posts: 38
Joined: 11.Sep.2001
Status: offline

search thread mails to louady.com not going
on msexchange.org

(in reply to jasmin)

Post #: 11

RE: delivery fails - 5.Feb.2002 7:46:00 AM

jamesjarder

Posts: 12
Joined: 31.Oct.2001
From: riyadh
Status: offline

Actually it's loudeye.com.

But no, it doesn't help.

In my situation, if i work with offline folders in Outlook2000, then ALL mail will go. It only happens when i connect to Exchange2000 (error 4.4.7)

James

(in reply to jasmin)

Post #: 12

RE: delivery fails - 7.Feb.2002 12:25:00 PM

jasmin

Posts: 24
Joined: 14.Nov.2001
Status: offline

hi.. have found this article on MS webpage that explains all...article number Q257638

to summarise the cause is:
Exchange Server 5.5 supports local scope restrictions on an address-space basis instead of by connector. Exchange 2000 only supports local scope restrictions by connector, and therefore, it is possible to get loops or for messages to be returned with an NDR if some connectors are configured with a scope restriction on an address space, while others are configured on a connector.

and the resolution is to:
Remove local scope restrictions on address spaces on the Exchange Server 5.5 connectors.

One solution is to add another connector with no scope restrictions, with the original connector left in place with scope restrictions. This way other sites and routing groups can see a valid route and will not let the messages expire or generate NDRs with 4.4.7 Delivery Status Notification (DSN). This resolution is feasible if, for example, there are multiple address spaces and the X.400 address space is not the restricted one.

apparently (according to MS) this is a design feature in exchange 2000.
As my server is only running exchange 2000 I have forwarded this info to the domains that I am having problems with..
hope this helps

(in reply to jasmin)

Post #: 13