esday, January 22, 2008 5:02 PM
To: MS-Exchange Admin Issues
Subject: Re: Event ID 9667
No need to apologize...in fact I should thank you for taking the time to
educate me...Now I know how much I don't know!
As for MFCMAPI, I downloaded the tool, but I'm not sure how to use it. Do I
B. Smith
>
> MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> *From:* Michael B. Smith [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, January 22, 2008 1:22 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* RE: Event ID 9667
>
>
>
>
>
>
mation, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From: Michael B. Smith [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 22, 2008 1:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Event ID 9667
Sorry, I got carried away with the explanation and didn't answer t
PROTECTED]
Sent: Tuesday, January 22, 2008 1:22 PM
To: MS-Exchange Admin Issues
Subject: RE: Event ID 9667
In general, any message accepted via SMTP (or via drop/pickup folders) is a
non-promoted message until it is processed by the store. This means that it
gets stored into the STM file in
January 22, 2008 12:35 PM
To: MS-Exchange Admin Issues
Subject: Re: Event ID 9667
Here are the named properties it's trying to create:
X-TM-IMSS-Message-ID
X-Content-Filtered-By
X-Original-Date
X-TFF-CGPSA-Filter
X-TFF-CGPSA-Version
X-Puresend
X-Fantasy-No-Post
X-filenames
By "it"
gt;
> Michael B. Smith
>
> MCSE/Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> *From:* Alex Alborzfard [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, January 22, 2008 10:33 AM
> *To:* MS-Exchange Admin Issues
> *Subject:* Re: Event ID 9667
>
>
>
&g
Alex Alborzfard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 22, 2008 10:33 AM
To: MS-Exchange Admin Issues
Subject: Re: Event ID 9667
If you're referring to the number after quota limit, it's 8192. There are
like 6 or 7 of these events with unique named properties in the APP log.
If you're referring to the number after quota limit, it's 8192. There are
like 6 or 7 of these events with unique named properties in the APP log.
>From the named properties, it seems that it has something to do with our
spam appliance.
Thanks
On Jan 22, 2008 9:38 AM, Michael B. Smith <[EMAIL PRO
What's the number? You only get that warning when you are within 20% of the
maximum limit.
You need to figure out what's creating the named properties.
Regards,
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
From: Alex Alborzfard [mailto:[EMAIL PROTECTED]
Sent
