amavis-release results in another banned message

[Heath Young]

Ah the $release_method for this setup was undefined. Which, as I
understand it defaults to the $notify_method. Which as you point Ralf
runs through the filtering again in this setup. I set it to the correct
path and we are all good.
 
Thanks for your help Ralf,
 
Heath Young
Denver Public Library

>>> Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> 2/27/2013 12:47 AM
>>>
* Heath Young <HYoung at denverlibrary.org>:
> I am trying to use amavis-release to release a quarantined message.
This source message was banned because of the following extensions:
>  
> .txt,myschema.xsd
>  
> When I try to run the release command, amavisd bans the resulting
message as well.
>  
> What do I need to do to release this message?

Which release_method are you using? If the release path is subject to
the same filtering, it won't work.

-- 
Ralf Hildebrandt                   Charite Universitätsmedizin Berlin
ralf.hildebrandt at charite.de        Campus Benjamin Franklin
http://www.charite.de              Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.amavis.org/pipermail/amavis-users/attachments/20130227/b912e2fd/attachment.html>