amavisd-release(2.6.5) and banned files ?

[Jernej Porenta]

On Apr 19, 2011, at 8:11 AM, Jarno Huuskonen wrote:
> 
> Hello,
> 
> I may have found a possible bug with amavisd-release (v.2.6.5)
> and banned files:
> 
> # amavisd.conf:
> ---------------
> $QUARANTINEDIR = '/var/spool/amavis/virusmails';
> @addr_extension_banned_maps     = ('banned');
> $banned_files_quarantine_method   = 'local:banned-%m';
> $final_banned_destiny     = D_DISCARD;
> 
> 
> # log:
> ------
> Apr 18 15:44:29 server3 amavis[10355]: (10355-01) Blocked BANNED (application/octet-stream,.exe,.exe-ms,putty2.exe), MYNETS LOCAL [ip.ad.dre.ss] [ip.ad.dre.ss] <sender at mydomain.fi> -> <recipient at mydomain.fi>, quarantine: banned-ncBYAoKPgaHx, mail_id: ncBYAoKPgaHx, Hits: -, size: 2484, 145 ms
> 
> 
> # /var/spool/amavis/virusmails/banned-ncBYAoKPgaHx
> ---------------------------------------------------
> ...
> Delivered-To: banned-quarantine
> X-Envelope-From: <sender at mydomain.fi>
> X-Envelope-To: <recipient at mydomain.fi>
> X-Envelope-To-Blocked: <recipient at mydomain.fi>
> X-Quarantine-ID: <ncBYAoKPgaHx>
> ...
> 
> Now if I try to release the banned message (with amavisd-release from 2.6.5):
> # amavisd-release banned-ncBYAoKPgaHx
> 450 4.5.0 Failure: File /var/spool/amavis/virusmails/ncBYAoKPgaHx does not exist at (eval 96) line 385, <GEN19> line 3.
> 
> (amavisd-release(2.6.5) seems to send the banned filename as ncBYAoKPgaHx).
> Dumping the @query that amavisd-release sends:
> $VAR1 = 'request=release';
> $VAR2 = 'mail_id=ncBYAoKPgaHx';
> 
> 
> If I use amavisd-release from amavisd-new-2.6.3
> everything works OK:
> # ./amavisd-release-263 banned-ncBYAoKPgaHx
> 250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 459FA1983
> And the query is:
> $VAR1 = 'request=release';
> $VAR2 = 'quar_type=F';
> $VAR3 = 'mail_id=ncBYAoKPgaHx';
> $VAR4 = 'mail_file=banned-ncBYAoKPgaHx';
> 
> Is this a bug in amavisd-release or is there something wrong with
> my config etc. ?

AFAIK, Mark is currently on vacation so don't expect any fixes any time soon.

If you are really affected by that bug, I would recommend downgrading to 2.6.4, checking the RELEASE_NOTES and greping through the diff.

regards, Jernej