Riaan,
> > > So, how to do it? 'sql_clause'
> > > IS a policy-able variable, but I'm not sure amavisd-new would be
> > > stable if that is set to undef in a policy declaration.
> >
> > That could work, but I never tried it. Please see if it works,
> > and if it doesn't I'd consider it a bug and f
>
> > So, how to do it? 'sql_clause'
> > IS a policy-able variable, but I'm not sure amavisd-new would be
> > stable if that is set to undef in a policy declaration.
>
> That could work, but I never tried it. Please see if it works,
> and if it doesn't I'd consider it a bug and fix it.
I do find
Riaan,
> Running 2.4.5, I do not want to log the details of outbound mail to
> sql (syslog is enough). Inbound, being processed for spam too, is
> great in sql, but outbound just litters my db.
Sorry to disappoint you but this is not currently possible,
nor planned. I see the following reasons:
hello Mark and amavis-users,
I'm trying to set up a nice all-in-one in- and outbound solution here,
and am a bit stuck:
Running 2.4.5, I do not want to log the details of outbound mail to
sql (syslog is enough). Inbound, being processed for spam too, is
great in sql, but outbound just litters my
