Tom, > Obviously it does, but it's too much data to store and scan, considering > the amount of mails that comes through our system. > The optimal format would be to store date, time, server, action > and spam sore / virus name
The closest thing is to modify sub save_info_preliminary and save_info_final, and throw away all that is not needed, i.e. modifying the list of arguments to SQL execute calls, and the associated ins_msg and upd_msg SQL clause templates in %sql_clause. > I tried doing: > 'ins_rcp' => undef, > 'ins_quar' => undef, > 'sel_quar' => undef, > 'sel_penpals' => undef, > But that doesn't work, just throws errors when mail comes in: > (!!)TROUBLE in process_request: sql exec: err=16, S1000, DBD::mysql::st > bind_param failed: Illegal parameter number at (eval 51) line 160 Yes, this was discussed recently, and I promised the next 2.5.0 (pre?) release will allow these clauses to be selectively disabled (now it is all-or-nothing). I have this part of the code done, but is not yet publicly available. > Even if it did work, it's still two SQL queries per mail, one being an > update, but that's something I can live with - I think. It is in two parts (insert and update) because this way we can guarantee the generated mail-id is unique among the set of records in a database. Generating mail-id must be done very early during processing, but information becomes available only late, which is why an update is done late. Mark ------------------------------------------------------------------------- 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 _______________________________________________ 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/
