Search results

Thanks for reporting back that it's fixed with this!

could you please post the journal from the time when you click on the link - and the log from /var/log/pmgproxy/pmgproxy.log ? Thanks!

hm - funktioniert DNS für das PMG zuverlässig? - diese SpamAssassin hits kenne ich von fällen wo DNS ganz oder teilweise nicht geht.

Please share the logs of such an email - and if possible also the headers or the complete email.

I'd try removing this policy - as long as TLS is enabled PMG/postfix will try to connect to the host using STARTTLS. do you have any other modifications to the configuration templates (mostly for postfix)? else - how do the logs look like without the encrypt-policy - does delivery work...

Ich habe die Seite mal angepasst und kurz getestet: https://pmg.proxmox.com/wiki/Quarantine_Web_Interface_Via_Nginx_Proxy bitte bescheid geben ob es damit funktioniert - Danke!

das kann gut sein - danke für den Report! Ich stelle das mal nach und update gegebenenfalls unsere Dokumentation im wiki: https://pmg.proxmox.com/wiki/Quarantine_Web_Interface_Via_Nginx_Proxy

you can also use the Mail Filter/Rule System to match headers with regular expression - that's what the "What Object" "Match Field" does. https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#chapter_mailfilter might be a bit more user-friendly/flexible. I hope this helps!

please share some logs from mails that get deferred - also consider testing if there's an issue connecting to the systems with `openssl s_client -connect <ip.of.mail.system>:25 -starttls smtp` (from the top of my head - check with the help-output/man page if it's not working)

Danke!! - aber in dem Fall hat die mail ja laut google-mx eine gueltige DKIM signature: ARC-Authentication-Results: i=1; mx.google.com;...dkim=pass header.i=XXXX header.s=xxx .... spf=pass (google.com: domain of..... as permitted sender)XXXX; Deswegen (und weil sonst doch ein paar mehr...

Bitte mal die header einer solchen mail (oder die gesamte Mail) teilen - und auch domain darin lassen - damit wir das hier nachvollziehen können. (post kann auch gleich danach gelöscht werden).

We identified a potential issue with the new mobile GUI - and @dcsapak sent a fix - I assume this should fix the issue once it's applied: https://lore.proxmox.com/pmg-devel/20251020170350.771358ce@rosa.proxmox.com/T/#t Thanks for the report!

one possible explanation is that you sent the mails to the external port - signing only happens on the internal port (for outbound mail): https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_mailproxy_dkim I'd also suggest to add all domains you want to sign explicitly to DKIM...

There's a similar report in the German forum: https://forum.proxmox.com/threads/fehler-beim-upgrade-auf-version-9-im-proxmox-container.173238/ In that case - upgrading PVE fixed the issue for them... if that's not helping for you -please open a new thread and provide: * `pveversion -v` *...

This is laid out in the upgrade-guide: https://pmg.proxmox.com/wiki/Upgrade_from_8_to_9#Stop_and_mask_services_before_upgrade I hope this helps!

I would really suggest to reconsider this - the quarantine loses it's meaning if you sent one mail for each potentially problematic mail, causing the recipient to both be distracted, and to be more likely to simply click on deliver .... If you need your mails to arrive directly - just don't put...

hm - Wie werden die mails nach dem PMG weitergeleitet - geht das direkt ins internet - oder ist da noch eine content-inspecting firewall oder sonst ein filter dazwischen?

Do you use an LDAP login for your users to log into the quarantine? If you don't switch the user agent (I assume select "use Desktop version" on the mobile site) - what error do you get?! Which errors do you get - please share the journal and the pmgproxy-log (as text in code-tags) - or...

Ich sehe das Leerzeichen jetzt in den screenshots nicht- wird das von MXToolbox so reported, wenn eine Mail hingeschickt wird? oder ist das der DKIM lookup und dort wird domain und selector reingepasted? (dann würde ich nochmal sicherstellen, dass beim pasten nicht das Leerzeichen dazukommt...)...

I still don't understand what is failing? The interface changed (it's based on a different framework now) - however login through a quarantine link still works for me...