| Rob McKee 2002-12-19, 8:23 am |
| I have reviewed the event logs with avail. However, while
doing so I realized that I had much of the Exchange
protocol logging turned off. The messages that fail are
ones from external to the office where the users are
connecting via POP connections and replying to multiple
head office staff. Is there a likely failure point in the
translation between POP to our internal MAPI routing.
Thanks for your help
>-----Original Message-----
>Off of the top of my head, it COULD possibly have
>something to do with the availablility of a GC. However,
>this would apply more to situations where you are sending
>to a distribution list.
>
>When you reply to a message, you are in fact "modifying"
>the original message and are creating a new message.
>Please someone correct me if I am incorrect with this
>statement.
>
>Are you familiar with the path that messages take? In a
>nutshell, a message goes from the MAPI Client (
assumption
>I am making is that we are talking about OUTLOOK 2000 or
>OUTLOOK XP ) to the Information Store ( to the edb
>database if MAPI )and then to the ExIPC Shared Memory (
>Exchange and IIS share this common memory area for
>performance reasons, among others ). It is now turned
>over to IIS. It goes to the Advanced Querying Engine, to
>the Pre-Categorizer, then to the Message Categorizer (
>where the GC fits in here - for expanding DLs, etc.
etc. )
>to the Post-Categorizer to the Routing Engine. This is
>where the LINK STATE TABLE comes into effect. The
Routing
>Engine then puts it in either the Local Deliver Queue or
>in the appropriate Remote Delivery Queue.
>
>Also, let's not forget that Exchange 2000 make use of the
>UDP Protocol for notification of new e-mails.
>
>I hope that this might point you in the right direction.
>
>I know that you mentioned "logs", but have you checked
the
>Event Viewer to see if you have any Warning or Error
>messages in there...
>
>Cary
>
>
>>-----Original Message-----
>>Our Exchange 2000 server is randomly failing to deliver
>>messages to all recipients. It mat not be entirely
>random,
>>in that the messages that appear to have not been
>>delivered are usually at the end of a long thread of
>>emails where there have been a number of replies and
>>forwards and CC's, & BCC's. At some random point in the
>>thread the server stops delivering the email to all of
>the
>>recipients. The server tracking logs show that the TO:
>has
>>dropped all the other recipients, however the detailed
>>events indicate that the messages were delivered to
boxes
>>that have definitely not received the messages.
>>
>>Any suggestions?
>>
>>.
>>
>.
>
|