-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spamhaus DNSBL AS Detection #5295
Conversation
I dont't have an OVH VPS, would need to get one for testing, but it looks okish |
PBL is missing when using DQS. Is there a reason for this? |
Don't understand exactly what you mean by that? Could you please be a bit more prercise? |
You've added the following lists I just had another read of the PBL https://www.spamhaus.org/pbl/ and on review, I'm not 100% sure if we should add this. |
Just readded the PBL if DQS is enabled. Can you test it? New Postfix image version has been uploaded to docker hub! |
I haven't moved to the new way of doing the DQS yet, I manually changed my config file 😅. I guess I'd have to move from stable to nightly too right to test? Which I don't really want to do. my
|
Yeah looks pretty much the same as i readded now :) But good call on moving it to nightly! |
When this does hit stable, I'll have to have a look what changes I need to make to my |
This PR will solve issue: #5293
It implements a check of the public IPv4 AS and reports if it is from AWS, Cloudflare or OVH as Spamhaus is blocking them to access the zen.spamhaus.org lists.
Therefore the DQS System of Spamhaus has been implemented within Postfix which uses a new variable called SPAMHAUS_DQS_KEY.
If the key is set it will use the DQS Lists for Postscreen if not it it will check if the IP is listed as a bad asn using curl to get a list from fuzzy.mailcow.email which is generated against bgpview.io API and deactivates (if necessary) the spamhaus.org list for postfix.