see:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_whitelist_overview
The mail-proxy whitelist is for allowing clients, which would be rejected by e.g. postscreen - it's independent of the rulesystem
I hope this helps!
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_whitelist_overview
The mail-proxy whitelist is for allowing clients, which would be rejected by e.g. postscreen - it's independent of the rulesystem
I hope this helps!
Good afternoon, we added the necessary domain to the whitelist, but DNSBL still blocks emails from this domain.
Attachments
yes - the IP is listed on the DNSBL - so you have to whitelist the IP
(else every spammer could send you mails by just forging the sender header...)
Good afternoon, thank you very much, the IP whitelist works, but then why do we need a domain whitelist here? If it doesn't work out anyway, what's its point? And another question unrelated to the whitelist: We have ldap tied to Proxmox, previously we had automatic domain synchronization with proxmox, after one of the Pmg updates, automatic synchronization stopped working for us. Please tell me where to dig to solve this problem, it is not very convenient to synchronize manually.
The screenshot of the tracking center with the anonymization does not give the complete picture - but I think if the IP is blocked by barracudacentral (and this is the only problem with this mail ) whitelisting the IP in the mailproxy whitelist should be enough
Nothing changed with that part IIRC - this is done by pmg-hourly.service (started by pmg-hourly.timer):
https://git.proxmox.com/?p=pmg-api....=30c74bd27c3a4bd751561032e1a04ef52177db53#l48
I hope this helps!
We understood this, but it is not entirely clear why there is a white list by domain if it does not work?
Sorry, I don't really understand what we need to do in order for automatic synchronization to start working. We have it in our services. Maybe we need to press start?
Now we have looked at the logs of this service, it can be seen that the service works and synchronizes every hour, but this is not true automatic synchronization does not work.
What exactly does not work? - I don't understand the comment. The sync works by running once every hour.
The whitelist by domain is for occasions where the IP is not the reason for a reject, but something in the configuration of the domain itself (e.g. a broken SPF record)...
Good afternoon, now it's clear from the white list. Thanks.
Question on pmg-hourly we have a cluster of two mxs, on mx2 the success status is syslog, but on mx3 there is no start and syslog status, when pressing the start button nothing happens.
That's odd - please check the journal on mx3 (journalctl -b ) for any messages which might show an issue with pmg-hourly
Grepping only for the service name will not catch all information - this is why I said look through the complete logs for hints.