Michael Hall wrote:
Per RFC 2252:
6.4. Boolean
( 1.3.6.1.4.1.1466.115.121.1.7 DESC 'Boolean' )
Values in this syntax are encoded according to the following BNF:
boolean = "TRUE" / "FALSE"
Boolean values have an encoding of "TRUE" if they are logically true,
and have an encoding of "FALSE" otherwise.
originals), amavisd takes that value for good. In amavisd.conf-sample it
is written:
# - for values which are interpreted as booleans, it is recommended
# to use 1 for true, and 0 or undef or '' for false.
# THIS IS DIFFERENT FROM OLD AMAVIS VERSIONS where "no" also meant false,
# now it means true, like any nonempty string does!
The value of 'amavisVirusLover' or 'amavisBypassVirusChecks' must be
either 'TRUE' or 'FALSE' (not 0, 1, y, n, true, false) per the RFC,
actually this applies to any of amavis* LDAP boolean variables.
Oh, man! Using all uppercase boolean values TRUE/FALSE it works. This is
in contrast with amavisd.conf-sample (see # commented lines above), at
least when dealing with Sun's Directory Server.
Thanks,
Paolo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&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/
