"Micheal Espinola Jr" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Chris Norman wrote: >> I run four ASSP instances on separate IPs pointing back to a single >> MTA instance (Merak). In this way, each domain has its own settings. >> I used to have all the domains on one ASSP instance I must say its >> effectiveness improved when I divided it up. No longer was one >> person's HAM arriving in someone else's mailbox as SPAM. > > A solution to this that I have always had running in the back of by mind > would be to change the format of the whitelist from a pair (address, > expiration) to a triplet (external address, internal address, expiration). > > Of course, I have no idea what kind of work it would require or the > complications that it would cause, but it seems to me to be a reasonable > way to have a per-use whitelist. And I suppose if you wanted to make it > per-domain, you could just drop the LHS info and only list the domain > instead of the entire internal address.
The biggest problem I foresee with a per-user whitelist is aliases. Many people have several aliases (ex: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], etc. etc. etc), and a per-user whitelist would mean a seperate whitelist for each of those aliases. Unless the Local Address FlatFile (or somehting similar) was modified/created to include which addresses were aliased to which. And I don't know if you can configure an LDAP directory to serve that information instead of using a flatfile. Just a couple of thoughts.... Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
