Doing either of these incorrectly
could open your server up as a relay that can be used by spammers to attack other sites.
If the client IP address is likely to change frequently and is not part of a trusted range,
you should either configure the client to use a mail server that is local to it or configure
SMTP authentication in Exim. More information about enabling SMTP authentication can
be found on your server in /usr/share/doc/exim4-base/README.SMTP-AUTH and
/etc/exim4/conf.d/auth/30_exim4-config_examples.
The Courier authdaemon examples in 30_exim4-config_examples can be enabled,
allowing Exim to use that facility for authentication and negating the need to set up a
different mechanism. In order for it to work, however, you will need to add the Debian-exim user to
the daemon group (gpasswd -a Debian-exim daemon) and restart Exim.
ClamAV Misconfiguration??”The following error indicates that the ClamAV daemon
could not read the temporary message file:
1E9PDq-0003Lo-BY malware acl condition: clamd: ClamAV
returned /var/spool/exim4/scan/1E9PDq-0003Lo-BY:
Access denied. ERROR
Make sure you added clamav to the Debian-exim group and restarted ClamAV, as shown
in the installation section.
ClamAV Unavailable??”This error usually indicates that the ClamAV daemon is not
running:
1E9PGL-0003MX-38 malware acl condition: clamd: unable to
connect to UNIX socket /var/run/clamav/clamd.
Pages:
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257