6 ms·
Spam blocklist SORBS closed by its owner, Proofpoint
- koollman 2y agosorbs sarved me well for many, many years. RIP :/
- gmuslera 2y agoWhat happens with (not very frequently maintained) mailservers or appliances that used it? There are some alternatives, but not too many of them, and having one less makes the whole system more vulnerable to DDoS or legal actions (honest or not).
- PreInternet01 2y agoIf your mail server or appliance still relies on DNSBLs, it's high time to upgrade to a solution that doesn't. These days, a list of 'compromised Azure tenant IDs' (or domains abusing the Gmail API, or dodgy Salesforce senders: Microsoft is by no means the only issue here) is way more useful than anything source-IP-related...
- CWuestefeld 2y ago> a list of 'compromised Azure tenant IDs' [...] is way more useful than anything source-IP-related... Where do I get such a thing? A large portion of my incoming spam seems to be coming from "xxxxx.onmicrososoft.com", which sounds like it might be what you're talking about.
- PreInternet01 2y agoWell, mostly from your incoming spam. The header you're looking for is `X-MS-Exchange-CrossTenant-Id`. If it ends in `aaaa`, don't touch it, as that's the freemail-outlook.com, but otherwise, feel free to (test-)reject it. To get started: 41a71966-4fa6-4839-a87d-034d66bdda33 d931cb4a-3984-4328-9fb6-96d7d7fd51b0 e85f2c00-2730-4ca5-b8d8-609b15bd4746 (all seen-in-the-wild compromised instances in the past 14 days)
- ttul 2y agoHey there, you should start a blocklist!
- PreInternet01 2y agoYeah, no, I'm good -- having seen what happened to the ones that came before me, I'm quite happy to limit myself to policing (nah, gardening) my own little corner of the Internet...
- X-Istence 2y agoAbout 70% of my spam originates from *.onmicrosoft.com. Unfortunately I can't easily block the whole thing because there is also legitimate email traffic from Office365/Azure. I have tried sending Microsoft reports, but have not heard back, and the spam continues.
- PreInternet01 2y agoYes, Microsoft is very slow in blocking their customers from sending spam, yet very quick in blocking external senders for that reason (same for Google, Salesforce, Amazon, etc. BTW). Funny how that works... But, if you can, record the `X-MS-Exchange-CrossTenant-Id` header value for the spam you receive. If it ends in 'aaaa', that means it comes from the public outlook.com/hotmail.com service, and you'll need to do text content/from-address filtering to get rid of spam. But otherwise, deny-listing the GUID you get, will do wonders to eliminate future spam from that source...
- X-Istence 2y agoFor anyone interested, here's the list for the last month or so: https://gist.github.com/digitalresistor/03ea1b8798c519a71f06a7905d276216 https://gist.github.com/digitalresistor/03ea1b8798c519a71f06... Edit: moved list to Gist.
- PreInternet01 2y agoYou... seem to get a lot of spam! Just out of interest, across how many unique local recipient addresses is this, and how did you determine these messages were illegitimate?
- X-Istence 2y agoSingle user... me. My email address is used on all my git commits/mailing lists across the web. I check my junk folder every other day to make sure that legitimate mail does not go through because I've set my rspamd config pretty tight. So all of these are classified correctly as spam by human eyes.
- PreInternet01 2y agoSo, while the loss of SORBS is troubling (I mean: yet another initially-volunteer-driven and widely-used project burning out...), it, like other DNSBLs, is not very relevant to modern spam filtering anymore. With, like, 80+% of inbound SMTP traffic coming from Google, Microsoft, Amazon and assorted non-malicious transactional/list-based SaaSes, a simple 'I either like or dislike the sending IP' approach has been infeasible for many years.
- jeffbee 2y agoDNSBLs have been effectively the same as turning your mailer off, for at least 15 years.
- PreInternet01 2y agoSorry, "turning your mailer off" seems outbound-related to me, whereas DNSBLs are typically used for inbound filtering? And in 2009, filtering inbound SMTP traffic using a popular DNSBL or two was definitely effective (as was greylisting). Alas, no more. But I probably misunderstand what you're saying?
- Animats 2y ago> With, like, 80+% of inbound SMTP traffic coming from Google, Microsoft Just do a challenge-response on incoming mail from new addresses on Gmail and Outlook. Send an auto-reply telling them they can get their mail through if they copy a code in the reply. That will kill most spams from those sources.
- INTPenis 2y agoI think SPF+DKIM+DMARC has taken over most verification of email online already. I've had it setup with protonmail for a year now and it works very well, easily automated with providers such as AWS route53 for example. So technically I could have hosted my own email that whole time, just replace the protonmail senders with my own. As long as I get a VPS IP without a tainted reputation.
- dmw_ng 2y agoSPF+DKIM+DMARC are a classic case of Goodhart's law, the amount of spam they stop these days (at least anecdotally) is minimal. Most spam I get seems to come via SalesForce infrastructure, and a variety of similar bulk email marketing providers
- PreInternet01 2y agoSPF definitely stops most 'stupid' spam (with the second-most valuable metric being EHLO-to-rDNS correspondence). Now, Salesforce and most other non-malicious transactional/list-based SaaSes present other challenges, mostly solved by applying SPF to their content From: header in addition to the SMTP 'mail from' address. This also involves promoting sender domains from 'DATA reject' to 'MAIL FROM reject' based on behavior, since most spammers see 'MAIL FROM accept' as a win, and won't check any further results.
- fullspectrumdev 2y agoProper SPF/DKIM/DMARC at least prevents brand reputation abuse via spoofing (in many cases), which at least blocks a good amount of bullshit phishing and BEC efforts.
- bawolff 2y agoThey kind of solve a different problem though - verifying that the email sender is really authorized for that domain. Nothing prevents spammers from setting up their own domain with valid spf, dkim, dmarc.
- johnklos 2y agoDNSBL are good to have in addition to checking SPF+DKIM+DMARC. This is because spammers now mass produce domains with valid SPF+DKIM+DMARC using Cloudflare and GoDaddy for domain registration, WHOIS and DNS because neither company gives the slightest care about abuse (and actively go out of their way to make reporting abuse arduous), and the source IPs could be anywhere in the world. One thing that does work to combat these SPF+DKIM+DMARC valid sources, I've found, is to reject all email from supposed email servers which either don't have working reverse DNS or which have reverse DNS which has a name that differs from the HELO / EHLO name. It used to be enough to just insist on working reverse DNS that has matching forward DNS resolution, but recently I've been testing requiring that "Return-Path" has the same domain as the HELO / EHLO. Another thing that I've noticed but I'm not sure how to check in sendmail is to reject email that has a "Return-Path", "From", "To", or "Reply-To" that's a Gmail address when the email isn't from Gmail. I'd like the same test with Outlook / Hotmail and Yahoo. I've found almost no instances of legitimate email sent this way. Many things to consider, now that SORBS is one less tool to use!
- fyt2024 2y ago[dead]
- rootusrootus 2y agoAs a former sysadmin at a business ISP about 25 years ago, I do not miss SORBS and friends. They probably got better when taken over by a professional team, but by then I had moved on into another industry and did not have to manage mail relays. I don't miss that one bit.
- ttul 2y agoRunning a DNSBL is/was hardly a glamorous job. It takes a peculiar character to withstand the endless onslaught of complaints from unscrupulous marketers, clueless sysadmins inadvertently running a spam cannon, and end-users feeling the need to threaten lawsuits because their church distribution list got blocked.