Search results

adapt the postfix config (https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine) to allow all IPs for the listener on port 26. I'd strongly recommend against adding 0/0 to the trusted networks - as those are added to postfix `mynetworks` which is allowed on the...

hm - I'd expect a hostname (technically not an url - i.e. my.pmg.com should work not smtp://my.pmg.com) to work just as well as an IP - please share the complete logs from PMG - these should who where things go wrong

das freut zu lesen :) Bitte den Thread als 'SOLVED' markieren (oben über dem ersten thread auf 'Edit thread' klicken und das SOLVED prefix auswählen) - das hilft anderen, die auch auf das problem stoßen. Danke

PMG does use Bayes learning (we changed the enabled auto-learning to deing disabled by default, as it usually cause more false-positives) additionally once a mail leaves PMG it is gone. If you want to use bayes learning- you can manually configure SpamAssassin to do so (but in my experience...

There is support for Avast for linux: https://pmg.proxmox.com/wiki/index.php/Getting_started_with_Proxmox_Mail_Gateway#Second_virus_scanner for Spamhaus - you can probably integrate it following their tutorial on github (or just add them to the postfix/postscreen level) for other things you...

DMARC also takes the From-header into consideration - without the headers and the actual domains in the logs it's not really possible to say why one got quarantined and the other went through. https://martech.zone/what-is-dmarc/ - the graphics there seem to show how/what dmarc does regarding...

siehe: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_spamdetector_quarantine (port in den Spam Quarantine settings setzen) Ich hoffe das hilft!

Hm - the sender should not get a notification - but if you have before-queue filtering enabled PMG sends a 5xx response ("Rejected for policy reasons") - I think (but haven't tested it yet) if you don't have before-queue filtering enabled the mail should be dropped silently (unless you enable...

Why do you think so? - which errors do you get and why (if it's still an issue)? Thanks!

Thanks for the information! your system is using proxmox-boot-tool - in that case keeping the ESP mounted might be problematic/the cause of the failing boot: I'd probably remove the /boot/efi mount from /etc/fstab, run proxmox-boot-tool reinit to get the system in a consistent state! (Keep in...

I'll lock this thread - so all answers end up in the first post.

Thanks for the feedback and the report! We improved the check for the boot-loader issues (but it's still not available on our public repositories) - https://lore.proxmox.com/pve-devel/20250814120807.2653672-1-s.ivanov@proxmox.com/T/#t I'd guess that this version should have caught the issue...

please check/post the journal after booting when the cards are not available - new kernel/new systemd version might change the names of the NICs - the journal should tell you if there's a problem there. physically available means that they are listed in `lspci -nnk`? In most cases I'd recommend...

Looking through our bugzilla (which is the place where feature requests and bug-reports are tracked) I found: https://bugzilla.proxmox.com/show_bug.cgi?id=5538 which should align with your issue - please note your suggestion there (it gets more visibility). Thanks!

please send it to our development list - and provide a short explanation why this is needed in your case. Thanks!

hmm - check if there are some files in `/etc/ssh/ssh_config.d/` - or even a bit more general run - `grep -rE 'ssh-dss' /etc/` - check this on all nodes in your cluster! if that does not point to the issue - please open a new thread (feel free to mention me with @Stoiko Ivanov) - and share the...

as @LnxBil said - it would help a lot to know which commands you ran to get in that situation? (and to provide /var/log/apt/term.log and history.log from that upgrade) a very blind guess: did you maybe run `apt upgrade` instead of `apt dist-upgrade`?

No - the permission system in PMG is not domain aware - and for a very large part of the administration/configuration the settings are global (e.g. rules, most postfix configuration,...) I hope this helps!

Contributions are very welcome - thanks for the suggestion! We use a mail-based workflow - see https://pve.proxmox.com/wiki/Developer_Documentation for submitting patches.

from a quick look at the code: https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Setup/Base.pm;h=dbfc775c6f4769609c50caa6c8a7b91a91566080;hb=HEAD#l294 It should be set to true, if you set the containers IPv6 config to 'auto' (called SLAAC) in the GUI (did not test this explicitly...