I'm still not sure how that would work. We do have Active Directory, but our users aren't in it. Only our technicians are in Active Directory to administer the servers. This is on purpose for better security. The users, and their email settings, are all stored in the database. The users also have the ability to manually create/edit/remove any user accounts (email accounts) as needed through the MailSite administration screen (a web page).
So, with your method, I would have to rewrite or integrate with the vendor's webmail administration interface so that it would add an active directory account, add mail attributes to it, when they add a new account, update the Active Directory account when they edit it, and make sure I delete when they delete the user's account.
I'm thinking it would still be easier to not worry about integration in BrightMail or in MailSite. If i create a .NET web-based project and read from the MailSite database to allow login and what report content that is returned, and then read the BrightMail database or filesystem for the actual report content it sounds easier.
If MailSite or Symantec drastically change their format or environment, I "may" not have to change my code if the file system or database don't change. And since it is outside of their systems, I don't run the risk of 'messing them up'. And you and I both know that Symantec tries to refuse support for custom integration (which I don't want to even get started on).
Thoughts? Suggestions? Ideas? I don't like doing stuff the hard way, so I'm open for anything you can think of.