[packaging] [Bug 3565] New: Path to calmd.sock differs between /etc/amavisd/amavisd.conf and /etc/clamd.d/amavisd.conf

Kolab Bugzilla noreply at kolab.org
Tue Sep 2 19:56:39 CEST 2014


            Bug ID: 3565
           Summary: Path to calmd.sock differs between
                    /etc/amavisd/amavisd.conf and
    Classification: Kolab Server
           Product: Kolab Server
           Version: 3.3
          Hardware: PC
                OS: Enterprise Linux 7
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: packaging
          Assignee: packaging-bugs at lists.kolabsys.com
          Reporter: mail at swalter-it.com
       Ticket Type: ---

After a fresh install on CentOS 7.0, virus checking fails, resulting in mails
being marked as "***UNCHECKED***". In the /var/log/maillog, messages appear
such as the following:

amavis[15056]: (15056-05) (!)connect to /var/spool/amavisd/clamd.sock failed,
attempt #1: Can't connect to a UNIX socket /var/spool/amavisd/clamd.sock: No
such file or directory

Checking the config files /etc/amavisd/amavisd.conf and
/etc/clamd.d/amavisd.conf, there is a mismatch between the paths to the
clamd.sock files. In /etc/clamd.amavisd.conf, the path to the socket points to
/var/run/clamd.amavisd/clamd.sock (where the file is correctly created), while
amavisd is configured in /etc/amavisd/amavisd.conf to expect it at

The settings for both of the paths must match instead (I recommend using the
path under /var/run to be compliant with SELinux).

Probably this bug is from EPEL and not Kolab, but the Kolab installer should
check for it.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolabsys.com/pipermail/packaging-bugs/attachments/20140902/e3c9f220/attachment.htm>

More information about the packaging-bugs mailing list