> "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org> wrote in message
> news:O8%23iVloZKHA.3992@TK2MSFTNGP04.phx.gbl...
>> "Nick" <No...@NotHere.com> wrote in message
>> news:%23oqNHjhZKHA.5372@TK2MSFTNGP06.phx.gbl...
>>> Hi,

>>> We have an SMTP event sink on our SBS2003 box which now works fine for
>>> normal incoming & outgoing mail but does not get triggered for mail sent
>>> via Outlook Web Access.  Any ideas why this is and what we can do to
>>> solve it?

>>> Thanks,
>>>  Nick

>> OWA connectivity works a bit different than MAPI. It uses DAVEx and EXIPC
>> ISAPI components that communicates to the information store. If you wrote
>> the event, I believe you will have to write something to monitor the
>> component, otherwise the issue *may* be in the SMTP sink where it is
>> triggering, at the actual outbound of the routing engine, or sooner. I'm
>> not a developer to specifically respond to how to do it, rather I'm just
>> juggling the IIS SMTP components in my head and surmizing this theory.
>> You may be better off posting this to a dev group related to the code you
>> used to write the sink.

>> For what it's worth, if it helps any at all, below is some info from the
>> MOC 2400 Exchange 2003 courseware that may help understand OWA components
>> and relationship, assuming of course, you are running SBS 2003 with
>> Exchange 2003. I hope it helps. Good luck!

>> MOC 2400, Mod 7, p5, Implementing OWA:
>> "OLE DB Provider for Exchange (ExOLEDB). Acts as the interface
>> between and the Exchange Information Store and the Exchange
>> Interprocess Communications (EXIPC). ExOLEDB accepts requests for
>> mailbox or public folder data from the EXIPC, later extracts the
>> information from the Information Store, and then sends the results back
>> to IIS through EXIPC."

>> p6:
>> "DAVEx. An Internet Service Application Programming Interface (ISAPI)
>> component that passes the client request between the World Wide Web
>> Publishing Service and the Information Store. DAVEx renders data
>> received from the store and then passes the data back to the World Wide
>> Web Publishing Service to return to the client browser. DAVEx is not
>> used by a front-end server in a front-end/back-end server configuration."

>> "ExProx. An ISAPI component that is used in a front-end/back-end server
>> configuration only. ExProx acts as a protocol gateway on a front-end
>> server. ExProx receives the request from World Wide Web Publishing
>> Service and then accesses Active Directory to locate the user's mailbox
>> server. ExProx then passes the request to the correct back-end server.
>> The back-end server passes the data to ExProx, which then sends the
>> data to the World Wide Web Publishing Service to return to the client
>> browser."

>> --
>> Ace

>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.

>> Please reply back to the newsgroup or forum for collaboration benefit
>> among responding engineers, and to help others benefit from your
>> resolution.

>> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
>> 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer

>> For urgent issues, please contact Microsoft PSS directly. Please check
>> http://support.microsoft.com for regional support phone numbers.

> Thanks Ace,

> There is definately nothing in the code of my event sink stopping this.
> It is triggered on the ISMTPOnArrival_OnArrival event and registered by
> the following command line:
> cscript smtpreg.vbs /add 1 onarrival SMTPEventSink SMTP.EventSink "RCPT
> TO=*"

> I have tried posting this to the microsoft.public.exchange.development
> newsgroup but no one seems to read that, virtually no activity there.  Any
> ideas how I can get in touch with someone from the Microsoft Exchange
> development team.
> Nick