|
|
|
date: Thu, 13 Oct 2005 14:46:36 -0500,
group: microsoft.public.exchange2000.development
back
Re: OOF and event sinks
Thanks Victor. But this begs the question: if an event sink deletes an
e-mail that is destined for a mailbox that has OOF turned on, and OOF has
already been processed, then OOF should *NOT* go out, but they probably will
be sent!
You'd think the item would have to be committed to the Inbox before OOF is
processed...
--
Eric Legault (MVP - Outlook, MCDBA, old school WOSA MCSD, B.A.)
Blog: http://blogs.officezealot.com/legault
Try Picture Attachments Wizard for Outlook!
http://www.collaborativeinnovations.ca
"Victor Ivanidze" <no@spam.please> wrote in message
news:ebErs5M0FHA.2884@TK2MSFTNGP09.phx.gbl...
> Hi Eric,
>
> on my test Exchange 2003 server OOF is processed before the store event is
> fired. I have no idea why it happened.
> So it seems your only option is deleting outgoing OOF messages.
>
> Regards,
> Victor Ivanidze
>
> "Eric Legault [MVP - Outlook]" wrote in
> message news:eVwfT7C0FHA.2008@TK2MSFTNGP10.phx.gbl...
> I'm trying to architect a solution to handle OOF notifications to the
> Internet. I have two options I'm reviewing:
>
> - delete outgoing OOF notifications if the e-mail address does not match a
> "white list" (stored in a database). Would require an SMTP event sink,
and
> assumes I can detect the message class as being
> IPM.Note.Rules.OofTemplate.Microsoft
> - bypass OOF from even firing by intercepting an incoming message in a
> store-wide synchronous sink - if sender e-mail doesn't match the white
list,
> delete before it is committed. Can the OOF rule be bypassed in this
> situation? This method is preferred because my client already has a sink
> trapping incoming messages and moving non white-list e-mails into Inbox
> subfolders. However, I assume that since these e-mails are still
generating
> OOF notifications that the OOF rule is processed before the store receives
> the item - but how can that be possible??
>
> Thoughts?
>
> --
> Eric Legault (MVP - Outlook, MCDBA, old school WOSA MCSD, B.A.)
> Blog: http://blogs.officezealot.com/legault
> Try Picture Attachments Wizard for Outlook!
> http://www.collaborativeinnovations.ca
>
>
date: Mon, 17 Oct 2005 10:31:31 -0500
author: Eric Legault [MVP - Outlook]
Re: OOF and event sinks
From what I remember, OOF is like a rule and rules are processed before
event sinks which would cause the behavior you're seeing. Weird, yes but
works as expected :)
Tom
--
Looking for a good book on programming Exchange, Outlook, ADSI and
SharePoint? Check out http://www.microsoft.com/MSPress/books/5517.asp
"Eric Legault [MVP - Outlook]" wrote in
message news:e98na$y0FHA.3336@TK2MSFTNGP12.phx.gbl...
> Thanks Victor. But this begs the question: if an event sink deletes an
> e-mail that is destined for a mailbox that has OOF turned on, and OOF has
> already been processed, then OOF should *NOT* go out, but they probably
> will
> be sent!
>
> You'd think the item would have to be committed to the Inbox before OOF is
> processed...
>
> --
> Eric Legault (MVP - Outlook, MCDBA, old school WOSA MCSD, B.A.)
> Blog: http://blogs.officezealot.com/legault
> Try Picture Attachments Wizard for Outlook!
> http://www.collaborativeinnovations.ca
>
> "Victor Ivanidze" <no@spam.please> wrote in message
> news:ebErs5M0FHA.2884@TK2MSFTNGP09.phx.gbl...
>> Hi Eric,
>>
>> on my test Exchange 2003 server OOF is processed before the store event
>> is
>> fired. I have no idea why it happened.
>> So it seems your only option is deleting outgoing OOF messages.
>>
>> Regards,
>> Victor Ivanidze
>>
>> "Eric Legault [MVP - Outlook]" wrote in
>> message news:eVwfT7C0FHA.2008@TK2MSFTNGP10.phx.gbl...
>> I'm trying to architect a solution to handle OOF notifications to the
>> Internet. I have two options I'm reviewing:
>>
>> - delete outgoing OOF notifications if the e-mail address does not match
>> a
>> "white list" (stored in a database). Would require an SMTP event sink,
> and
>> assumes I can detect the message class as being
>> IPM.Note.Rules.OofTemplate.Microsoft
>> - bypass OOF from even firing by intercepting an incoming message in a
>> store-wide synchronous sink - if sender e-mail doesn't match the white
> list,
>> delete before it is committed. Can the OOF rule be bypassed in this
>> situation? This method is preferred because my client already has a sink
>> trapping incoming messages and moving non white-list e-mails into Inbox
>> subfolders. However, I assume that since these e-mails are still
> generating
>> OOF notifications that the OOF rule is processed before the store
>> receives
>> the item - but how can that be possible??
>>
>> Thoughts?
>>
>> --
>> Eric Legault (MVP - Outlook, MCDBA, old school WOSA MCSD, B.A.)
>> Blog: http://blogs.officezealot.com/legault
>> Try Picture Attachments Wizard for Outlook!
>> http://www.collaborativeinnovations.ca
>>
>>
>
>
date: Sun, 23 Oct 2005 21:39:53 -0700
author: Tom Rizzo [MSFT]
Re: OOF and event sinks
Eric,
I do not catch your point. You mean that OOF address matches "white list"
but original message is deleted by other store event sink? Then outgoing OOF
will be generated, but you're bothering about that? External Internet
recipient has to receive OOF despite of any action on your side, and he'll
receive it. Or I missing something?
Regards,
Victor
"Eric Legault [MVP - Outlook]" wrote in
message news:e98na$y0FHA.3336@TK2MSFTNGP12.phx.gbl...
> Thanks Victor. But this begs the question: if an event sink deletes an
> e-mail that is destined for a mailbox that has OOF turned on, and OOF has
> already been processed, then OOF should *NOT* go out, but they probably
> will
> be sent!
>
> You'd think the item would have to be committed to the Inbox before OOF is
> processed...
>
> --
> Eric Legault (MVP - Outlook, MCDBA, old school WOSA MCSD, B.A.)
> Blog: http://blogs.officezealot.com/legault
> Try Picture Attachments Wizard for Outlook!
> http://www.collaborativeinnovations.ca
>
> "Victor Ivanidze" <no@spam.please> wrote in message
> news:ebErs5M0FHA.2884@TK2MSFTNGP09.phx.gbl...
>> Hi Eric,
>>
>> on my test Exchange 2003 server OOF is processed before the store event
>> is
>> fired. I have no idea why it happened.
>> So it seems your only option is deleting outgoing OOF messages.
>>
>> Regards,
>> Victor Ivanidze
>>
>> "Eric Legault [MVP - Outlook]" wrote in
>> message news:eVwfT7C0FHA.2008@TK2MSFTNGP10.phx.gbl...
>> I'm trying to architect a solution to handle OOF notifications to the
>> Internet. I have two options I'm reviewing:
>>
>> - delete outgoing OOF notifications if the e-mail address does not match
>> a
>> "white list" (stored in a database). Would require an SMTP event sink,
> and
>> assumes I can detect the message class as being
>> IPM.Note.Rules.OofTemplate.Microsoft
>> - bypass OOF from even firing by intercepting an incoming message in a
>> store-wide synchronous sink - if sender e-mail doesn't match the white
> list,
>> delete before it is committed. Can the OOF rule be bypassed in this
>> situation? This method is preferred because my client already has a sink
>> trapping incoming messages and moving non white-list e-mails into Inbox
>> subfolders. However, I assume that since these e-mails are still
> generating
>> OOF notifications that the OOF rule is processed before the store
>> receives
>> the item - but how can that be possible??
>>
>> Thoughts?
>>
>> --
>> Eric Legault (MVP - Outlook, MCDBA, old school WOSA MCSD, B.A.)
>> Blog: http://blogs.officezealot.com/legault
>> Try Picture Attachments Wizard for Outlook!
>> http://www.collaborativeinnovations.ca
>>
>>
>
>
date: Tue, 25 Oct 2005 08:34:59 +0400
author: Victor Ivanidze se
|
|
