Giampaolo, [...] > But I would like to go a bit further automating some checks I'm used to do > when a message gets banned. > > I would like to: > 1) administratively invoke the ClamAV's sigtool on a banned > part/file; > 2) allow users to automatically invoke a VirusTotal scan on the > banned part(s)/file(s). > > In order to do this, I need access to the banned part or file. At first, > I was thinking of somehow "replicate" the job amavis do in decoding a > message. I see however that amavis does really a good job in this, such > that it seems to me that it could be difficult (and possibly unreliable) > to replicate. Not even to mention the waste of cpu cycles in "duping" this > feature. Or even the fact that duping this feature outside would probably > imply having two configuration points which may easily "get apart"... > > So, is there a way to have amavis kindly "share" these banned contents? > Or the only way we have is to re-decode a message?
I don't see an easy way out, apart from duplicating the code. It may be possible to save away decomposed message parts when quarantining code is invoked. Perhaps an alternative approach may suffice: do a fake release (i.e. to a dedicated/dummy/null recipient, using a $release_method or $requeue_method setting) and let the released message be fed to a MTA port where a pre-queue amavisd instance is sitting. This way you could check the status reported by amavisd-release, which may suffice for your needs. Mark ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
