Curtis Doty wrote:
> Here's a couple of tweaks needed to quiet down the unmatched noise a bit:
>
> --- amavis-logwatch.orig2007-09-17 21:07:47.0 -0700
> +++ amavis-logwatch2007-09-21 09:43:46.0 -0700
> @@ -458,6 +458,10 @@
> or ($p1 =~ /^updating snmp variables/)
> + or ($p1 =~ /^AM.PDP /) # this appears to be always two spaces
^^^
> or ($p1 =~ /email.txt no longer exists, can't re-use it/)
^^^
Don't forget to quote literal dots: \. is a dot, a . matches any character.
Mark
---
Yesterday MrC said:
> Mark Martinec wrote:
> >
> > Seems the only one that is actively maintained is the logwatch:
> > http://www.mikecappella.com/logwatch/
> >
>
> Benedict - feel free to drop me a line if you have questions or
> improvement requests. I have just made some recent experimental
Hi all,
I would like to setup a global sneder whitelist using MySQL (not per
recipients), but I don't see how to write the correct SQL lookup as
amavisd-new seems tobe very dependent on the sql_policy lookup (it never
hit my sql_select_white_black_list because it don't have an answer to
the policy
Ian,
> > Yes, by-recipients setting is available:
> > @bypass_header_checks_maps = ( list of lookup tables as usual );
>
> So the lookup table is simply regex matched?
If you use a regexp-type of a lookup table, then yes.
All types of availabe lookups are explainded in README.lookups .
> I.E. I
