Clayton, > I notice in the Release Notes as of 2.6.1 the following decoder entries > are commented: > > # ['asc', \&Amavis::Unpackers::do_ascii], > # ['uue', \&Amavis::Unpackers::do_ascii], > # ['hqx', \&Amavis::Unpackers::do_ascii], > # ['ync', \&Amavis::Unpackers::do_ascii], > > However, in the provided configuration examples with the 2.6.4 source > the folowing configuration files included do not have them commented out: > > amavisd_conf-sample > amavisd.conf > > While the amavisd-conf-default does have them commented.
True. The inconsistency has been pointed out before, will be fixed with the next release. > I am migrating some existing setups from 2.5.4 and wanted to be sure > that it was safe to comment the four entries above as I migrate the > config to a 2.6.4 safe config. Yes, just comment them out - or not. The decision is yours: do_ascii can decode some unusual messages - which can be useful, especially if a virus scanner with deficient decoding is used - but on the other hand the underlying perl module has caused some grief in the past (crashes or loops or security vulnerabilities), so I have decided to keep it disabled by default. Mark ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ 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/
