Re: Slow Incoming Mail Performance
- From: "Geoff Pearce" <buckypearce@xxxxxxxxxxx>
- Date: Mon, 4 Apr 2005 12:08:56 -0400
This queue is described at the following link
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3TechRef/f4fb781c-5d7a-495b-9f53-b09aa8c4ddf8.mspx
In the section
"Messages Awaiting Directory Lookup This queue is also named the
pre-categorization queue. It is a throttling queue for the categorizer. This
queue contains messages before they reach the categorizer. The categorizer
resolves the sender and recipient information against Active Directory,
expands distribution lists, checks restrictions, applies per-sender and
per-recipient limits, and more. The categorizer is discussed in more detail
in the section, "Exchange Categorizer," later in this chapter. "
Two common problems
1) Check the performance of the Domain Controller that Exchange Server is
performing its lookups for resolving receipients.
2) If you have a large number of items in your outbound SMTP queues with <>
or
postmaster as the originating email address then you have a dictionary
attack issue.
Exchange Server accepts aliases to valid domains at your exchange server.
Later if the alias is undeliverable then Exchange Server returns an Non
Deliver Report (NDR) to the orginator. If a nondelivery report can't be
delivered to the sender, a copy of the original message is placed in the
"bad" mail directory. Messages placed in the bad mail directory can't be
delivered or returned. You can use the bad mail directory to track potential
abuse of your messaging system. By default, the bad mail directory is
located at root:\Exchsrvr\Mailroot\vsi#\BadMail, where root is the install
drive for Exchange Server and # is the number of the SMTP virtual server,
such as C:\Exchsrvr\Mailroot\vsi 1\BadMail. You can change the location of
the bad mail directory at any time, but you should never place the directory
on the M: drive, which is reserved for other types of Exchange Server data.
Likely at your location spammers are attempting dictionary attacks on your
domains in an attempt to get their emails delivered. A dictionary attack
are emails addressed to a large list of common aliases. Also to prevent the
spammer from being swamped with NDRs the originating email address is
typically spoofed or randomized. Exchange Server attempts to deliver NDRs
to the originator of the emails with invalid aliases during the dictionary
attack. Due to the fact that many of the originating addresses of the spam
are falsified the NDRs sit in the outbound queue (outbound with originating
address of <> or postmaster@xxxxxxxxxxxxxx) attempting to go to an invalid
location. Eventually the NDRs fail the defined number of retrys and are
moved to your Badmail folder.
The following article describes how to prevent exchange 2003 server from
accepting undeliverable email and therefore would reduce the amount of items
in your badmail folder.
http://support.microsoft.com/default.aspx?scid=kb;en-us;823866
Geoff Pearce
"smoore3513" <smoore3513@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:729BBAD8-315F-41F2-AC38-5634402B2EAD@xxxxxxxxxxxxxxxx
> Yes, the messages are sitting in the messages awaiting directory lookup
> que
> on the FE SMTP connector.
>
> "Mark Arnold [MVP]" wrote:
>
>> On Tue, 29 Mar 2005 09:23:10 -0800, "smoore3513"
>> <smoore3513@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> >When email is sent to our domain it takes 15-30 minutes to receive. We
>> >have
>> >around 100 users and a FE-BE Exchange 2000 topology setup. This just
>> >started
>> >occuring after 2 years. We have over 2gb of ram on the FE and BE and
>> >dual
>> >1ghz Zeon Processors. We have ran the Exchange Best Analayzer tools and
>> >made
>> >the necessary corrections recomended. The latest service packs and
>> >patches
>> >have been applied to Windows 2000 and Exchange 2000 servers. Any idea
>> >on
>> >why incoming mail takes 15-30 minutes to reach our end-users?
>> >
>> have you looked at Message tracking and taken a look as to where the
>> delay actually is?
>> Do you see the messages sit in a queue (any queue) waiting to be
>> delivered into the mailbox?
>>
.
- Prev by Date: Unable to Open other Users Inbox
- Next by Date: Re: Exchange 2003 owa login problem
- Previous by thread: Unable to Open other Users Inbox
- Next by thread: Global Address list
- Index(es):
Relevant Pages
|
