On Tue, Mar 29, 2016, at 09:54 AM, /dev/rob0 wrote: > > and my goal is to block that & all OTHER mta hosts that have their > > NS on *.synapp.io or just synapp.io (just in case) > > Hehe, this brings to mind an old spam war story. Sorry, but this > might be of interest to this thread.
I've (re)read your 'story'. IIUC what this^^ effort is doing, I'm only blocking mail from mta hosts whose NS is hosted on these 'bad actor' domains. Since, for my money, they've lost my trust completely -- and on stubborn principle I don't like supporting their business model thru abuse of my server -- anybody who hosts at these bad actors can go pound sand. I think I've limited my blocks to that. Though, I'm keeping an eye on my logs for awhile, since I don't completely trust my postfix skills, either :-) > I was thinking like the one whose name I can't recall which sued > Spamhaus in US Federal court and almost took down the spamhaus.org > domain name when UK-based Spamhaus opted not to respond to the suit. > (Later Spamhaus did respond and solidly won.) Yeah, I remember that episode. But obviously what I do on my own server for my own needs, is my business :-) > FWIW, if you get spammed by MailChimp, they do staff and empower an > abuse desk. A report to them is not a waste of your time. I've reported to them in the past; seems to make a difference. What I don't appreciate is that they encourage THEIR customers to 'externally validate' their mailing lists. Sounds like a good thing, right? But they know darn well HOW those external validations are done, and by who. They just offload the bad action with a wink ... Well, that's my opinion and I'm sticking to it. Not clear what to DO about it, other than what I'm doing. > http://spammers.dontlike.us/ ... a mailing list which I [sort of] > co-manage ... this would be welcome there. Thanks. > > > In many cases you can do all your restrictions in one place, and > > > the usual choice for that would be smtpd_recipient_restrictions. > > > See again the aforementioned SMTPD_ACCESS_README. ... > The "Dangerous use" section describes it somewhat. I try to re-read it at least once every other day ;-) > BTDT, and I have lots of empty aspirin bottles to prove it. :) Once you get enough understanding of WHAT postfix does to be able to start step-by-step thinking it through, it's cool what you can actually do! But, I've learned you've GOT to be careful: "With great power comes great responsibility". Thanks. Jason
