My problem with Twitter isn't that a particular billionaire owns it.
It's that a billionaire can own Twitter.
My problem with Twitter isn't that a particular billionaire owns it.
It's that a billionaire can own Twitter.
Internet services owned by billionaires:
1. Twitter
2. Facebook
3. Instagram
4. TikTok
5. Snapchat
Internet services not owned by billionaires:
1. Email
2. IRC
3. BitTorrent
4. RSS
5. HTTP
So donβt tell me that walled gardens are inevitable and we should just accept surveillance capitalism as the price of doing business.
I appreciate the sentiment, but even the ones not owned by billionaires are still DEGRADED by them.
1. Email: have to use major provider or go to spam bin.
2. IRC, cf. freenode takeover. Also surveilled.
3. Maybe not so bad. :)
4. Viva Aaron Swartz!
5. HTTP is the protocol, oligarchs mostly control the browser itself.
What is important is people:
DO NOT USE PROPRIETARY CLIENTS!
Sure they bin it. Even with SPF etc. I've been running DNS since at least 1995, very familiar with it.
Also notable, is how many domains that don't have DKIM, DMARC, SPF, etc. that they do pass through. For example, from what I've seen, most companies using Microsoft mail services don't have those set up.
It isn't the mail configuration. It isn't something "tricky" on my side, to be clear. I am 100% compliant with standards.
The reverse DNS on your MX record doesn't match your domain.
$ host -t mx smugglersbbs.com
smugglersbbs.com mail is handled by 10 smtp.sixcolormail.com.
So even things like that, I have "better" for example, in that my MX record is actually handled by the same domain, and the reverse is correct.
There is more to it than just how the server is configured.
Where the server is located, is another factor for instance.
@jebba You are also correct, I use smtp.sixcolormail.com as my RDNS setting as the business that I own hosts email for other customers. smugglersbbs.com is a domain that is hosted on that mail server.
So, the settings are still correct, I am not sure what you are trying to get at?
What I'm getting at was just a response to your first post where you were saying you just need to set up DKIM and configure, and things will be ok. No, they won't. There is more to it than that.