> > There are E-Mailaliases in a LDAP-Tree (I don't know if I can query the > > LDAP) > You mean you don't know if you can query the LDAP from within DSPAM? Or do > you mean something else?
exactly! > Then I would suggest to use either a global or a merged group. > > > The next step is to use the LDAP information to maintain email aliases > > with one dictionary and quarantine (maybe shared,managed) > For all users? I would not do that. Maybe one per domain but not a global > one. I meant account based (One email account whith several email addresses) but my test environment knows these aliases without any groups, so this step isn't nessesary. > > And it should be maintainable with a frontend (not written yet). > Why not using the DSPAM Web-UI? The Web-UI is only for the End-User. I want to manage/ create groups and users with a front end. Maybe I can retrieve the user and Passwords from the ldap tree. But I think I need a frontend for group administration > I think from the viewpoint of speed any setup is faster the SA. Sounds good :) > > Exists something like a > > managed, inoculation group? > > I don't think so. But maybe Jonathan knows more? I think I should try this. > > In general is a shared group or a combination inoculation/ classification > > the > > better choice? > > I personally think a global or merged group is a better choice. I use > merged since merged allows me to train periodically the merged group and > have influence on the filter even if the user has trained his filter very > well. can a user be a member of a merged and a shared group? Or doesn't nake that sense? regards Sven
