Recent content by Stoiko Ivanov

please share the logs of such a mail being rejected.

Zumindest nicht mit (den Bordmitteln von) PMG - ich glaube es gibt sicher noch einige pop/imap proxies (potentiell hat nginx da was, sonst perdition - aber da sind meine Erfahrungen auch schon ~ 15 Jahre her - sprich bin nicht sicher ob das noch gut maintained wird).

PMG kann POP3/IMAP accounts abfragen (via fetchmail), filtern, und dann per _SMTP_ an einen Mailserver schicken - vielleicht lässt sich das verwenden: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_fetchmail Ich hoffe das hilft!

The easiest and recommended way would be to wait for a new version of zfsutils-linux to be released - the patch is already applied on master and should be available with the next update to zfsutils-linux. for building the ZFS packages yourself - check out the developer documentation...

Glad that upgrading to the latest kernel worked for the reporters here - this is the recommended way to not run into issues with a different ZFS userspace and kernel version! But if someone runs into this issue - and still needs to run an older kernel - the following patch should allow running...

hm - Wie sehen die logs zu diesen mails denn aus? - hätte fast angenommen, dass alleine .beauty alleine von `KAM_SOMETLD_ARE_BAD_TLD` 5 punkte bekommen sollte - i.e. vl. würde es auch passender sein, ab einem gewissen spamscore global zu blocken statt mails in die Quarantäne zu verschieben...

Derzeit nicht - und ich bin mir auch wirklich nicht sicher ob das in der Praxis nicht dazu führt, dass viele User einen Haufen Domains Welcome-/Blocklisten und sich lange Zeit später wundern, warum mails nicht ankommen/nicht erkannt werden. Wenn es ein globales Problem ist, dass nicht einzelne...

This is the German speaking sub-forum - please post in German - or post in the general forums in English - this increases the chances that you get answers from our community. Thanks!

make sure you have selected the correct realm in the login-mask else - please share: * the journal while trying to login * /var/log/pmgproxy/pmgproxy.log I hope this helps!

from a quick look in the code and a quick check on a testsystem - no (the part rewriting the postfix config templates calls postmap for all needed files)

please share the complete journal around that time - this is not the only cause of "detected undelivered mail to"... - maybe pmg-smtp-filter had another issue, or postfix is not running properly...

Currently /etc/pmg/transport and /etc/pmg/domains are the authoritative source of the information in the API - so it should work fine to just edit those files. This might change in the future (for all readers who read this later) - so check the changelogs/release notes for versions after 9.0...

hm - just to not miss anything - is the affected system a Proxmox Mail Gateway? In any case - the issue seems rooted in Veeam - so asking there might yield better results. I don't have experience with Veeam application backups - so I might miss something. The error message seems like Veeam's...

hm - that response code does not look like it's coming from a regular PMG - maybe check the logs of the mailserver that should have received the message. else - yes the message is gone (technically it is still on the disk as long as the quarantine life-time of the message has not expired) in...

see: https://forum.proxmox.com/threads/proxmox-mail-gateway-security-advisories.149333/post-838667: