I think there's no logging for normal operations, only for errors

How strange. Unfortunately I don't know python so I cannot help further. You can try opening an issue on the project's github

zimico wrote:Just remove the .sock file (the path is in the conf file) and restart service. And then you will see the errors which relate to .py files.

I have no idea how the plugin works, but based on this message Connection to www.virustotal.com timed out. it looks like your server cannot reach VT

From this line Nov 12 15:06:20 mail.zoholab.com amavisvtd[16553]: 2019-11-12 15:06:20,394 ERROR [MainThread] Socket /opt/zimbra/data/clamav/amavisvtd.sock isn't working: [Errno 111] Connection refused it looks like either the socket isn't created or it doesn't have permissions to access the location.

I was mistaken. Content of /etc/systemd/system/amavis-vtd.service is [Unit] Description=AmavisVTd [Service] ExecStart=/usr/bin/python3 /usr/local/lib/python3.5/dist-packages/amavisvt-0.5.3-py3.5.egg/amavisvt/amavisvtd.py Restart=always RestartSec=10 StandardOutput=syslog StandardError=syslog SyslogI...

The service file is in the GitHib repo of the project. I'll try to document better

It's an old page (2016) and it's in french (sorry) but here you have informations about using the free version of Tyk as proxy/cache to the VT API. https://blog.zenithar.org/post/2016/01/15/tyk-proxy-virustotal/ Thanks, very useful. It needs a little tweaking, at least for how I intended to use it....

Yeah that limit is pretty low and you often hit it. I have installed it in three servers and so far it's working good, I didn't have any problem reported. I see the proxy suggested in the README is dead. I did a quick search on Google and found there are some python stuff around, but I didn't try th...

Same situation (and actually very similar background :D) solved by adding -o smtpd_sasl_auth_enable=no to the smtpd line in /opt/zimbra/common/conf/master.cf.in. Resulting modified block should look like this: smtpd pass - - n - - smtpd -o smtpd_tls_security_level=%%zimbraMtaTlsSecurityLevel%% -o sm...

For the migration itself ZeXtras tool is the best option, as phoenix said.

As for the backup of your new install all the current open implementations are possibly faulty due to this bug. Your only safe option is to use ZeXtras backup, paid solution.