Re: [AMaViS-user] User level querantine maintenance

From: Peter Sørensen <maspsr(at)sdu.dk>
Date: Wed Dec 19 2007 - 02:25:27 EST

Thanks Mark,

I think I have the solution to the setup so FYI here is my thoughts.

All user are registered in Actice Directory. I need to extend the attributes and for this I use ADAM. So when a user is createt in AD they will be given a default SPAM profile in ADAM according to the LDAP schema in amavisd-new.

Authentication - here we use a SingleSignOn based on CAS - so it is fairly simple to integrate in a cgi script.

So now - just some work to be done :-)

Regards

Peter Sørensen
Vid.medarb., IT-service

Tlf. 6550 2858
Fax 6550 2860
Email maspsr@sdu.dk
Web http://intern.sdu.dk/it-service/ansatte/ps-238/ Adr. Campusvej 55, 5230 Odense M

SYDDANSK UNIVERSITET

---

Campusvej 55 * 5230 * Odense M * Tlf. 6550 1000 * www.sdu.dk                                                  

-----Oprindelig meddelelse-----
Fra: amavis-user-bounces@lists.sourceforge.net [mailto:amavis-user-bounces@lists.sourceforge.net] På vegne af Mark Martinec Sendt: 18. december 2007 19:57
Til: amavis-user@lists.sourceforge.net
Emne: Re: [AMaViS-user] User level querantine maintenance

Peter,

> I am considering moving from the amavisd-maia to amavisd-new primarily
> to make sure I have the newest version running.
> I probably still need to be able to let users maintain their own
> quarantine settings (tag-level and maybee other features) but I want
> to keep it fairly simple.
> I have looked into Mailzu but as I see this, it only make it able for
> users to release,delete messages in the Quarantine area.
> What about tag-levels? Do I need to keep theese in a separate database
> if I want to make it possible to lets users change theese?
> And will this be easy to integrate in amavisd-new or should I stick to
> the MAIA version if I want this kind of functionallity?

It mostly depends on how much your users depend on being able to adjust their spam levels, and how frequently they do so. As far as I know the MailZu does not offer it, although it is being requested every now and then and would come handy.

The SQL per-user (or per-domain) settings have their own two SQL tables, which can reside in a separate database, or can be in the same database as SQL logging and quarantining (if that is in use). From a database side it makes sense to keep mostly read-only tables separate from the more volatile and larger r/w tables, but amavisd does not mind one way or another.

The key issue is how can users authenticate to a database (or to its front-end) in order to be allowed to change their settings. Once this is solved, the rest could be a simpleminded cgi-bin script or a more fancy GUI addition to MailZu for example. In small-scale sites a change request could just be a mail sent to an administrator :)

  Mark

---

SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

---

AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/

---

SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

---

AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/ Received on Wed Dec 19 02:26:42 2007