On 10/7/2019 10:49 AM, Jaroslaw Rafa via mailop wrote:
Well, we all have right to protect ourselves from actual spammer. But not from "someone who I think might look like a spammer".
There is no difference when it comes to the rights of what I can do with the equipment/bandwidth I own.
I regularly and without a second thought block whole TLDs and > /24 netblocks. Do I worry about it? Not really,
It's similar to self-defense when someone is attacking you on the street. If someone is actually attacking you, you have all the right to defend yourself. But not if you just see someone who looks suspicious to you and you think "he may attack me, so I attack him first".
Not even close to the same thing as accepting vs. rejecting e-mail.
I'm not talking here about blocking actual spams. I'm talking about blocking messages who are*not* spam, because the receiving end "thinks" for some reason that the*might* be spam.
As owner of my mail server, I'm allowed to define what I consider spam/unwanted e-mail. The courts have already affirmed that that is a right that providers have.
Of course, this can always happen. But there*should* be always a way for the*sender* to complain to the admin on recipient side, and, if the messages are actually mis-classified and the sender actually isn't a spammer, the admin of the receiving server*should* correct the configuration.
Or not correct it, if they don't feel its worth their time/effort or if it opens them up to more abuse.
I have my own legacy IP assignment that I send from that only has ever been under the control of my org - that gives me leverage when I contact providers and ask for them to investigate.
You don't by using OVH. Get your own IP block from the RIRs and likely your experience will change.
"Should" in RFC sense:) - which means it is no obligation, but it this the best practice that should;) be followed. And Google doesn't follow it. That's the actual problem. There's no way to complain to them about the issue.
Again, totally within their rights. Just because you can scream into the phone doesn't mean I have to take your call.
-- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop