[Bug 151850] Re: clamav-milter postfix defaults fail
** Changed in: clamav (Debian) Status: New = Fix Released -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
** Changed in: clamav (Debian) Status: Unknown = New -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
clamav (0.91.2-3ubuntu2) gutsy; urgency=low * Correct Postfix socket location for clamav-milter in debian/clamav-milter.default (LP: #151850) -- Scott Kitterman [EMAIL PROTECTED] Fri, 12 Oct 2007 11:13:10 -0400 ** Changed in: clamav (Ubuntu) Status: Fix Committed = Fix Released -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
Note that by default that entry is commented out. Please give me the clamav milter related bits of your Postfix main.cf and master.cf so I can try to replicate the situation (I use Postfix with clamav, but use clamsmtp so I don't have a clamav-milter setup handy). -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
Adding the filename to the default option makes sense and seems to be the only thing missing after you do what's in README.Debian. ** Changed in: clamav (Ubuntu) Importance: Undecided = Low Assignee: (unassigned) = Scott Kitterman (kitterman) Status: New = In Progress -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
Uploaded. ** Changed in: clamav (Ubuntu) Assignee: Scott Kitterman (kitterman) = (unassigned) Status: In Progress = Fix Committed -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
There are a couple other issues with the init script that will case it to fail with postfix chroot: - It doesnt give the postfix user any write permissions to the socket (which is dynamically created/destroyed). - There's a race condition where it doesn't wait for the socket file to be created, so the chgrp command actually fails silently. I've made the following modifications which, although not particularly dynamic, make it work properly on my setup: while [ ! -e $SOCKET_PATH ]; do sleep 2 done if [ $ret = 0 ] [ -e $SOCKET_PATH ] [ $USE_POSTFIX = 'yes' ]; then chgrp postfix $SOCKET_PATH chmod g+w $SOCKET_PATH fi -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 151850] Re: clamav-milter postfix defaults fail
Even if I setup Postfix to point to the actual socket, there are still permissions issues to deal with (that I haven't figured out yet). Unless I can figure a general solution to getting clamav-milter working with Postfix that won't break using it with Sendmail, I'm going to leave this alone for Gutsy. If you unchroot Postfix it will find the socket file in the normal location. -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
README.Debian gives instructions that I think work through the permissions issues. I'm not comfortable this close to release with automagically messing with permissions issues. The Debian maintainer and I have discussed closer cooperation on clamav. I've added a better set of options for Postfix to my list of things to discuss with him. Thanks for your contribution. In the meantime Debian has the exact same issues, so if you want to file bugs against clamav-milter in the Debian BTS, that would help get this on his radar screen. -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
Yes, well my rationale was that if an example is going to be included that one can uncomment and use, it should probably work. :) I can solve the problem fairly simply... I leave the path as suggested, but add an actual socket file name to it: SOCKET=local:/var/spool/postfix/clamav/clamav.ctl I then manually create the clamav directory (as root). My current working system has the clamav dir, plus the socket, owned by clamav and in the postfix group, mode 775. This should be fairly trivial to do with the new init script since it already has a variable specifying postfix. -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446404 -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151850] Re: clamav-milter postfix defaults fail
** Also affects: clamav (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446404 Importance: Unknown Status: Unknown -- clamav-milter postfix defaults fail https://bugs.launchpad.net/bugs/151850 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
