Categorizer event sink / routing event sink

Categorizer event sink / routing event sink

Post by jordan.r.s » Sat, 16 Jul 2005 12:08:35


I want to reroute all email from a particular group of internal users
through another (non-Exchange) server which will pre-process their
email before it's sent to its final recipient.

The best way I can see to do this (I've only just started learning
about the way Exchange works though) is:
- create a Categorizer event sink to look up the group membership of
the sender. - if they belong to the group I want to reroute emails from
then add some kind of attribute to the email.
- create a Routing event sink to reroute the email based on the
attribute set in the Categorizer event sink.

Is this the best way to do it? I can't find much info on creating
categorizer sinks (or routing sinks for that matter: what kind of info
do I have access to in a routing sink?)

-- Jordan
 
 
 

Categorizer event sink / routing event sink

Post by Chris Scha » Tue, 19 Jul 2005 14:00:12

On 14 Jul 2005 20:08:35 -0700, XXXX@XXXXX.COM hired a team
of monkeys to write:


Writing categorizer event sinks is non-trivial and there's not a whole
lot of documentation out there[1]. Can you describe your needs a
little more? Do messages sent by these users need to be processed if
the recipients are internal, or only if they are destined for external
recipients? If it's just to external recipients you may be able to
bypass the need for an event sink altogether and use restrictions on
SMTP connectors to force mail from these recipients through a specific
connector which routes their outbound Internet e-mail to a smart host
(your external server) for processing.


[1] And if it's also for internal mail you'd potentially need to write
several event sinks to achieve a fluid and robust system.

--
Chris Scharff
Messaging Services Architect
MessageOne

Emergency Mail System: http://www.yqcomputer.com/

 
 
 

Categorizer event sink / routing event sink

Post by jordan.r.s » Wed, 20 Jul 2005 08:36:44

The email only needs to be processed if it's to an external recipient,
and coming from a user in a particular Active Directory group.

How would it work using restrictions on SMTP connectors? It looks like
you can only reject mail. If one connector rejects an email does
Exchange then try another connector (that has a higher cost) or does
the email sending just fail?

- Jordan
 
 
 

Categorizer event sink / routing event sink

Post by Chris Scha » Wed, 20 Jul 2005 09:12:49

On 18 Jul 2005 16:36:44 -0700, XXXX@XXXXX.COM hired a team
of monkeys to write:


If a user (or group) is not allowed to use a particular connector, if
there is another connector valid for that address space, they will use
it instead.

--
Chris Scharff
Messaging Services Architect
MessageOne

Business Continuity That Makes Business Sense
http://www.yqcomputer.com/
 
 
 

Categorizer event sink / routing event sink

Post by jordan.r.s » Thu, 21 Jul 2005 08:26:27

Thanks for the help.

-- Jordan