We have an ISMTPOnArrival event sink triggered on
theISMTPOnArrival_OnArrival event, which is registered by:
smtpreg.vbs /add 1 onarrival mySMTPEventSink mySMTP.EventSink "mail
from=*"



This works fine for incoming email but unfortunately does not get triggered
for outgoing mail. Any ideas why this might be the case?

What are you trying to accomplish with event sinks in a typical SBS
2003/Exchange 2003 install? Perhaps asking in an Exchange newsgroup would
bring you more/better responses.

"Nick" <NoOne@newsgroup> wrote in message
news:uSDuVUhNKHA.5108@newsgroup

> We have an ISMTPOnArrival event sink triggered on
> theISMTPOnArrival_OnArrival event, which is registered by:
> smtpreg.vbs /add 1 onarrival mySMTPEventSink mySMTP.EventSink "mail
> from=*"
>
> This works fine for incoming email but unfortunately does not get
> triggered for outgoing mail. Any ideas why this might be the case?
>
>
>

Trying to write a system to Archive all emails, both incoming and outgoing.

"SteveB" <newsgroup@newsgroup> wrote in message
news:uCnb94hNKHA.4580@newsgroup

> What are you trying to accomplish with event sinks in a typical SBS
> 2003/Exchange 2003 install? Perhaps asking in an Exchange newsgroup would
> bring you more/better responses.
>
> "Nick" <NoOne@newsgroup> wrote in message
> news:uSDuVUhNKHA.5108@newsgroup

>> We have an ISMTPOnArrival event sink triggered on
>> theISMTPOnArrival_OnArrival event, which is registered by:
>> smtpreg.vbs /add 1 onarrival mySMTPEventSink mySMTP.EventSink "mail
>> from=*"
>>
>> This works fine for incoming email but unfortunately does not get
>> triggered for outgoing mail. Any ideas why this might be the case?
>>
>>
>>

>
>

"Nick" <NoOne@newsgroup> wrote in message
news:OkmUz9hNKHA.3992@newsgroup

Wouldn't Exchange's journaling feature be better suited?

Ace

> Trying to write a system to Archive all emails, both incoming and
> outgoing.
>
> "SteveB" <newsgroup@newsgroup> wrote in message
> news:uCnb94hNKHA.4580@newsgroup

>> What are you trying to accomplish with event sinks in a typical SBS
>> 2003/Exchange 2003 install? Perhaps asking in an Exchange newsgroup would
>> bring you more/better responses.
>>
>> "Nick" <NoOne@newsgroup> wrote in message
>> news:uSDuVUhNKHA.5108@newsgroup

>>> We have an ISMTPOnArrival event sink triggered on
>>> theISMTPOnArrival_OnArrival event, which is registered by:
>>> smtpreg.vbs /add 1 onarrival mySMTPEventSink mySMTP.EventSink "mail
>>> from=*"
>>>
>>> This works fine for incoming email but unfortunately does not get
>>> triggered for outgoing mail. Any ideas why this might be the case?
>>>
>>>
>>>

>>
>>

>
>

Trust me on this one; writing your own isn't worth it. If you are ever in a
situation where you *need* that archiving (usually legal) it means that you
are in a position where someone has asked for discovery and a home-brew
system won't be considered trustworthy.

Plenty of 3rd-party products offer this and they are relatively inexpensive
if you are in the market segment that requires archiving. Save yourself the
time and hassle and just pick one up.

-Cliff


"Nick" <NoOne@newsgroup> wrote in message
news:OkmUz9hNKHA.3992@newsgroup

> Trying to write a system to Archive all emails, both incoming and
> outgoing.
>
> "SteveB" <newsgroup@newsgroup> wrote in message
> news:uCnb94hNKHA.4580@newsgroup

>> What are you trying to accomplish with event sinks in a typical SBS
>> 2003/Exchange 2003 install? Perhaps asking in an Exchange newsgroup would
>> bring you more/better responses.
>>
>> "Nick" <NoOne@newsgroup> wrote in message
>> news:uSDuVUhNKHA.5108@newsgroup

>>> We have an ISMTPOnArrival event sink triggered on
>>> theISMTPOnArrival_OnArrival event, which is registered by:
>>> smtpreg.vbs /add 1 onarrival mySMTPEventSink mySMTP.EventSink "mail
>>> from=*"
>>>
>>> This works fine for incoming email but unfortunately does not get
>>> triggered for outgoing mail. Any ideas why this might be the case?
>>>
>>>
>>>

>>
>>

>
>

But that only puts the mail into another mailbox which would soon fill-up if
it were keeping an archive of all mail. What we are trying to do is record
the mail in a database.


"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:%23rRV4BiNKHA.4004@newsgroup

> "Nick" <NoOne@newsgroup> wrote in message
> news:OkmUz9hNKHA.3992@newsgroup
>
> Wouldn't Exchange's journaling feature be better suited?
>
> Ace
>
>
>

>> Trying to write a system to Archive all emails, both incoming and
>> outgoing.
>>
>> "SteveB" <newsgroup@newsgroup> wrote in message
>> news:uCnb94hNKHA.4580@newsgroup

>>> What are you trying to accomplish with event sinks in a typical SBS
>>> 2003/Exchange 2003 install? Perhaps asking in an Exchange newsgroup
>>> would bring you more/better responses.
>>>
>>> "Nick" <NoOne@newsgroup> wrote in message
>>> news:uSDuVUhNKHA.5108@newsgroup
>>>> We have an ISMTPOnArrival event sink triggered on
>>>> theISMTPOnArrival_OnArrival event, which is registered by:
>>>> smtpreg.vbs /add 1 onarrival mySMTPEventSink mySMTP.EventSink "mail
>>>> from=*"
>>>>
>>>> This works fine for incoming email but unfortunately does not get
>>>> triggered for outgoing mail. Any ideas why this might be the case?
>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>
>

"Nick" <NoOne@newsgroup> wrote in message
news:OjZdIjqOKHA.1280@newsgroup

> But that only puts the mail into another mailbox which would soon fill-up
> if it were keeping an archive of all mail. What we are trying to do is
> record the mail in a database.
>

Your event sink is doing something similar, I assume, whether it puts it
into a database or a mailbox. In a large scale environment, (I know, I'll
get comments on this), we have journalling enabled, as well as a 3rd party
archive system that puts everything into an SQL database, with a front end
that works with OWA and Outlook allowing users access to their archived
data, but at the same time, we have a journal mailbox for each store to go
back on directly, if needed.

I am not a programmer, and I don't know if you are storing it per user, as
in mirroring a whole mailbox for each individual or not, but I would imagine
to look at MAPI methods to work with inbound and outbound mail at the store
level, otherwise, I would write something to intercept data in and out of
the Journal mailbox using MAPI.

These are just thoughts, thinking out loud. However, I would think if you
need more specific help with the event sink, since it is a programming
question and not specifically an SBS question, I would suggest to post to
the following more qualified newsgroups for specific help in programming. I
don't know which language or method you are using, but the two following
would be a good start, and I'm they can direct you to a specific group if
they are not the correct groups.

microsoft.public.dotnet.scripting
microsoft.public.scripting.vbscript

Ace

Because the only events are for mail which is Arriving,
not outgoing.

To make your outgoing mail "arrive", add a second
SMTP thing to Exchange, and route all of your outgoing
mail through it, and then on from it in the normal way.

All of your outgoing mail from Exchange goes out
through your original SMTP thing, into the new one,
and then out to the world. An event sink on the
new SMTP thing will see all outgoing mail arriving.

(david)
*OK, I can't remember what the SMTP thing is called.
Just go to Exchange, find SMTP, and create a new one.


"Nick" <NoOne@newsgroup> wrote in message
news:uSDuVUhNKHA.5108@newsgroup

> We have an ISMTPOnArrival event sink triggered on
> theISMTPOnArrival_OnArrival event, which is registered by:
> smtpreg.vbs /add 1 onarrival mySMTPEventSink mySMTP.EventSink "mail
> from=*"
>
> This works fine for incoming email but unfortunately does not get
> triggered for outgoing mail. Any ideas why this might be the case?
>
>
>

"david" <david@newsgroup> wrote in message
news:eKYAOADPKHA.4172@newsgroup

> Because the only events are for mail which is Arriving,
> not outgoing.
>
> To make your outgoing mail "arrive", add a second
> SMTP thing to Exchange, and route all of your outgoing
> mail through it, and then on from it in the normal way.
>
> All of your outgoing mail from Exchange goes out
> through your original SMTP thing, into the new one,
> and then out to the world. An event sink on the
> new SMTP thing will see all outgoing mail arriving.
>
> (david)
> *OK, I can't remember what the SMTP thing is called.
> Just go to Exchange, find SMTP, and create a new one.
>

You are referring to an SMTP Virtual Server (VS). To do that, will require
an additional IP address on SBS. THis is because each virtual server
instance will be using port 25, and you can't have additional virtual
servers with the same port on the same IP. It causes a conflict. Therefore
it needs another IP to set it up. Unfortunately, SBS will have trouble
handling additional IPs on a NIC, which will complicate and cause problems
with AD.

Ace

Thank you, I ought to know that :~)

On the outbound connection for the Default SMTP Virtual Server,
change the outbound port.
On the inbound connection for the new SMTP Virtual Server,
change the inbound port.

To change the inbound port, go to Properties, General, Advanced, Edit.
To change the outbound port, go to Properties, Delivery, Outbound
Connections.

Here is a demonstration of the outbound port:
http://www.no-ip.com/support/guides/...port_smtp.html

Don't use port 587 for this. This is not a "Message Submission Agent", and
you don't want agents submitting messages to the new SMTP Virtual Server.
In fact, I would not recommend using port 1025,2025,3025, etc: you don't
need to make it easy for anyone to submit mail to the new SMTP Virtual
Server, it's only purpose is as a loop-back connector for Exchange. Of
course, this SMTP Virtual Server should only accept mail from the one source
anyway.

Note, anther use of changing the Exchange ports is to add a spam filter. Put
a spam-filter SMTP server on port 80, have it forward mail to another port,
and make that port the input port for an input SMTP Virtual Server. Done
this way (1) you don't a separate spam filter machine (2) you don't need a
spam filter that installs inside exchange, (3) you don't have to mess around
with DNS when you take your filter machine offline, (4) your outgoing as
well as your incoming SMTP mail goes through the filter (on port 80)

(david)

"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:OOSxjREPKHA.4796@newsgroup

> "david" <david@newsgroup> wrote in message
> news:eKYAOADPKHA.4172@newsgroup

>> Because the only events are for mail which is Arriving,
>> not outgoing.
>>
>> To make your outgoing mail "arrive", add a second
>> SMTP thing to Exchange, and route all of your outgoing
>> mail through it, and then on from it in the normal way.
>>
>> All of your outgoing mail from Exchange goes out
>> through your original SMTP thing, into the new one,
>> and then out to the world. An event sink on the
>> new SMTP thing will see all outgoing mail arriving.
>>
>> (david)
>> *OK, I can't remember what the SMTP thing is called.
>> Just go to Exchange, find SMTP, and create a new one.
>>

>
> You are referring to an SMTP Virtual Server (VS). To do that, will require
> an additional IP address on SBS. THis is because each virtual server
> instance will be using port 25, and you can't have additional virtual
> servers with the same port on the same IP. It causes a conflict. Therefore
> it needs another IP to set it up. Unfortunately, SBS will have trouble
> handling additional IPs on a NIC, which will complicate and cause problems
> with AD.
>
> Ace
>
>
>