Search results

The log was posted in this post https://forum.proxmox.com/threads/does-the-mail-filter-rule-have-priority-over-the-systems-spf-checking.114846/post-496849 Here is the screenshot of the whitelist

What is the relevant part? In my example, I whitelisted the FROM address and the IP of the sending server but it still went into the SPF check.

But isn't that what a "whitelist" is supposed to do. Especially this is something you have to manually override? A Whitelist should bypass any RFC, as this is something an system administrator would have to manually put in and understand the risk involved by whitelisting an IP. Otherwise, this...

Huh? I showed the log on post 6. Not sure what other logs want. If you want the screenshot, here it is https://prnt.sc/T1MxPvzaivMh This is a clear bug that the whitelist isn't working as intended. There's not much else to troubleshoot.

I did that as mentioned in my original post. Here is how I test it. Sender is noreply@yourdomain.com and the log is as I put the x.x.x.226 in the whitelist under mailproxy and also the sender email

Nop. Seems like whitelisting is somewhat broken in PMG.

I have a Whitelist Rule. Within the Rule, there is the Whitelist WHO The WHO includes ->email from address ->IP of the sending server, in this case it is a smarthost However, it seems like the Mail Filter is checking the SPF first before going through the Mail Filter rules. My question is...

Problem solved. Used the wrong function to add transport. Needed to use https://pmg.proxmox.com/pmg-docs/api-viewer/index.html#/config/transport The one I used was to update an already set transport

Trying to add a domain into the transport using the API. Using the pve2-api-php-client class. $pve2->PUT("config/transport/domain.com", array("host"=>"mx.domain.com","port"=>25,"use_mx"=>1,"protocol"=>"smtp") The dump of the header comes back with resource(6) of type (curl) string(336)...

Thanks, this is more clear on the condition now. Perhaps should be added in the manual. :)

@Stoiko Ivanov Care to chime in ?

Gone through the filter section in manual but it didn't mention. If I have multiple objects, is the rule only triggered when all of the objects are met or just one ? For example, eg 1) if I'm trying to block outgoing spam. I add all three What Object Spam Level (4), Spam Level (5), Spam...

I noticed that even if I try to do email tracking in the master node via the GUI, nothing will show up if the email isn't routed through it. That means if I'm running a API, I would need to query each of the nodes in the cluster to get the full tracking picture?

Thanks, will try this

Rule- https://prnt.sc/11c4ogh Who Object - https://prnt.sc/11c4pw3 As you can see it's quite simple. Other conditions in the Blacklist object (such as network) works. Just not the regular expression.

There are few spam emails that passes the spam filter every time, so I'm trying to block them based on the subjects. For example, I tried putting in the exact subject line Ran it through the test string and it worked fine. But then still receiving the same spam.

I currently have a setup of clusters in this format mx1.domain.com node1 node2 node3 mx2.domain.com node4 node5 node6 Domains are using mx1.domain.com and mx2.domain.com as the MX record I'm setting up this way because if one node goes down or I want to add new node to it, I can quickly...

Check this thread, https://forum.proxmox.com/threads/how-to-lets-encrypt-and-pmg.41493/ The setup on a single server is easy enough but the problem comes when in a cluster setup since you will have to update the fingerprint In post 10 of the same thread, I see a basic solution for a 2 node...

I'm following this guide to allow IP rotation on my nodes - https://forum.proxmox.com/threads/postfix-mail-rotate-outgoing.53584/post-247543 However, whenever the cluster syncs. It wipes out the custom changes per node (/etc/pmg/templates/) to the master node's files. Is there a way to...

There are many use cases for a feature. What the "creators" intended does not mean that's what users are using it for. And the fact that you want to dictate what end users (actual email users and not the sysadmins) do simply mean you had disconnected from the actual world usage. The fact that...