Amavisd question

Alan Davies via amavis-users amavis-users at
Mon Sep 2 15:56:37 CEST 2013

Hi Benedict,

Thanks for your recommendation - I've modified my definition. I've got something similar that only releases from local host anyway  :) I'll definitely checkout mailzu though, that looks interesting from the screenshots on sourceforge!

I've checked my logs but I am still getting no recognized protocol name 0.

Kind Regards,
Alan Davies
Business Support 

ITCS - IT Computer Services
Bridgend Ind Estate
CF31 3TP 

Tel:   08456 444 200
Fax:  01656 660 016 

-----Original Message-----
From: Benedict White [mailto:Benedict.White at] 
Sent: 02 September 2013 14:44
To: amavis-users at
Cc: Alan Davies
Subject: RE: Amavisd question

-----Original Message-----
From: Alan Davies [mailto:adavies at]
Sent: 02 September 2013 14:42
To: Benedict White
Subject: RE: Amavisd question
>My AM.PDP settings are as follows:
>$interface_policy{'SOCK'} = 'AM.PDP-SOCK'; # only applies with 
># Use with amavis-release over a socket or with Petr Rehor's amavis-milter.c # (with amavis-milter.c from this package or old amavis.c client use 'AM.CL'):
>$policy_bank{'AM.PDP-SOCK'} = {
>  protocol => 'AM.PDP',
 > auth_required_release => 0,  # do not require secret_id for amavisd-release };

Do you need to have the release so open? As in, do you need to have emails released without the secret ID? I use MailZu for quarantine Management (albeit our own patched version) and that supplies both Mail-id and secret-id for quarantine release.

Mine looks like this:
$policy_bank{'AM.PDP'} = {
    protocol => 'AM.PDP',
    inet_acl => [qw( )],

This allows release from requests from the local machine only, but does require the secret ID. You could just hash out the auth_required_release line as well.

Kindest regards,

Benedict White

More information about the amavis-users mailing list