> Ok, What you're trying to do here is admirable and well thought out.  I

Thanks, we try.  :)

> different records such as [EMAIL PROTECTED] ?  That way you
> could assign each of your 4 account types a separte virtual domains within
> IMail.  Each different account would have its' own virtual domain thus
its'
> own kill.lst/rules.ima files.  They would also be able to send mail to the

I'm not sure I totally understand this part.  The account types and their
permissions are controlled through our ASP/COM front-end.  The only reason
we would use virtual domains is for more generalized organizational control.
For example:

houstonisd.domain.com, dallasisd.domain.com, montgomeryisd.domain.com,...
(with the vague objective of using dedicated servers for the larger
institutions)

> setup for IMail.  One could do further filtering and control by porting
the
> incomming email to a program alais, such as a batch file, that would scan
> the "From" and/or "To" addresses and then forward the email accordingly.

This is what I've decided to work on today.  It's really the only way to get
everything we need.  After a couple of tests, it looks like all I have to do
is check the From field, parse the X-RCPT-TO line, and append the email to
the *.mbx file.  It "looks" straightforward.

The advantages to this seem to outweigh the other options.  After much
discussion, it's also been determined that outgoing filtering on a per user
basis is a "must have".  Since there is only 1 orules.ima file for the whole
domain, it would be impractical to rely solely on the one orules.ima file
for outgoing mail of 5,000+ users.

We realized we definitely needed outgoing filtering.  This will effectively
prevent most students from spamming or sending unsolicited email to those
outside of our system.  Also, online behavior problems and communications
are currently treated as real world behavior problems in the school.
Cussing in an email will get the same treatment as cussing in class.

Our only concern with the program alias is the processing overhead.  Is
there a hard limit to the number of simultaneous program alias spawned
processes?  If we break the 10,000 user mark (which will come in Spring
2003), will message delivery speed suffer significantly?  I guess we'll just
have to see.

Thanks,
Norm



To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/

Reply via email to