> Depending if a message content category has been cached or not, amavis
> alternates the log it sends:
> First hit:
> # amavis: (30689-14) Blocked INFECTED (310, Eicar-Test-Signature),
> [192.168.50.162] [192.168.50.162] <virus-sender@...> ->
> <virus-rcpt@...>, quarantine: L/virus-L2pjxyYgIrRe, mail_id:
> L2pjxyYgIrRe, Hits: -, size: 1072, 118 ms
> Cached hit:
> # amavis: (11257-01) Blocked INFECTED
> (Eicar-Test-Signature(44d88612fea8a8f36de82e1278abb02f:68)), LO
> Would it be possible to _harmonize_ the log output and have the cache
> reference more isolated like this:
Right, this is just one of the consequences of caching results.
Other may be even more sinister: with personalized spam checking,
with getting back a signed message from a remote mailing list,
or dealing with virus checkers reporting spam.
...which is why I ditched results caching with 2.7.0-pre9.
release notes in 2.7.0-pre9:
- caching of virus and spam check results based on a mail body hash has been
removed. It was very beneficial years ago when virus storms were common
and spam was not personalized. Nowadays (2010) the feature barely pays
for itself (savings are comparable to additional processing needed), and
is incompatible with per-recipient spam checks (as introduced with this
version), and incompatible with DKIM verification on locally originating
and signed mail being returned from a mailing list. Rather than trying
to fit a square peg into a round hole, the feature is now dropped.
Associated configuration variables are still declared for compatibility,
but have no effect: