Peter, > I have been running amavisd-maia for the past 4 years with > just minor problems. We are in the state of redesigning the > system due to increasing load. > > Furthermore the MAIA Web interface tends to be more complicated > than our users like. So we consider going back to use amavisd-new > and the integrated quarantine mechanism inhere. > > What Our user would like is the ability to find and release > spam and see what has happened to mail sent/received to their > account. > > We have a logtrace system dealing with the last part but need a > simpler interface to the first part.
Also a SQL log may be useful for that purpose. > I have looked into the MailZu interface and it might be useful in Our > setup. > > We have 3 running instances af amavis quarantining throug SQL(mysql) to ONE > DB. Will there be any problems in this setup towards using amavisd-new and > MailZu? Or to put it different - how does amavisd-new create a uniq > identifier in the DB? I don't see a problem there. Multiple instances of amavisd can use the same SQL database: transactions are used, SQL server ensures locking, and amavisd ensures that generated mail-id keys are unique across all records currently in a database, regardless of how/where they were generated. If there is a contention on a tentative attempt to enter a record in a database, amavisd generates a new random mail-id and re-tries repeatedly. Releasing from a common quarantine can be done by any amavisd process with an access to a database. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
