FS#44505 - [clamav] Enable Milter
Attached to Project:
Arch Linux
Opened by ushi (ushi) - Wednesday, 08 April 2015, 17:13 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 09 April 2015, 21:20 GMT
Opened by ushi (ushi) - Wednesday, 08 April 2015, 17:13 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 09 April 2015, 21:20 GMT
|
Details
Description:
Please enable milter support for ClamAV. A sample configuration is already shipped upstream. Here is a example service file: [Unit] Description=clamav-milter After=clamd.service [Service] Type=forking PIDFile=/run/clamav/clamav-milter.pid ExecStart=/usr/bin/clamav-milter --config-file /etc/clamav/clamav-milter.conf [Install] WantedBy=multi-user.target Thanks, ushi |
This task depends upon
Closed by Gaetan Bisson (vesath)
Thursday, 09 April 2015, 21:20 GMT
Reason for closing: Implemented
Additional comments about closing: clamav-0.98.6-2 in [extra]
Thursday, 09 April 2015, 21:20 GMT
Reason for closing: Implemented
Additional comments about closing: clamav-0.98.6-2 in [extra]
Comment by Gaetan Bisson (vesath) -
Wednesday, 08 April 2015, 18:13 GMT
Comment by ushi (ushi) - Wednesday,
08 April 2015, 18:15 GMT
Comment by ushi (ushi) - Wednesday,
08 April 2015, 18:17 GMT
Comment by Gaetan Bisson (vesath) -
Wednesday, 08 April 2015, 18:28 GMT
Comment by ushi (ushi) - Wednesday,
08 April 2015, 18:29 GMT
The thing is, our default clamd.service uses the default
clamd.conf we provide that's simple enough to be worth maintaining
with the package. The milter configuration file you mention is
just a sample and would need to be tailored to your setup, so it
makes little sense to provide a working service file for a non
existing clamav configuration.
Yes, of course. The configs are just samples. What i actually
want, is that the package is compiled with the --enable-milter
configure option. The configs are just a nice to have.
See:
http://www.clamav.net/doc/install.html#installing-clamav
Ah, sure, the compile option is fine. :)
Thank you very much =)