Search results

see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#chapter_pmgqm

It should - if the dependency is present (else it just gets skipped) - is libmail-dmarc-perl present on the system? - if not just install it you can check if it actually gets loaded by looking for DMARC in the `spamassassin -D all --lint` output but the error seems unrelated to the missing...

Did you clean-up the old deployment of the 3.4.6 installation? Additionally - how did you upgrade your PMG installation? (asking because according to the spamassassin lint output DMARC was not found - while it should get pulled in if you upgrade with `apt full-upgrade`) If this does not...

Thanks for the information - it seems one other user also hat similar issues - and both installations have a spamhaus-dqs installation in common. When did you deploy spamhaus-dqs? (PMG ships SpamAssassin version 4.0.0 since 7.3 - so if you installed it before you probably need to...

Hm - the issues is not common - do you have any modification to your PMG installation? (additional modules, rulesets, ...) Any specifics to your DNS setup? else - please provide: * pmgversion -v * spamassassin -D all --lint 2>&1 (the last one as plain text-file) Thanks!

ok - 256kb - da sollte die 16kb mail reinpassen dennoch erkennt spamassassin die DKIM signature als invalid.. beim durchschauen sehe ich nur dass das subject ein 'SPAM:' vorne stehen hat - woher kommt das? (wenn es durch das PMG rule-system kommt, sollte das keine rolle spielen, da die...

please share the complete logs for this e-mail

wie groß ist die max spam size?

Hmm - spannend - kurz die Nachfrage - ist es tatsächlich ein legitimes mail? (ich würde nochmal die header genau anschauen) Ansonsten als Tip wie in so einem Fall vorgegangen werden kann um herauszufinden was genau passiert: grep -r FACEBOOKMAIL /var/lib/spamassassin/ ...

welche regel genau soll denn abgeschwächt werden ? (das wird am besten im header der mail nachgeschaut, wenn die SPAMINFO hinzugefügt wird - sonst auch recht gut in den Logs/Trackingcenter zu sehen - bei 5 Punkten (das sind -5, da es weniger spampunkte macht) tippe ich mal auf: RCVD_IN_DNSWL_HI...

ich würde da einfach den score der betreffenden Rule herabsetzen (oder gleich auf 0 setzen um den test auszuschalten): https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_spamdetector (section 4.8.3) Ich hoffe das hilft!

mir wäre bisher noch nie ein Fall untergekommen in dem das notwendig wäre... (und 5 Minuten .... sind doch sehr lange) ich würde mal schauen was kommt wenn direkt auf port 25 von dem ERP system connected wird: `nc -v 192.168.1.248 25` - da sollte ein banner kommen sonst kann ich auch swaks...

before PMG got support for DKIM a few users installed a dkim-signing milter and configured it inside the postfix configuration - this might be more flexible to edit the postfix config in PMG you need to use the templateing system...

The location of the templates has not changed - you can check yourself with `dpkg -L pmg-api` the setting from the template sets the myhostname variable to 'hostname' (which is read from /etc/hostname usually) and the first entry of your search domains in /etc/resolv.conf see the reference...

The invalid domain message comes from acme.sh implementation for cloudflare (dns_cf.sh) - so I guess something does not work with that domain or it's cloudflare registration I hope this points you in the right direction (I don't have a domain registered with cloudflare so cannot test it here)

Nein - ist derzeit nicht möglich (und auch nicht geplant).

This is currently not possible in the GUI If you want to delete all the mail in the queue you can use `postsuper -d ALL` if you only want to delete specific mails you need to get the queue ids from the postqueue command and feed them to postsuper (postqueue has json output - so you could use...

If I recall correctly this log-message points to a general problem with DNS resolution from postfix point of view. * does DNS resolution work reliably at 23:00? * how does your /etc/resolv.conf look like - what are your nameservers?

maybe it's related to this issue: https://github.com/rustls/rustls-native-certs/issues/48

hmm - again more on a hunch - do you have any local CA-certificates in the system? (/usr/local/share/ca-certificates) - and if yes - could it be that they contain something which is not really well-formed for a certificate?