Search results

False positives can happen and would require a bit more time to process mail and on a busy PMG that could cause delays especially if some of those are not responding and timeouts are waited for. Personally, I would remove all the uceprotect and sorbs lists. Have had issues with both for...

It sounds like a network config issue and as @Stoiko Ivanov mentions, it would be best to talk with hetzner support on what IPv6 settings you need to use. It could be the gateway isn't correct, or the prefix (netmask) isn't, or a few other problems that only they would know what the correct info...

Good question but would presume it to be all must match and not just some parts or else they would have put in "or and" conditions.

Expanding on this, a rule could be used to quarantine mail where the attachment doesn't match the list of allowed extensions. Something like: ((?!(.docx|.test)).)*$ just add the extensions in and use in a match file name object .

I give it in that post i mentioned but will post here also: ((?!example.com).)*$

So to confirm, you're talking about example@gmail.com sending to bob@example.com, where example.com is hosted by you. Bob@example.com forwards to bob@gmail.com. And you want to stop the forward from bob@example.com to bob@gmail.com. And more exactly, if the from address is not your domain...

The warning is a known issue and is planned to be removed in the upcoming versions according to https://forum.proxmox.com/threads/warning-ignoring-deprecated-option-safebrowsing-at-etc-clamav-freshclam-conf.88298/post-386900 .

Is postfix set to listen on a specific IP or all IPs on the system? If a specific one and that one is the public iP, it might not be able to use the private network IP as it can't route the public to the private. Where as the telnet works because the system routes it properly since you don't...

Well, what are you using? /api2/json/nodes/{node}/storage may show you what you want as it should show all storage setup within proxmox.

Have a look at /api2/json/nodes/NODE_NAME/disks/zfs (if ZFS is used ;) ) and that should show the free space . Replacing zfs with "lvm" should show details there but don't use LVM so can not test.

You'll want to look at config templating to avoid the changes being overwritten .

And remember any hardware / software RAID should not be used with ZFS .

Mail filters should be able to do this. Do a who regex object with the regex being: ((?!example.com).)*$ Then do a new mail filter rule for outbound with this who object and the block action object. Now anytime a message tries to go out and example.com isn't the sender, it should block the...

You could try value: !TLS

Show screenshots of those two rules object -- on the right side. They should have an action of "Accept" with from who object of the whitelist.

Just to toss this out there, hardware RAID should not be used with ZFS. Most ZFS performance complaints I have seen relate to ZFS config, using hardware RAID with ZFS, or slow drives.

I could be mistaken but that would be flagging every mail as spam in that case. Try disabling it and see if that helps the rule you're interested in.

You'll need to look at the action objects and find that and see what it is doing. Though that sounds like maybe adding a header.

The timing depends on the sending mail server's queue retry time I believe and not anything within PMG's configs.

Is the whitelist above the blacklist in the mail filter rules listing? If not, move it up above blacklist.