Any ideas where I can do this without my changes constantly being overwritten?# ### \&ask_daemon, ["", 'sssp:/var/run/savdi/sssp.sock'], \&ask_daemon, ["", 'sssp:[127.0.0.1]:4010'],# # or: ["", 'sssp:[127.0.0.1]:4010'], qr/^DONE OK\b/m, qr/^VIRUS\b/m, qr/^VIRUS\s*(\S*)/m ],this is in in.Unless you’re deploying on a small disk where storage is a concern, this step is recommended: # Edit this file to introduce tasks to be run by cron.# # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones.After applying the updates, and restarting the necessary components of the mail stack, I ran my usual test of sending an email from one of my accounts to another one. However, I realised that it isn’t a completely valid test to send an email from one internal account to another because I have amavisd configured to not scan anything coming from my trusted IPs and domains.
This guide assumes you have already followed our Email with Postfix, Dovecot, and My SQL guides and are running Ubuntu 12.04 LTS.
Nov 14 lenovo systemd: amavis.service: Failed with result 'exit...'.
Hint: Some lines were ellipsized, use -l to show in full.
Shoudn't the latest amavisd-new package/update taking care of removing the file? Just checked - /etc/cron.daily/amavisd-new still persists, I've deleted the file manually now.
it is a configfile and I usually dislike kicking configfiles. Shoudn't the latest amavisd-new package/update taking care of removing the file? Delete the conffile if it has not been modified, otherwise rename it with a .dpkg-old suffix.