> Which would mean that either you have a hash collision, would would be
> very unprobable, or the first mail that got hashed and cached came
> from a whitelisted sender.
Whitelisting should have no effect there, it does not propagate through cache,
white/blacklisting is always re-checked on per-r
Hi,
> We get this (or something like it) in the maillog on a regular basis:
>
> Jul 30 06:35:28 spamhost amavis[1516]: (01516-18) cached
> fa63a14bcc69e31f69e554579f645969 from
> <[EMAIL PROTECTED]> (1,0,1)
amavis can keep a cache hashes of mails with the corresponding diagnosis
(virus/clean/spa
We have a Postfix(2.1.5)/Amavis-new(20030616)/SpamAssassin(3.0.2) setup
on RH9. Our setup works very well with one exception:
We get this (or something like it) in the maillog on a regular basis:
Jul 30 06:35:28 spamhost amavis[1516]: (01516-18) cached
fa63a14bcc69e31f69e554579f645969 from <[EMA
