Search results

without checking explicitly if i remember correctly the database-sync (containing those entries) happens after the files are synced - so I'd first fix the one error you're having and then see if this resolves the issue what's the output of the command that files when run in a root-shell...

They are synchronized with the cluster-sync usually - do you see any errors with the sync in the past? could you share: * the output of `pmgcm status`? * journal from pmgtunnel and pmgmirror for a longer timeframe - and while you add one entry for one user ? * the output of `pmgsh get...

The complete logs of PMG are (like most modern Linux systems) in the journal - see `man journalctl`. For a particular mail the Tracking center also provides the logs. from the config you sent I really don't see how a mail sent from 151.248.236.202 to your PMG on the internal port would not be...

do you have modifications to the postfix config (mostly master.cf.in ) - that might rename postfix services? the Tracking Center is quite fast, but at the expense of being tightly relying on the logs having the expected formats ... I hope this helps!

If you have a subscription of level Basic or above - open a ticket at https://my.proxmox.com - there you'll get responses within a certain time frame - help in this forum is on a best-effort basis. else please share (in code-tags): * contents of /etc/postfix/main.cf * contents of...

you have selected "All Match" for your Whitelist who object... - that is most likely the issue

How are the priorities and configuration of your actual rules? - what is Quarantine/Mark Spam (Level 6), what is your Whitelist rule? (`pmgdb dump --rules active` provides a text overview)

the outputs of : * `ls /etc/pmg/templates/` * `nft list ruleset` * `iptables -nvL` and a reboot would still help in seeing where the issue might be.

the Tracking Center already should contain the relevant logs (you might need to select include Greylist and include empty sender) else the journal from the timeframe where such a mail was sent to the quarantine would help as well

That's probably the main cause of the not delivered reports ... https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_mailproxy_options you can disable smtpuf8 support for PMG (and postfix) this should help in this case alternatively - see how to enable this for your downstream...

does any address have mails in quarantine? (`pmgqm status` should tell you) - you can also send the report with pmgqm - see it's help output Also - please share logs as text (in code tags) instead of screenshots - it's far easier to work with (and the timeframe you shared is too short to see...

if the report style is not set to none, but to verbose (Ausführlich) then the mails should be sent at 00:05 to each user who has received mails that were placed in quarantine during the previous day. You can check the journal to verify that the `pmgspamreport.timer` started...

Hm - I'd expect the mail to be accepted.. * do you have any modifications in place (e.g. adaptations of the postfix config (in /etc/pmg/templates), firewall,NAT rules on the PMG? (`iptables-save -nvL` `nft list ruleset`)? Just to rule out any glitches - did you reboot after adapting the...

No this is not necessary, and you should not do that (else PMG would send mails from anybody to gmail.com) Is the mail from x2.suxeed.com[151.248.236.202] using the internal port 26?

Please share the logs of such a mail, and its header

How did you install - from ISO, on top of Debian, Container template? Thanks for the report!

PMG caches the LDAP lookups and aliases - it refreshes that cache with the pmg-hourly.timer (and associated service) once per hour. from a quick look it should keep the old data in case LDAP is not reachable for the resync. I'd suggest to simply try integrating it (in a test machine), and to...

For people affected by this with NVMe drives - could you please share the make and model? (`lspci -nnk` should provide enough information) additionally the output of `cat /sys/block/nvmeXn1/queue/write_zeroes_max_bytes` would help (replace nvmeXn1 by your nvme drive) Thanks!

see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#firewall_settings the PMG-nodes need also to be able to reach each other on port 8006 for cluster-sync in addition to the above list. I hope this helps!

use a regex - try `.*@.*maindomain\.shop` I hope this helps!