Bugzilla Bug 211672

Since qmail-scanner has supposedly been fixed in portage recently, it now uses
some wrapper around the original perl script. The docs should have been fixed
as well:

 * Messages for package mail-filter/qmail-scanner-2.02-r1:

 * Adding items to the SILENT_VIRUSES list
(bagle,beagle,mydoom,sco,maldal,mimail,novarg,shimg,bugler,cissi,cissy,dloade,netsky,qizy)
 * To activate qmail-scanner, please edit your
 * /var/qmail/control/conf-common file and set:
 * export QMAILQUEUE=/var/qmail/bin/qmail-scanner-queue
 * Or place it in your tcprules file.
 * Please note that it was a call to qmail-scanner-queue.pl before,
 * but this is now changed to use a wrapper to improve security!
 * Once you have changed to the wrapper, you can remove the setuid 
 * bit on qmail-scanner-queue.pl
 * If this is an upgrade from <=2.0.1 the home directory of the qscand
 * user is changed. Please update it manually to /var/spool/qscan
 * or remove the user and emerge again this package
 * To allow clamav integration comment-out in /etc/clamd.conf:
 * AllowSupplementaryGroups putting yes.
 * After that, restart clamd with
 * /etc/init.d/clamd restart



However, I do see also:

# grep scanner /etc/tcprules.d/*
/etc/tcprules.d/tcp.qmail-qmtp:# If you are using qmail-scanner, this line here
is the correct one to use
/etc/tcprules.d/tcp.qmail-qmtp:#:allow,QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl"
/etc/tcprules.d/tcp.qmail-smtp:# If you are using qmail-scanner, this line here
is the correct one to use
/etc/tcprules.d/tcp.qmail-smtp:#:allow,QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl"
#

Please fix the two files in /etc/tcprules.d/.

Fixed. You should again emerge netqmail to get the changes.
Thanks

 * Messages for package mail-mta/netqmail-1.05-r8:

 * QA: stop using the bindnow-flags function ... simply drop it from your
ebuild

please open a new bug for a new issue.

this particular error message is being emitted by recent flag-o-matic.eclass
versions and is not related to the problem described in this bug. if you think
it is related, then please provide a more elaborate error description.

thanks :)