Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On 14/10/2019 16:50, Marc Haber wrote: On Mon, Oct 14, 2019 at 09:23:17AM +0100, Adam D. Barratt wrote: On 2019-10-14 01:21, Serge Rijkers wrote: exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl Debian Policy requires that /var/run be a symlink to /run, so that change should make no difference. I tested again with the symlink in place. It does make a difference. Also, the configuration option is commented in the default file, and there is not even a macro to enable it. So, who enables this already knows her way around things. Apparently, I am one of those who knows my way around things. Even so, this av_scanner = thing bit me. And yes, I figured it out quickly. This should, IMO, be fixed in unstable and testing (it's a no-brainer one-line change), but I don't think we should do this in stable. That seems fair enough. Regards, Serge Rijkers
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On 2019-10-14 Marc Haber wrote: > On Mon, Oct 14, 2019 at 09:23:17AM +0100, Adam D. Barratt wrote: [...] > Also, the configuration option is commented in the default file, and > there is not even a macro to enable it. So, who enables this already > knows her way around things. > This should, IMO, be fixed in unstable and testing (it's a no-brainer > one-line change), but I don't think we should do this in stable. I concur. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On Mon, Oct 14, 2019 at 09:23:17AM +0100, Adam D. Barratt wrote: > On 2019-10-14 01:21, Serge Rijkers wrote: > > exim4.template.conf contains: > > > > av_scanner = clamd: /var/run/clamav/clamd.ctl > > > > clean buster clamav-daemon uses /run/clamav/clamd.ctl > > > > For a on tech-savvy user this is difficult to diagnose > > possibly exim4.template.conf should contain: > > > > av_scanner = clamd:/run/clamav/clamd.ctl > > Debian Policy requires that /var/run be a symlink to /run, so that change > should make no difference. Also, the configuration option is commented in the default file, and there is not even a macro to enable it. So, who enables this already knows her way around things. This should, IMO, be fixed in unstable and testing (it's a no-brainer one-line change), but I don't think we should do this in stable. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On 14/10/2019 10:23, Adam D. Barratt wrote: Control: tags -1 + moreinfo On 2019-10-14 01:21, Serge Rijkers wrote: exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl Debian Policy requires that /var/run be a symlink to /run, so that change should make no difference. Regards, Adam I would like to point out that a clean buster install does not create the symlink, so the change would make a difference. I feel that a package should not depend on erratic behavior elsewhere in the system. Clamd-daemon uses /run not /var/run exim should reflect that change. Ultimately a new user installing buster runs into this problem. Whether this is fixed in exin, clamd or debian installer is metter for debate. should i report this elsewhere?
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On 14/10/2019 10:23, Adam D. Barratt wrote: Control: tags -1 + moreinfo On 2019-10-14 01:21, Serge Rijkers wrote: exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl Debian Policy requires that /var/run be a symlink to /run, so that change should make no difference. Regards, Adam I have also created the symlink to/run in /var and retested with av_scanner = /var/run/clamav/clamd.ctl wihich then fails again.
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
Control: tags -1 + moreinfo On 2019-10-14 01:21, Serge Rijkers wrote: exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl Debian Policy requires that /var/run be a symlink to /run, so that change should make no difference. Regards, Adam
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
Package: exim4 Version: 4.92-8+deb10u3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? A clean install of buster as an smtp mail server * What exactly did you do (or not do) that was effective (or ineffective)? exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl instead. * What was the outcome of this action? Changing this to the above made clamd scanning from exim4 operational is was not before. * What outcome did you expect instead? -- Package-specific info: Exim version 4.92 #3 built 27-Sep-2019 16:09:35 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DANE DKIM DNSSEC Event OCSP PRDR PROXY SOCKS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 Configuration file search path is /etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='tregare.net' dc_local_interfaces='192.168.0.110 ; 127.0.0.1 ; ::1' dc_readhost='tregare.net' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='192.168.0.0/24' dc_smarthost='smtp.ziggo.nl' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='true' dc_mailname_in_oh='true' dc_localdelivery='maildir_home' mailname:tregare.net # /etc/default/exim4 EX4DEF_VERSION='' # 'combined' - one daemon running queue and listening on SMTP port # 'no' - no daemon running the queue # 'separate' - two separate daemons # 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4. # 'nodaemon' - no daemon is started at all. # 'queueonly' - only a queue running daemon is started, no SMTP listener. # setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4 QUEUERUNNER='combined' # how often should we run the queue QUEUEINTERVAL='30m' # options common to quez-runner and listening daemon COMMONOPTIONS='' # more options for the daemon/process running the queue (applies to the one # started in /etc/ppp/ip-up.d/exim4, too. QUEUERUNNEROPTIONS='' # special flags given to exim directly after the -q. See exim(8) QFLAGS='' # Options for the SMTP listener daemon. By default, it is listening on # port 25 only. To listen on more ports, it is recommended to use # -oX 25:587:10025 -oP /run/exim4/exim.pid SMTPLISTENEROPTIONS='-oX 25:465:587 -oP /run/exim4/exim.pid' -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.71 ii exim4-base 4.92-8+deb10u3 ii exim4-daemon-heavy 4.92-8+deb10u3 exim4 recommends no packages. exim4 suggests no packages. -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = "en_US:en", LC_ALL = (unset), LC_MONETARY =
