citrix ica
$ cd /opt/Citrix/ICAClient/keystore/
$ sudo rm -r cacerts
$ sudo ln -s /etc/ssl/certs cacerts

lamAV requires quite a bit of resources to run in the background and this usually slows down the mail delivery. In the ISPConfig 3 (Under Perfect Server setup), clamAV is run within Amavis. Therefore, typical removal of clamAV commands will not remove it.

When RAM is really low, Linux kills amavis and this will cause mail not being delivered. Therefore, if we run amavis to manage anti-virus and spam, consider a minimum of 2G or 4G RAM VM/Cloud servers.

The steps to disable clamav and amavisd are:

(1) edit postfix conf - note amavis uses a special port 10024 and 10026. Therefore, if you are not using these ports, consider closing them in your firewall settings.

nano /etc/postfix/main.cf


# content_filter = amavis:[127.0.0.1]:10024
# receive_override_options = no_address_mappings

(2) Under ISPConfig 3.1, comment additional 2 lines

nano /etc/postfix/tag_as_foreign.re
#/^/ FILTER amavis:[127.0.0.1]:10024
nano /etc/postfix/tag_as_originating.re
#/^/ FILTER amavis:[127.0.0.1]:10026

Save changes and restart postfix


/etc/init.d/postfix restart

(3) stop and disable the services

/etc/init.d/clamav-daemon stop
/etc/init.d/clamav-freshclam stop
/etc/init.d/amavis stop

update-rc.d -f clamav-daemon remove
update-rc.d -f clamav-freshclam remove
update-rc.d -f amavis remove

To restore the changes, do:

update-rc.d clamav-daemon defaults
update-rc.d clamav-freshclam defaults
update-rc.d amavis defaults

The services shall start in the next reboot

(4) Under Ubuntu 16.04 and ISPConfig 3.1, also execute the following commands:

systemctl disable clamav-daemon.socket
systemctl disable clamav-daemon.service
systemctl disable clamav-freshclam.service

Note - The changes in postfix main.cf will get overwitten by an ispconfig software update when you select to "re-configure" services during update, so you should comment out the lines again after you install a ispconfig update.

xmonad
qtile

bash

prepare the new server, make a new installation of the very same version of ISPConfig you have on the origin server;
    make sure you have the same php packages installed on the new server. You can generate a list on the origin server with
    dpkg --get-selections | grep ^php | awk '{print $1}' | xargs
    and paste the output to apt install on the destination;
    make a backup of the ispconfig database on origin. If you want you can change the IP (and eventually the hostname) with sed:
    sed -i 's/1\.2\.3\.4/5\.6\.7\.8/g' db-dbispconfig-2019-05-25.sql
    sed -i 's/old\.host\.name/new\.host\.name/g' db-dbispconfig-2019-05-25.sql
    And restore it on the destination with:
    cat db-dbispconfig-2019-05-25.sql | mysql -u root -p dbispconfig
    connect to the new server ispconfig panel and go to Tools > Resync, check the All services checkbox and press Start;
    rsync /var/www with:
    rsync -a --stats --progress --delete ORIGIN_SERVER:/var/www/* /var/www/
    rsync /var/vmail by adjusting the command above
    rsync /etc/letsencrypt
    rsync -a --stats --progress --delete ORIGIN_SERVER:/etc/letsencrypt/* /etc/letsencrypt/
    make a dump of all c* databases and restore them on the new server;
    if you want to retain the same ISPConfig panel certs copy /usr/local/ispconfig/interface/ssl/;
    move DNS and all related stuff to the new IP.