Recent content by Stoiko Ivanov

Soweit ich das verstehe heißt die Änderung nicht, dass ssh-rsa hostkeys nicht mehr verwendet werden, sonder nur, dass nicht sha1 mit einem rsa key verwendet wird: (von: https://www.openssh.com/txt/release-8.8) sprich das Problem wird wahrscheinlich woanders liegen - ein output von `ssh -vvv...

No stress - thanks for reporting it - at least we do see that it affects more users :)

I think this is already reported in: https://bugzilla.proxmox.com/show_bug.cgi?id=4192 - subscribe there to get notified once it is fixed (I assume sooner rather than later) I hope this helps!

Ich würde vorschlagen hier mal die logs des systems zu posten und auch wie genau die storage angelegt wurde ... Auf den ersten blick würde sich potentiell anbieten den <user> ins username feld einzutragen und <domain> ins domain feld neben dem passwortfeld in der GUI - aber ich bin mir gerade...

Currently this is not implemented - but quite a few users in the community have created workarounds - see: https://forum.proxmox.com/threads/sync-tracking-center-between-multiple-nodes.108983/post-468290 I hope this helps!

check the journal since boot - there should be messages pointing towards why pmgproxy is not running `journalctl -b` I hope this helps!

Thanks for bringing this to our attention - I agree that the phrasing is misleading - the dates in the table were correct though (PVE 6.X was always planned to be supported til 2022-07) We'll rephrase the documentation to (hopefully) be less confusing

If you still have the time @t.lamprecht uploaded a new kernel 5.15.39-4 yesterday - which contains the same fix, but in a version that is more likely to get merged upstream - so testing would be much appreciated! In general I'd say as long as there is a kernel on the machine that does boot and...

glad we cleared that up :)

from the logs matches the first entry in your screenshot?

check the user blacklist of jboutwell@aquilasolutions.us - you should find that it contains the address listed in the relevant headers of the mail. I hope this helps!

show the complete log for the mail - this should explain which address is listed on the user blacklist of which user ....

the matches are indeed case-insensitive - see the 'i' at the end of: https://git.proxmox.com/?p=pmg-api.git;a=blob;f=src/PMG/RuleDB/MatchField.pm;h=2671ea404dbcd8b910cacb636d8301eee59f5074;hb=HEAD#l110 so - no there is no way to do a case-sensitive match

almost - as far as your logs show - you used a '@gmail.com' address as sender ... and gmails dmarc policy is (for very good reasons) not strict: dig txt _dmarc.gmail.com +short "v=DMARC1; p=none; sp=quarantine; rua=mailto:mailauth-reports@google.com" I hope this explains it

sorry - overlooked this thread... for your original question: just to be on the same page - your issue here is that the mail that dmarc-tester.com sends gets delivered by PMG? If I understand their tests right (sadly I did not find a technical explanation on their page of what they're testing...