41
Can't choose a secure email provider! (feddit.uk)
submitted 1 year ago by cool9@feddit.uk to c/privacyguides@lemmy.one
71 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments
[-] amithinkingright@lemmy.one 2 points 1 year ago

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?

[-] Bork@beehaw.org 4 points 1 year ago* (last edited 1 year ago)

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.yml file 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 -d command 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.

[-] mikni@lemmy.friheter.com 2 points 1 year ago* (last edited 1 year ago)

https://mailinabox.email or https://mailcow.email for the server. And then Porkbun.com usually have some domains on sale for a dollar or two.

this post was submitted on 17 Jun 2023
41 points (100.0% liked)

Privacy Guides

16263 readers
2 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.

You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...

Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!

This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.

Moderation Rules:

  1. We prefer posting about open-source software whenever possible.
  2. This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
  3. No soliciting engagement: Don't ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don't repost topics which have already been covered here.
  7. News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
  12. General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago
MODERATORS
jonah@lemmy.one
dngray@lemmy.one
freddy@lemmy.one
ninchuka@lemmy.one
jonah@lemmy.jonaharagon.net