Hi All,
I would like to choose a new email provider, where security and privacy of the email is one of my main concerns (nothing to hide, but want to keep my data private, differently than what happens with the major providers). I have read maaany posts and websites guides but I am still confused.
I am happy to pay a euro or so /month, so I had reduced my choice to Mailbox, Posteo, Mailfence. The problem is that each of them has some flows that don’t let me go ahead with them!
Mailbox: uses PGP, so not straightforward to send encrypted emails (unlike with tutanota) and to have encryption at rest. No mobile app. Alias reuse after 90 days
Posteo: no spam folder. ALias reuse after 24 months
Mailfence : has no encryption at rest , no mobile app. Not sure about alias reuse
Have you got any comments on the above providers and /or other suggestions (except for Tutanota and Protonmail)? thank you, appreciated!
You must log in or register to comment.
I used this guide when setting up my self hosted email: https://workaround.org/ispmail/buster/big-picture/
I also added in Ciphermail for email encryption and it’s been almost hands off ever since.
Granted, there were quite a few things to digest until things were working as I wanted.
Why do you need a mobile app? It’s just email, all IMAP clients should work.
I have a mailbox address since years, never use the webui for checking mails, only for changing some settings, I access my mails with Thunderbird on desktop, Fairemail on Android. Both apps have builtin PGP, so you shouldn’t care what the provider supports.
The spam filter in mailbox is glorious, never got a spam there.
Well imap isn’t encrypted, right? That’s why one can or rather needs to run a software with proton called proton bridge to get imap locally
Yes, but for me standards are more important than encryption. I can encrypt mails with pgp, than they are end to end encrypted, imap doesn’t matter. I considered proton when I switched to mailbox, but usually I don’t send encrypted mails, because the reciepents cant read them, so I wouldn’t use the pros of proton.
Still haven’t found the perfect email service provider but Mailfence has worked for me. It’s easy to set it up with a mail client or use PWA, and I feel its calendar function is overall more robust than the competitors. Service and troubleshooting has also been timely and good for me. Not the most user friendly but best balance of everything in my opinion.
I’m currently using skiff, I don’t know if it suits you or not.
- Modern Interface
- E2EE
- Aliases available (can send messages using aliases)
- 10gb of storage
- Has a mobile application
You can selfhost your own mailserver and you have full control over the data.
I’ve heard this is becoming increasingly difficult to actually accomplish
I have some tech skill and this option looked flat out daunting to me. Then when considering the cost of domain, it looked more expensive than choosing a mail service.
Does anyone know a good guide for own mail server, including getting cheap enough domain?
10€/year domains are the standard. There are some alternatives like Hostinger which have “free” ones. Managing domain settings can be a pain in the ass a lot of the time. I personally use Cloudflare to manage my DNS settings for ease of use, tho I’ve heard tgere are privacy concerns with using Cloudflare.
As for the guide, here’s one from ChatGPT:
Certainly! Here’s a step-by-step guide to setting up a self-hosted and secure email service using Docker containers:
Step 1: Set up a server
- Choose a server provider or use your own hardware to set up a server with a reliable internet connection.
- Install a Linux distribution of your choice (e.g., Ubuntu, Debian) on the server.
Step 2: Install Docker and Docker Compose
- Follow the official Docker documentation to install Docker on your server.
- Install Docker Compose, which will simplify the management of multiple Docker containers.
Step 3: Acquire a domain name
- Register a domain name from a domain registrar of your choice (e.g., Namecheap, GoDaddy).
- Configure the domain’s DNS records to point to your server’s IP address.
Step 4: Obtain an SSL certificate
- Use Let’s Encrypt to obtain a free SSL certificate for your domain.
- Follow their documentation to set up Certbot and generate an SSL certificate.
Step 5: Configure DNS records
- Set up the necessary DNS records for your email service:
- Create an MX record that points to your server’s domain.
- Create an SPF record to verify your server’s authenticity.
- Add DKIM and DMARC records for additional security (optional but recommended).
Step 6: Set up and configure mail server containers
- Choose a mail server software to run in Docker (e.g., Postfix, Dovecot).
- Create a
docker-compose.ymlfile to define the containers and their configurations. - Configure the mail server containers with appropriate settings, such as domain name, SSL certificate, and mail storage location.
Step 7: Start the containers
- Run the
docker-compose up -dcommand to start the containers in detached mode. - Verify that the containers are running without any errors by checking the logs.
Step 8: Test the email service
- Create an email account using the chosen mail server’s administration tools.
- Configure an email client (e.g., Thunderbird, Outlook) to connect to your server using the provided credentials.
- Send and receive test emails to ensure the service is working correctly.
Step 9: Implement additional security measures
- Configure firewall rules on your server to allow only necessary ports (e.g., 25 for SMTP, 143 for IMAP).
- Regularly update the Docker images and containers to ensure you have the latest security patches.
- Consider enabling additional security features like fail2ban to protect against brute-force attacks.
It’s important to note that setting up a secure email service requires a good understanding of server administration and email protocols. It’s recommended to consult official documentation and seek professional assistance if needed to ensure proper configuration and security.
I like Proton Mail. It does have a free tier, but the paid tier is pricier than you suggested in your post.
Why the need for a specific mobile app for Mailbox? I use Mailbox in combination with FariEmail app on Android. It even supports PGP. Couldn’t be happier.
I use posteo.net for 10 years now, and I am super happy with them. I don’t get spam, and I have never missed an email.
They choose not to use a spam folder system, and I understand their reasoning, and agree with them.
They sometimes get criticized for some other decision (something to do with certificates, if I remember correctly), but after reading their reasoning, I agree with them.
In my experience, they have now real downside, and I recommend them to everyone I know when they come to me with email problems.
Keep in mind posteo.net does not have DMARC which means anyone can spoof an email @posteo domain.
All of the other providers have this. Mailing lists can be used with DMARC.
Thank you for pointing this out. I am no way expert but trying to study and understand. I then found other negative comments regarding the lack of DMARC, while on posteo website they say: “We have a DMARC “none” policy for Posteo email domain names, since DMARC is currently not recommended for mailbox providers. Outbound DMARC policies are primarily “best-suited for transactional emails and semi-transactional emails” (dmarc-org FAQ). At the present, DMARC has implications which do not meet customers’ individual use of email.” link
The dmarc-org FAQ is interesting too. I understand that Posteo publishes thier DMARC record, if I am not wrong
I would appreciate your opinion, you seem competent! Thank you
deleted by creator
I have my emails set up with Purelymail, they’re great if you don’t need the extra office suite tools and have a lot of custom domain addresses, but I’m also skeptical about the “single point of failure” setup as everything is run by one person and the entire service can go down with him. As far as I’m aware, there isn’t any other mail service that doesn’t charge extra for additional domains.
deleted by creator
After reading up on this some more it seems like he has plans in place to have his brother maintain the service if he can’t anymore, and even if he didn’t, the service should run until his aws subscription ends. Seems like not too big of an issue even for those who don’t use a client.
deleted by creator
