@cancel this is a lie.

I can reach most Outlook users, and most users can reach me. I've been self hosting since last year. I will not give up and strongly suggest others not do so either.

I'm on four whitelists already and I intend to keep finding ways to secure my systems, while encouraging others which best practices work, from locking out ports 465, 587 and 993 to making sure you specify high-end ciphers, setting up strict paramters, and require encryption for inbound connections (optional for outbound).

I have no interest in pandering to Gmail users as my networks are designed to DROP them.

I have some detailed tutorials on how this can be properly and SAFELY done.

@eric which is it? the article is a lie, or you aren't able to exchange emails with gmail users?

@cancel the article claims that they had hosted email for decades and gave up because they believe that relays are a racket (they most certainly are).

I do support the use of BT relays as backups, however.

I deliberately blackhole Gmail addresses. I still get spam, but not a lot. I also have stricter requirements that I can set for email that comes with the benefit of hosting your own server.

By blocking Google domains, I also am insulated from pixel tracking, spam payloads hosted on Drive, and so much more. It was a difficult decision, but I love the outcome for my systems.

Giving up your own relay is an OpSec mistake. To paraphrase Benjamin Franklin:

"Those who would sacrifice security for a little bit of convenience deserve neither security nor convenience, and will lose both."

@eric If your email requirements don't include things like "exchanging emails with gmail users" then yeah I think you can do pretty much whatever you want with your email. I don't think this is a reasonable suggestion for other people.

@cancel it's not, and I actually warn against it. However, it isn't permanent.

If a user wants to interact with Gmail users all they need to do is take down the Wireguard connection.

BOOM! It's all back.
@cancel "never surrender", although it is entirely sensible to use the big guys as backups when I need to to updates.

@yojimbo @cancel Yep. People are free to decide what is best for them. Film at 11 ;)

@jwildeboer @cancel I liked his article focusing on the consequences of making email very hard to self-host; not suggesting that people should or should not take this position.

@yojimbo @cancel My e-mail server is a cheap VPS at OVH. I can happily send e-mails to and receive from Google, Microsoft etc. My article series describes how I run my server with all the things needed nowadays, like SPF/DKIM/DMARC, which is definitely not that simple. So both sides are valid. That's all.

@cancel this is a rant with some errors like the fact that blocklists are forever, etc. I've sent emails from a shitty IP range at OVH for years w/o issues so what can I say: YMMV.

On the other hand, if you're sending email, you're dealing with rules set by Gmail, Yahoo!, and Microsoft... So yes, fuck that centralized bullshit.

@oz @cancel that's the key differences there, your bog standard Blocklist and spam filtering is easy to deal with and fix.

Google, Microsoft, and Yahoo! their shit is totally arbitrary, other than using their trash product, there is no real way to create an email that won't end up in their spam folders (or silently dropped) at some point without warning

@cancel @WG3K I am running self hosted email servers for more than 25 years now and recently switched my stack to Mailcow (dockerized). Highly recommended!

Sign in to participate in the conversation

Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.