> Rick penned: > > > Couldn't one set up > > 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. > > FWIW, this is precisely what I did for a university. It works very well but > there was the inevitable initial load of user complaints about having to > change [the domain portion of] their e-mail address ;) > > Guy
"I see." said the blind man to his deaf dog. I guess my problem is that even if I just count students, one of the schools we are working with has ~3,000 students. With only 1 orules.ima file to filter contacts and such, performance and maintainability suffer. The way our system works is a student requests to communicate with a specific email address. Depending on how their parents have set their permissions, a school admin, teacher, or parent approves the contact request. At that point, we add the email to the whitelist of emails that student can communicate with. If the approval is taken away, the contact must be removed from the orules.ima file as well. Since I haven't written the code to hit the orules.ima file yet and I'm not even sure how to load test this, I'm not sure if this is a problem. Why all the filtering? The schools we are working with are K-12. 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/
