Mark, in amavisd.conf-defaults are shown defaults for the following: # $banned_admin = [EMAIL PROTECTED]; # for compatibility with pre-2.2.1 # $bad_header_admin = [EMAIL PROTECTED]; # for compatibility with pre-2.2.1
# @banned_admin_maps = (\$banned_admin); # @bad_header_admin_maps= (\$bad_header_admin); I don't think this works for $banned_admin and $bad_header_admin. If it worked, wouldn't assigning: $virus_admin = '[EMAIL PROTECTED]'; also assign '[EMAIL PROTECTED]' to $banned_admin and $bad_header_admin? It does not. # @virus_admin_maps = (\%virus_admin, \$virus_admin); http://marc.theaimsgroup.com/?l=amavis-user&m=112555299108038&w=2 I think $banned_admin and $bad_header_admin should be configured in the same manner as $virus_admin in amavisd.conf and amavisd.conf-sample and the defaults for $banned_admin and $bad_header_admin should instead be undef, just as $spam_admin and $virus_admin are now. In amavisd (and amavisd.conf-defaults), because it does not seem to work, I just don't think this serves any purpose: $banned_admin = [EMAIL PROTECTED]; # compatibility $bad_header_admin = [EMAIL PROTECTED]; # compatibility Gary V ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
