On Fri, Sep 01, 2017 at 05:51:39PM +0200, Holger Weiß wrote: > And either way your comparison doesn't hold. If you're operating an > open SMTP relay, you're doing something you can't do with XMPP. We're > talking about blocking service providers who have *local* spammers.
Fair enough -- but regardles of the technical differences under the hood (unsecured relay, or trivial to create accounts and use them) users are still being innundated by spim from a server whose operator will not, or cannot, clean up their act. Just *two* domains were resposible for >80% of the spim I was getting, before I finally said "screw this" and just blocked both domains entirely. This crap can and will drive users away from federated XMPP altogether, and is a far bigger practical problem than non-encrypted S2S comms. Wholesale domain blocking is what it took force email providers to start caring about the greater effects of their insecurity. And, I might add, is the only techincal solution available to XMPP server operators today. (The joys of network effects!) I'm struggling to see an upside to keeping my XMPP server federated. Or, for that matter, keeping it running at all. - Solomon -- Solomon Peachy pizza at shaftnet dot org Delray Beach, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur.
signature.asc
Description: PGP signature
