Upgrade to latest version - few other questions

[BliXem]

Hello,

1: Can I upgrade to the latest update? I did install EFA on clean CentOS 64bit OS. I need to make sure it isn't creating partitions or does other stuff that can break this.

2: How can I set a maximum day limit of the quarantaine? I see this list now:

10/04/2017 301 items
09/04/2017 409 items
08/04/2017 434 items
07/04/2017 522 items
06/04/2017 556 items
05/04/2017 477 items
04/04/2017 635 items
03/04/2017 623 items
02/04/2017 354 items
01/04/2017 456 items
31/03/2017 532 items
30/03/2017 575 items
29/03/2017 537 items
28/03/2017 65 items

And it's eating ssd space. How can I set this till a maximum of 5 or 7 days?

3: If a mail IP has been blacklisted by spamhaus and someone is mailing our server with the blacklisted IP (not spammer), do they get any notice that the IP has been blocked by spamhaus with a link? If not, can I set this feature on?

[ovizii]

2.
/usr/local/sbin/EFA-Configure => 6 => 3

3.
the sending email server will see something like: 554 5.7.1 Service unavailable; Client host [42.112.81.187] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/42.112.81.187; - how it reportsthat back to the user is up to the sending server.

[BliXem]

Can someone tell me more about 1?

[shawniverson]

1) Partitions are not modified during updates, so that should not be a problem. Bear in mind updates are fully supported on the packaged VMs, so if you run into issues, support may be limited. Backup or snapshot/clone and test the update process first.

[BliXem]

Is it not possible to do 2 updates, on voor VM's and one for stand alone Centos versions? I want to run this with 7000 domains, so failures are not an option...

[BliXem]

Painless:

Update to 3.0.2.0 complete.

Please visit https://efa-project.org for more information.
Please reboot the system as soon as possible.

Update to 3.0.2.1 complete.

Please visit https://efa-project.org for more information.
Please reboot the system as soon as possible.

Well done guys!

[pdwalker]

I just upgraded from 3.0.1.8 to 3.0.2.1. It took a while, involved a couple of reboots, threw out some scary errors during the MariaDB installation, but otherwise completed. Very impressive.