If you want a communications system that’s safe from government snooping, don’t use email. Stick to signal or maybe WhatsApp. Or if you must, self host. At least then the court order to see your server will come to you.
If you want a communications system that’s safe from government snooping, don’t use email. Stick to signal or maybe WhatsApp. Or if you must, self host. At least then the court order to see your server will come to you.
And if you're restricting your conversation to people on protonmail for security, why bother with email at all? Seems easier to just put the conversation on signal anyway. And then you get all of signal's other security benefits, like E2E encryption, crypto ratcheting, disappearing messages and so on.
This second restriction is especially damning: They accept cryptocurrency, but only for existing accounts - after you've already doxxed yourself.
The idea that "as the webmaster of the email server, i could get a notice and i can conveniently, confidently say "fuck off" sounds fun".
This isn't about protecting pedos or serious bad people but dmca nonsense or such "legal requests" that you are confident you can say no.
3 years ago:
gmail/outlook was an ass. They marked all emails as spam. I had to call recipients to check spam and mark as not spam. this was on-off for the first few months. then things went good on their own. They would mark spam initially all emails, then emails with attachments then once marked as not spam, things got better.
today i have 0 issues in outgoing email. funnily, i have a website that sends me emails and there is some unknown problem on "receiving emails". just one website so haven't had much look into it.
last month: followed the same setup and gmail/outlook made no complaints. this was surprising to me as i deliberately sent attachments but nothing.
one thing to note. i once send 15-20 mails in bulk (not cc/bcc but separate) at once and that triggered some spam response. marked as not spam fixed it though on recipient side.
both times i used mailinabox and a cheap vps from lowendbox deals. racknerd or something on offer.
takes 1 hour almost from domain/vps purchase to full setup and sending emails. backup on backblaze b2.
takes 5 minutes every 6 odd months to update the software but that's about it.
Do not bring your server up without securing the email setup and setting up essentially useless things like DKIM, SPF (and DMARC). Large providers want to see those.
If you get into a block list, know quickly and fix quickly.
Use a well established domain suffix like .com. The cheap vanity ones are usually blocked more.
If you need software recommendations, there is nothing Postfix+Dovecot cannot do.
* Proper A and MX record set up in DNS per SMTP standards
* Proper SPF record in DNS
* Proper DMARC record in DNS
* Proper DKIM record in DNS
* SMTP server (postfix) is not configured as an open relay
* SMTP server is configured with a DKIM milter to sign outgoing messages
I used basic guides for the DMARC/DKIM stuff since that was new to me and tested with a Gmail account. The first few messages were marked as spam but I was able to unmark them. Once I was able to verify a correct SMTP setup, after two or three unmarkings, all messages were just delivered normally and no longer marked as spam. Google will even email you a report to help debug issues if your DMARC record is set up for it.As far as I know this is about the best you can do. Everything else is pretty much getting your mail server IP addresses removed from various blacklists which can be easy to impossible depending on the service. The other option would be to forward to another service that allows relaying and has IP addresses with better spam scores but I personally prefer to avoid that.
Or Session?
(typo - wrong link corrected)