Problem solved !
I was still BLOCKED since my IP was already over quota with URIBL. Even if new requests where cached, I had to wait a few hours to be able to query again.
To help others, here is a quick tuto on how to enable and test unbound on PMG running in PVE:
At datacenter level (OVH for...
Ok, almost there... I needed to add two rules in OVH firewall: TCP and UDP for all adresses with source port 53.
Unbound is now working:
 unbound[273131:0] info: 127.0.0.1 220.127.116.11.in-addr.arpa. PTR IN
 unbound[273131:0] info: 127.0.0.1 mail1.sea91.rsgsv.net. A IN...
If I disable the firewall at the datacenter level (OVH), not the one in my PVE nor in my PMG, it work !! I'll try to find the right rule to add
The only nftable rules I have are the one created by Fail2Ban, or the one delivered with PMG (if there are rules delivered with it)...
I tried to follow instruction's in https://forum.proxmox.com/threads/uribl_blocked-however-uribl-com-shows-its-not.76825/#post-478336, but I'm not able to make it work.
What I need is to make unbound work in my PMG, so I don't over use URLBL and get BLOCKED.
root@pmg14:~# dig a...
I tried to implement the solution at https://pmg.proxmox.com/wiki/index.php/DNS_server_on_Proxmox_Mail_Gateway, but I always get this error:
root@pmg14:~# dig a proxmox.com @127.0.0.1 +short
; <<>> DiG 9.16.27-Debian <<>> a proxmox.com @127.0.0.1 +short
;; global options: +cmd
I can't pinpoint where the file is added, but it happened when doing a backup to a PBS in ZSTD, around the line:
INFO: CT Name: pmg14.legardeur.net
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/1085863/root/ to /var/tmp/vzdumptmp1941818_1003
My root "/" partition is getting from ±60% to a 91% usage during backup job to an external PBS. After the job, free space is back to normal.
Like if a temp folder was pointing to a mount on this 21Gb partition instead of the 500Gb partition (i,e,: /var/lib/vz/*').
I don't see...
As soon as I add my PBS (version 2.1-5) as a backup storage in my 8 PVE (version 7.1-10), my /var/log/proxmox-backup/api/auth.log contains tons of this. If I disable the storage, it stop. If I limit access to certains nodes, it's slowing down, but it keep going every few seconds ...
Just want to make sure the problem is not on my side, since all my PMG are reporting me the same errors... is it AIRCANADA.COM SSL that is expired? Anyway to accept the connexions anyway?
Dec 26 11:57:43 pmg10 postfix/smtpd: connect from r121.mail.aircanada.com[18.104.22.168]