Hi Stephen, On Wed, Mar 02, 2005 at 08:46:15PM -0500, Stephen Gran wrote: > This one time, at band camp, Anand Kumria said: > > Hi, > > > > If you put the attached file in > > > > /etc/exim4/conf.d/main/20_clamav-daemon_socket_path > > > > It will automagically enable clamav for those Exim users who run with > > a split configuration. This will currently only work with the > > exim4-heavy-daemon so you would need to depend upon that. > > You do see the problem of depending on a particular version of an MTA, > right?
No, I don't. > That will prevent others from running it with Postfix, sendmail > etc. No, it won't. What about Depends: mail-transport-agent | exim4-daemon-heavy (>= 4.44) Conflicts: exim4-daemon-light (<=4.44) > I think this is probably not going to work automagically - It's > easy enough to drop the single line in, but (think about dpkg conffile > handling here) what if the admin decides they want to run it on an inet > socket instead? They get prompted forever. 'forever' being the infrequent times they upgrade clamav-daemon, yes What is the common mail server case? Guy setting up a machine wanting to perform greylisting, spamassassin and antivirus checks at smtp time? Or organisation setting up cluster of machine with lots of load-balancing doodads all over the place. I don't think there is anything wrong with optimising for the common case here. > And, it won't be turned on > automagically, since it will never be called by the data ACL. Well for Exim 4.5 it can be in the mime ACL but the data ACL stuff I was going to wait until clamav-daemon was ready then reportbug on the exim4 maintainers. > I am also > not allowed to reload exim from the postinst of my package, so nothing > would happen at all. Yes, you are; see 'invoke-rc.d'. It'll do the right thing. > No, all in all, I think the extra integration required (making sure the > directories exist, not adding it if exim4-daemon-light is installed, > etc) are not worth it to save an admin a single line of cut-n-paste. Well the exiscan patch is integrated upstream into exim 4.50, so it is likely that exim4-daemon-light will have right thing in future. > As I recall, the stock packages of exim4 already come with all the clamd > stuff present but commented out, so it really would only save the admin > the trouble of removing a few comments. No, they don't. Which is basically my bug; setup of clamav-daemon using exim4 is harder than it should be. If README.Debian said "for Exim if you are using the split configuration, clamav is enabled. You will need to modify the file /etc/exim4/conf.d/acl/40_... and put the contents of /path/to/example before this are checked. If you are using either the template of monolithic configuration you will also need to put the enable line from /etc/exim4/conf.d/main/20_clamav-daemon_socket_path in the main section" > I think this should be closed, but if it is important to you as a > feature request, I am happy to leave it open as a wishlist bug, but I am > afraid I will tag it 'wontfix' Personally I think 'wontfix' is a bit of a copout. Especially for a wishlist bug. But how you triage is your own problem. One package that I think you should take a look at is how greylistd works and interacts with Exim. It has similiar problems and has some interesting solutions. > Thanks for reporting, Thanks for responding; nowadays fewer and fewer developer even do that courtesy to reporters. I appreciate I pretty much rejected outright your response but when I look at greylistd the nice thing is it basically 'Just Works'. In contrast for clamav-daemon, the package didn't have information for me to put in the right rules and enable things. Eventually I would like it to be (essentially) 'apt-get install clamav-daemon' and you have virus checking with exim4. I believe this the first step in getting there. Cheers, Anand -- linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX Canberra, Australia - http://lca2005.linux.org.au/ - Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
