Link to home
Start Free TrialLog in
Avatar of JasonBigham
JasonBigham

asked on

Suggest an implementation to segregrate SMTP traffic

Currently, I am wrapping up an Ex5.5 to 2000 (standard edition) migration... any day now. End result will be a single site in native mode.

What I have is a bunch of employees, and three pseudo employees. These 3 are here as a partnership with another company. Due to regulations, I am required to send all incoming/outging SMTP traffic through a 3rd party monitorig service for just these 3 pseudo employees.

For security reasons, I want to ONLY send these 3 pseudo employees SMTP internet traffic through this 3rd party monitoring service, while leaving the other 300+ as is. All the employees need to communicate with each other normally, have access to the same address lists, etc.

The 3rd party SMTP relay we will be using for these 3 pseudo employees for regulatory purposes.
http://www.amicus.com/products_email.html

I invision two SMTP connectors, but I am unclear as to the implementation. If they have the same cost, they will load balance. Thus if I restrict access, they may get rejections on occasion if I allow/disallow SMTP usage accordingly on each SMTP connector. I cannot create addition stores, as I have the standard version.





ASKER CERTIFIED SOLUTION
Avatar of OneHump
OneHump

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of OneHump
OneHump

I didnt notice that you were the guy who suggested the event sink in another post.  :)

If you know how to write them then you're problem is a piece of cake.  If you do go that route, I'd appreciate knowing how it turned out.  


OneHump
Avatar of JasonBigham

ASKER

Yes, a new server/routing group was my initial plan... I should have stated that. I am actually cleared for budget on this plan as well, just seems a waste for just 3 users...