Thanks for the response, Mark!
My idea was to still have all the sender/recipient/message information
but only for those e-mails that are quarantined. Thus, we would want to
call save_info_preliminary and save_info_final whenever a message is
being quarantined. The users could then control that
Tenyo,
> > Hi. I'm working on a custom Amavis/SA quarantine solution using MySQL,
> > and I was curious if there's a way to disable the SQL reporting while
> > still having spam get quarantined?
Control knob is not provided to turn off reporting and still use SQL
for quarantining, although both m
It looks like amavisd follows these steps for SQL reporting/quarantining:
in check_mail sub (in the order indicated):
1. save_info_preliminary()
1.1. find_or_save_addr()
1.1.1. ins_adr (inserts info into maddr table)
1.2. ins_msg (inserts preliminary data into msg table)
2. do_not
Hi. I'm working on a custom Amavis/SA quarantine solution using MySQL,
and I was curious if there's a way to disable the SQL reporting while
still having spam get quarantined?
My understanding is that as soon as you specify @storage_sql_dsn, Amavis
starts logging all e-mails. For right now, I'm
Hi. I'm working on a custom Amavis/SA quarantine solution using MySQL,
and I was curious if there's a way to disable the SQL reporting while
still having spam get quarantined?
My understanding is that as soon as you specify @storage_sql_dsn, Amavis
starts logging all e-mails. For right now, I'm
