[SOLVED] Spam Quarantine master and slave didn't match

[sysops.bgn]

Hello everybody,

I've been checking on my cluster hardisk consumption and found that there is a significant different on Master and all slave server.



Further check, I found that there is a different stored file inside /var/spool/pmg/cluster on Master and slave server.
Here is from slave server:

And this is from master server:


When I check, all slave are still store spam from 3 months ago. We are using PMG 6.1-2 .
What should I do to fix this things? Can I just delete all files and let they sync to master again?

 

[Stoiko Ivanov]

which versions are you running on your PMG nodes?

out of curiosity - why do you need 8 nodes (haven't seen such a large deployment yet)?

 

[sysops.bgn]

which versions are you running on your PMG nodes?

I use PMG 6.1-2 .

out of curiosity - why do you need 8 nodes (haven't seen such a large deployment yet)?

It just we want to optimize all Public IP we have and it is a Shared SMTP for relay so yeah that's why.

 

[Stoiko Ivanov]

I use PMG 6.1-2 .

I assume that's the version displayed on top in the GUI? (should have been more explicit - the output of `pmgversion -v` would have helped a bit more - sorry!)

In any case we found a bug in the quarantine cleanup code which got fixed with pmg-api 6.1-8 - so please upgrade to the latest versions (pmg-api 6.2-5) - and report back if this does not solve the issue
Thanks!

 

[sysops.bgn]

I assume that's the version displayed on top in the GUI? (should have been more explicit - the output of `pmgversion -v` would have helped a bit more - sorry!)

In any case we found a bug in the quarantine cleanup code which got fixed with pmg-api 6.1-8 - so please upgrade to the latest versions (pmg-api 6.2-5) - and report back if this does not solve the issue
Thanks!

Sorry, I forgot how.

Spoiler: pmgversion

# pmgversion -v
proxmox-mailgateway: 6.1-1 (API: 6.1-2/53ccdd75, running kernel: 5.3.10-1-pve)
pmg-api: 6.1-2
pmg-gui: 2.1-3
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
libarchive-perl: 3.3.3-1
libjs-extjs: 6.0.1-10
libjs-framework7: 4.4.7-1
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-8
libpve-http-server-perl: 3.0-3
libxdgmime-perl: 0.01-5
lvm2: 2.03.02-3
pmg-docs: 6.1-2
proxmox-mini-journalreader: 1.1-1
proxmox-spamassassin: 3.4.2-13
proxmox-widget-toolkit: 2.0-9
pve-firmware: 3.0-4
pve-xtermjs: 3.13.2-1
zfsutils-linux: 0.8.2-pve2

Sure I'll try to update it and report back after I have result.

 

[sysops.bgn]

Just want to confirm, updating PMG to latest version solved this problem.

Spoiler: Latest pmgversion

# pmgversion -v
proxmox-mailgateway: 6.2-1 (API: 6.2-5/05a7829e, running kernel: 5.4.60-1-pve)
pmg-api: 6.2-5
pmg-gui: 2.2-2
pve-kernel-5.4: 6.2-6
pve-kernel-helper: 6.2-6
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.60-1-pve: 5.4.60-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
clamav-daemon: 0.102.4+dfsg-0+deb10u1
libarchive-perl: 3.3.3-1
libjs-extjs: 6.0.1-10
libjs-framework7: 4.4.7-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-http-server-perl: 3.0-6
libxdgmime-perl: 0.01-5
lvm2: 2.03.02-3
pmg-docs: 6.2-2
pmg-log-tracker: 2.1.7-1
postgresql-11: 11.7-0+deb10u1
proxmox-mini-journalreader: 1.1-1
proxmox-spamassassin: 3.4.4-2
proxmox-widget-toolkit: 2.2-12
pve-firmware: 3.1-3
pve-xtermjs: 4.3.0-1
zfsutils-linux: 0.8.4-pve1