RE: SBS 2003 SP1 and Exchange SP2
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Wed, 30 Nov 2005 07:23:19 GMT
Hi Courtney,
Thanks for posting here!
For your description, I understand that you got error " The administrative
limit for this request was exceeded." When you try to add send filters on
Exchange 2003 server.
Based on my knowledge, this is an Active Directory error caused when the
non-linked attributes stored in an Active Directory object exceeds the
limitations. A nine-byte tag for every value must be put on the database
record for that object, and database records cannot span multiple database
pages (8k). That implies a theoretical upper limit of 910 values (across
all non-linked attributes) on a single DS object. In fact, the number is
~50 lower because of fixed fields in the database record.
Due to this AD limitation of the non-linked attributes, the Turf list in
Exchange (i.e. Recipient filtering + Sender filtering + Connection
filtering) is limited to approximately 850 total entries.
For your now situation, I suggest that you refer to the following KB
article to automate the removal of all of the extra addresses.
Removing duplicate and unwanted proxy addresses in Exchange
http://support.microsoft.com/?id=318774
And there is another possible workaround, that is instead of filtering on
individual email addresses or domains, enable "filter recipients who are
not in the directory" on the Recipient Filtering. This should dramatically
reduce the amount of SPAM hitting the server. If so, you may be able be
able to remove/reduce most of the Sender Filtering which will lower the
number of non-linked attributes stored on the Message Delivery object
settings.
Hope above information helps! I am happy to be assistance of you and look
forward to your reply!
Have a nice day!
Sincerely,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: SBS 2003 SP1 and Exchange SP2
>thread-index: AcX099Aen+egaiYlSCqpkwscGPl+tw==
>X-WBNR-Posting-Host: 207.101.109.178
>From: "=?Utf-8?B?Q291cnRuZXk=?=" <Courtney@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: SBS 2003 SP1 and Exchange SP2
>Date: Tue, 29 Nov 2005 07:16:03 -0800
>Lines: 22
>Message-ID: <E8309D95-A3EC-4F9B-8885-A11270967246@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:226353
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>I have SBS 2003 with SP1 installed and all other updates as of last month
>installed including Exchange SP2. Yesterday I started receiving an error
>message when adding email domains to the Sender Filtering as described
below.
>
>Under Global Settings / Message Delivery / Sender Filtering I've been
adding
>SPAM email addresses. Just today I have seemed to have reach some kind of
>limit.
>When I add a new email address to filter and click on Apply I get the
>following error:
>
>The administrative limit for this request was exceeded.
>Facility: LDAP Provider
>ID no: 80072024
>Exchange System Manager
>
>When I click OK and then Apply again, the message does not come up again,
so
>it seems to take, but I am curious if anyone else has seen this before or
>knows what the actual limit for addresses is?
>
>Thanks in advance for your help!
>
>Courtney
>
.
- Prev by Date: RE: Mail Marshal for SMTP on SBS 2k3 Premium
- Next by Date: Re: Upgrading the instance of WMSDE used for Windows SharePoint Se
- Previous by thread: Re: SBS 2003 SP1 and Exchange SP2
- Next by thread: SBS 2003 may be trashed - can it be saved?
- Index(es):
Relevant Pages
|
