New version of qmail-scanner is out and ready for use ... could be a replacement for 1.20 which still has permission problems. Reproducible: Always Steps to Reproduce: 1. 2. 3. qmail-scanner needs a fully functional version for development use. I would strongly recommend adjust permssions and updating the ebuild to 1.22, it now has better support for clamav the number virus scanner of linux users.
Could someone from the net-mail team really start monitoring this one, please? qmail-scanner is the cornerstone of pretty much... any qmail based AV/A-spam mail gateway...
This permissions error is a big deal, like any mailserver the users of qmail want to know there servers are protected just like any other server. The sooner this is fixed the sooner qmail users will be confortable with there systems again and fully operation when it comes down to the fact that we recieve mail for windows users and what not.
I have just installed qmail-scanner 1.22 by hand ... suprising enough no patches are needed anymore suidperl has been removed and updated. Also permissions are perfect straight up when you run the install by hand. I am working on a new ebuild that I will submit when tested and hopefully we can get it into portage.
Created attachment 29847 [details, diff] new ebuild for qmail-scanner 1.22 new ebuild for qmail-scanner 1.22
problem wiith your ebuild is you based it off of qmail-scanner 1.20 which is nothing but an ebuild full of permsission errors. If you correct it to work properly it would be a great help ... I am working on that issue myself.
*** Bug 47389 has been marked as a duplicate of this bug. ***
this is no longer failed now that qmail-scanner can be fixed with ease by editing your tcp rules. refer to the bug-report on broken permissions
Jory: do _NOT_ close bugs that are still active. I haven't got to putting qmail-scanner 1.22 into portage yet.
qmail-scanner 1.22 is in portage as of 17 Jul 2004. how stable is it?
Closing this bug since the ebuild is already in CVS
