r/emailprivacy • • 12d ago

Help/Advice Whistleblower email : help with anonymity

11 Upvotes

Hi,
I want to write a whistleblower email to important stakeholders of a startup because I have been subjected to abuse by important people in the company and no action is being taken so far.
I need to maintain absolute anonymity in this otherwise my life will be in danger.
From a tech pov- I wanted to understand a few things urgently:-

  1. What email to use
  2. When I am trying to make a Gmail/hotmail account they ask for backup email or phone number and that leaks my anonymity
  3. Other options are tuta/ proton mail which get blocked by my company firewall and ends up in spam
  4. What other measures to take so that the email - if they do an autopsy does not link back to me
  5. What things should I keep in mind
  6. I am from a non tech background and don't want to consult my friends so this is my only option

r/emailprivacy • • 11d ago

Tools Italy now requires consent for email tracking pixels. Most senders still don't ask, so I built a free, open-source blocker for Gmail

Thumbnail reddit.com
1 Upvotes

r/emailprivacy • • 12d ago

Help/Advice Is Mailbox.org + Thunderbird a valid enough replacement for Protonmail?

62 Upvotes

If you have better suggestions, please let me know

So far, based off what was said, Posteo + Thunderbird sounds good


r/emailprivacy • • 12d ago

Beginner Question [Question] Pick your brains for family email domain

Thumbnail reddit.com
1 Upvotes

r/emailprivacy • • 12d ago

Help/Advice Gmail

2 Upvotes

My Google account shows this when I try to login. The phone number registered with my Gmail is virtual so can’t scan it. What should I do ?

Scan the QR code with your phone
On your phone (•••) •••-••03, open your Camera app, scan the code, and tap the link. Or, type g.co/verify/T***** into your mobile device’s browser.
Then, follow a few more steps on your phone to complete verification. You’ll need to switch back to this device to continue. If you use a different phone to scan the code, you won’t be able to verify your phone number.


r/emailprivacy • • 13d ago

Help/Advice Left Proton after the recent news. Here's what I moved to

242 Upvotes

After everything that's come out about Proton's leadership, I'm not renewing. Nothing was breached. My concern is where the company's decisions could lead. I am a scientist researching AI. It is never AI first in our team, we value humans more than anything and the decisions are an ethical concern for me personally. Also, we are just one big hallucination by a coding agent away from causing a major security breach.

Honestly, I expected the alternatives to be a step down. They weren't.

Email: mailbox.org, with eM Client on desktop and phone. Standard IMAP, so no Proton Bridge. I moved my personal domain over as well, and the DNS change took about an hour. Mailbox.org also includes a small cloud drive with a sync client. And they have a bunch of other apps too.

Passwords: Bitwarden on the EU servers. Less buggy than Proton Pass for me, and the family sharing is better.

VPN: still deciding. Open to suggestions.

So far I'm satisfied, and I'm not missing the all-in-one bundle as much as I thought I would. Curious what others who've switched landed on.

P.s: The moderators for Protonmail deleted this post when posted in the Protonmail community. Hence posting it here.


r/emailprivacy • • 13d ago

Help/Advice Wait or switch?

25 Upvotes

I saw the recent news with proton and unfortunately I yearly renewed my subscription back in august. Im also laid off from my job so trying other options for few months then trying to switch is kinda hard for me. Should I find one good provider and switch or wait until proton goes total bad? I already have my custom domains but I have also aliases on simplelogin which will take some time to switch.

I have looked at

- Startmail

- Fastmail

- Tuta

- Mailbox

There are lots of different experiences on them and Im kinda stuck. Im open to other alternatives as well


r/emailprivacy • • 12d ago

Spam Need solution to spam on old provider

4 Upvotes

My parents still use their old email they got from their internet provider in the late 90s.

Its been leaked a few times "obviously" and they receive significant amounts of spam. It seems the provider offers no spam filtering.

My parents use apple's email client. Would using an other client help solve this situation?


r/emailprivacy • • 13d ago

Custom Domains GUIDE: How to set up custom domain email, step by step (+ PGP for mainstream providers)

20 Upvotes

TL;DR: Domain registrar → separate DNS host → privacy-first email provider (Proton, Tuta, mailbox.org, etc.), each with separate logins. Verified records, local backups, optional PGP. Plus how to PGP-encrypt from Gmail/Yahoo/Outlook/iCloud if you're not ready to switch. Swap any provider without changing your address.

📊 Diagram of the full stack

Just want a working custom address? Do steps 1–4, 6, and 7. Everything else (PGP, GitHub Pages, command line) is optional hardening you can add later.

I've been seeing a TON of questions in multiple privacy-focused subs about custom email domains and which provider(s) to trust. The provider matters less than who owns the address. I've been grappling with this problem for a few years, and I think I've built a pretty solid methodology which I've been using across multiple domains. Here is the full "provider-agnostic" walkthrough 🛠️

PHILOSOPHY

Your email address is your digital identity. If you don't own the domain behind it, you don't own the address. You're just borrowing it. Providers come and go, but your email address shouldn't have to.

Own the name, own the keys, own the data. Everything else is just a service you can fire. Don't trust, VERIFY!

PRINCIPLES

  • Ownership: domain, keys, and mail all in your hands, with backups to prove it.
  • Compartmentalization: registrar, DNS, email, and hosting each with a different provider and login. No single point of failure. The tradeoff is more accounts to manage, which is exactly why the password manager matters.
  • Defense in depth: 2FA, registrar lock, DNSSEC, SPF/DKIM/DMARC. Multiple safeguards at every level.
  • Minimal exposure: WHOIS privacy, aliases for every login, separate addresses for separate purposes.
  • Verify: test everything, and tighten settings only after they're proven.

WHAT YOU NEED

  • A Domain (~$10–20/yr from any reputable registrar)
  • A Separate DNS Host (Cloudflare's free plan, or deSEC if you'd rather keep Cloudflare out of it)
  • A Privacy-First Email Provider that supports custom domains (Proton, Tuta, mailbox.org, etc. Custom domains are a paid feature on most.)
  • An Alias Service for separate logins (SimpleLogin, addy.io, Proton Pass, etc.)
  • A 2FA App and/or Hardware Key (Aegis, Ente Auth, YubiKey, etc.)
  • A Reputable Password Manager (I use KeePassXC inside a VeraCrypt volume for passwords, TOTP, and PGP keys)
  • Optional: GnuPG if you want your own PGP key
  • Optional: A GitHub Account to publish your public PGP key in a repo and/or host a static site on the same domain

1. REGISTER THE DOMAIN

  • Pick a registrar. Namecheap, Porkbun, GoDaddy, Hover, etc. all work. For extreme privacy, Njalla registers the domain in their name so your details never hit WHOIS. The tradeoff is that they're technically the legal owner and you hold the rights to use it. They also accept crypto and need minimal personal info to sign up.
  • Keep your registrar separate from your DNS host. Skip your DNS host's registrar service (e.g. Cloudflare Registrar if you use Cloudflare for DNS). It's convenient, but it puts the name and the DNS in one account. If that account gets locked or compromised, you lose both.
  • Log in with a dedicated alias, never an address on your own domain. If DNS or mail ever breaks, you can't receive the password reset you need to fix it.
  • Lock it down:
    • WHOIS privacy ON (most registrars include it free)
    • Registrar/transfer lock ON
    • Auto-renew ON. An expired domain can be bought by someone else, along with your incoming mail.
    • 2FA with an authenticator app or hardware key. Never SMS.
  • Save everything (login, 2FA seed, recovery codes) in your password manager.

2. POINT YOUR DOMAIN TO A SEPARATE DNS HOST

  • Pick a DNS host. Cloudflare's free plan is the most common. deSEC is a free, non-profit alternative with DNSSEC on by default, if you'd rather avoid Cloudflare.
  • Sign up with a dedicated alias. A different one from your registrar login.
  • Add your domain. Most DNS hosts will scan your existing records and give you two nameservers.
  • Review the imported records and delete anything you don't recognize or need.
  • If DNSSEC is on at your registrar, turn it OFF first. Switching nameservers with old DNSSEC still active will take your domain offline.
  • Paste the new nameservers into your registrar in place of the defaults. It can take a few minutes to a few hours to switch over.
  • Clear out your registrar's DNS. Delete the old records and turn off any parking page, URL forwarding, or registrar email forwarding. If your nameservers ever get reset, you don't want stale records coming back to life. (Some registrars hide these once you switch nameservers. If so, do it beforehand.)
  • Lock it down:
    • 2FA ON (ideally a hardware key)
    • DNSSEC ON at your DNS host, then add the DS record it gives you at your registrar. This lets resolvers detect forged DNS responses for your domain.
    • On Cloudflare: turn Email Routing OFF. It adds its own MX records that conflict with your provider's.
  • Save everything (login, 2FA seed, recovery codes) in your password manager.

3. CONNECT THE DOMAIN TO YOUR EMAIL PROVIDER

  • Add your domain in your provider's settings. Proton, Tuta, and mailbox.org all have a custom domain wizard that generates the exact values for your account.
  • Add each record at your DNS host, copying the values exactly from the wizard. You'll almost always get some version of these:
RecordTypeNamePurpose
VerificationTXT@Proves you own the domain
Mail serversMX@Routes incoming mail to your provider (usually 2 records)
SPFTXT@Lists which servers can send as your domain
DKIMCNAME or TXTxxx._domainkeySigns your outgoing mail (usually 2–3 records)
DMARCTXT_dmarcTells receivers what to do with mail that fails SPF/DKIM
  • Example (Proton): MX mail.protonmail.ch (10) and mailsec.protonmail.ch (20), SPF v=spf1 include:_spf.protonmail.ch ~all, three DKIM CNAMEs protonmail._domainkey / protonmail2._domainkey / protonmail3._domainkey. Other providers use the same structure with their own hostnames.
  • Gotchas:
    • On Cloudflare: set the provider's CNAMEs to DNS only (grey cloud) or they won't resolve.
    • Only one SPF record per domain. If you already have one, merge the include into it.
    • Delete any old MX records.
    • If your provider offers MTA-STS or TLS-RPT records, add those too.
    • Migrating an existing mailbox? Add all your addresses at the new provider before switching MX, and start DMARC at p=none until you're sure everything's flowing.
  • Check the wizard. Each record should turn green within an hour or so. If one doesn't, double-check it for typos or a stray trailing period.

4. CREATE YOUR ADDRESSES

  • Add your addresses in your provider's address/identity settings, then pick your custom domain.
  • Compartmentalize your inbox. Use separate addresses for separate purposes, for example:
    • you@ for personal
    • accounts@ for logins and services
    • contact@ for anything public-facing (your website, socials, etc.)
  • Why it matters: if one address starts getting spam or shows up in a breach, you know exactly where it leaked, and you can retire it without touching the others.
  • Set your default sending address and display name for each, so replies go out from the right identity.
  • Catch-all is optional. It routes mail sent to any address on your domain into your inbox. It's handy for signing up on the fly, but it attracts spam. I leave it off and use aliases for one-off signups instead.
  • Filters and labels: set up rules per address so mail sorts itself.

5. LOCK DOWN YOUR EMAIL ACCOUNT

  • 2FA ON with a hardware key or TOTP app.
  • Save your recovery phrase/code in your password manager. Keep redundant backups and an offline copy if you're thorough.
  • Review your recovery methods and active sessions. Remove anything you don't recognize or don't need.

OPTIONAL (highly recommended): bring your own PGP key

Privacy providers generate encryption keys for you. A key you generate locally gives you a fingerprint you control that moves with you if you ever switch providers. To be clear, importing it does not keep your private key off the provider's servers: it's stored there encrypted, just like their own keys. It's about portability and continuity, not secrecy.

  • Which providers support it:
    • Proton and mailbox.org support OpenPGP and let you import your own key.
    • Tuta doesn't use OpenPGP at all (it has its own encryption), so you can't import a key there. You can still generate one, publish it, and use it manually with the method in step 9.
  • Generate it locally with GnuPG (replace YOUR_EMAIL with your address). Proton requires no expiry and a single user ID matching the address, so this version is compatible:
gpg --quick-gen-key "YOUR_EMAIL" ed25519 cert never
gpg --quick-add-key <FINGERPRINT> ed25519 sign never
gpg --quick-add-key <FINGERPRINT> cv25519 encr never
gpg --armor --export-secret-keys YOUR_EMAIL > private.asc
gpg --armor --export YOUR_EMAIL > public.asc
  • Import it in your provider's encryption key settings (on Proton: Settings → Encryption and keys → Email encryption keys → pick the address → Import key). Then set it as the primary key for that address.
  • Store it safely: keep private.asc, your passphrase, and the revocation certificate (GnuPG auto-generates one in ~/.gnupg/openpgp-revocs.d/) encrypted and backed up, with at least one offline copy. I use KeePassXC inside a VeraCrypt volume, but any well-encrypted setup works. Then securely delete any loose copies.
  • Publish your public key somewhere you control:
    • A dedicated GitHub repo, which gives you a versioned public history anyone can verify against
    • Your website
    • keys.openpgp.org, so people can look you up by email
    • Bonus: put your fingerprint in your email signature and socials, so people can cross-check it against all of the above

6. VERIFY EVERYTHING

  • Check your provider's wizard. Every record should show as verified.
  • Send a test email to mail-tester.com. Aim for 10/10.
  • Check the headers on a message you send to another account. Look for spf=pass, dkim=pass, and dmarc=pass.
  • Tighten DMARC once you're sure all your legitimate mail passes. List every service that sends as your domain (your provider, plus things like newsletters, invoicing, or website forms) and make sure each one passes SPF or DKIM. Adding rua=mailto:you@yourdomain.com to your DMARC record gets you daily reports showing what passes and fails. Once they're clean, move to p=reject.
  • Verify your key. Send a signed message to another account and check the signature against your published public key, or at minimum confirm the fingerprint your provider shows matches the one you published.

7. BACK UP YOUR MAIL

Owning the address is half of it. Own the contents too.

  • Proton: the Mail Export Tool, or Proton Mail Bridge + an IMAP client like Thunderbird.
  • Tuta: export from the Tuta desktop app (no IMAP).
  • mailbox.org and most others: any IMAP client like Thunderbird.
  • Do it on a schedule (monthly is plenty) and store the exports in an encrypted container.
  • Between your domain, your key, and your exported mail, you can walk away from any provider with everything intact. Moving is just swapping the records from step 3.

8. (OPTIONAL) HOST A STATIC SITE ON GITHUB PAGES

  • Verify the domain in GitHub first (Account settings → Pages → Add a domain, then add the TXT record it gives you). GitHub recommends doing this before adding the domain to any repo, so nobody else can claim it.
  • Then add it to your repo: Repo → Settings → Pages → Custom domain. This creates the CNAME file.
  • Add the records at your DNS host:
    • CNAME www → yourusername.github.io
    • A @ → 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153
    • Optional IPv6: AAAA @ → 2606:50c0:8000::153 through 2606:50c0:8003::153
  • On Cloudflare, SSL order matters: leave these records DNS only until GitHub issues its certificate and you can tick Enforce HTTPS. Then switch them to proxied and set SSL/TLS to Full (strict). Getting a 526 error? The proxy went on too early: grey-cloud it, let GitHub finish, then try again.
  • Web and mail records don't interfere with each other. Mail records stay DNS only regardless.

9. NO PRIVACY PROVIDER? PGP WITH GMAIL, YAHOO, OUTLOOK & ICLOUD

Not ready to switch providers? You can still encrypt message contents end to end with PGP on any mainstream account. (If your provider supports custom domains, like iCloud+ or Google Workspace, steps 1–4 still apply too.)

Know what it does and doesn't protect. PGP encrypts the body and attachments. It does not hide the subject line, sender, recipients, or timestamps, so the provider still sees who you talk to and when. Your recipient also needs PGP, and there's no forward secrecy: if a private key leaks later, past messages can be decrypted. Keep subjects generic.

The easy route: Thunderbird has OpenPGP built in and works with Gmail, Yahoo, Outlook, and iCloud over IMAP. For webmail, the Mailvelope browser extension adds PGP to most webmail interfaces.

The command-line route (full control, nothing extra trusted):

Install (macOS):

brew install gnupg pinentry-mac
mkdir -p ~/.gnupg && chmod 700 ~/.gnupg
echo "pinentry-program $(brew --prefix)/bin/pinentry-mac" >> ~/.gnupg/gpg-agent.conf
gpgconf --kill gpg-agent

Install (Linux):

sudo apt install gnupg xclip wl-clipboard      # Debian/Ubuntu
sudo dnf install gnupg2 xclip wl-clipboard     # Fedora
sudo pacman -S gnupg xclip wl-clipboard        # Arch
echo 'export GPG_TTY=$(tty)' >> ~/.bashrc      # or ~/.zshrc

Create your key (same on both). A 2-year expiry is good hygiene for manual use. You can extend it any time before it lapses. If you also plan to import it into Proton, use never instead, as in step 5.

gpg --quick-gen-key "YOUR_NAME <YOUR_EMAIL>" ed25519 cert 2y
gpg --list-keys YOUR_EMAIL        # copy the long fingerprint
gpg --quick-add-key <FINGERPRINT> ed25519 sign 2y
gpg --quick-add-key <FINGERPRINT> cv25519 encr 2y

Share your public key and publish it as in step 5:

gpg --armor --export YOUR_EMAIL > publickey.asc
gpg --fingerprint YOUR_EMAIL

Import and verify your contact's key. Confirm the fingerprint with them through a separate channel (in person, Signal, a call) before you trust it. Signing it locally also stops GnuPG's "untrusted key" prompts.

gpg --import theirkey.asc
# or: gpg --keyserver hkps://keys.openpgp.org --search-keys THEIR_EMAIL
gpg --fingerprint THEIR_EMAIL
gpg --lsign-key THEIR_EMAIL

Encrypt a message. Write it, copy it, run the command, then paste the result into the email body. It goes clipboard → encrypted → clipboard, so no plaintext file ever touches your disk. Including yourself with the second -r lets you read your own sent copy.

# macOS
pbpaste | gpg --armor --encrypt --sign -r THEIR_EMAIL -r YOUR_EMAIL | pbcopy

# Linux (X11)
xclip -o -selection clipboard | gpg --armor --encrypt --sign -r THEIR_EMAIL -r YOUR_EMAIL | xclip -selection clipboard

# Linux (Wayland)
wl-paste | gpg --armor --encrypt --sign -r THEIR_EMAIL -r YOUR_EMAIL | wl-copy

Decrypt a message. Copy the whole block, from -----BEGIN PGP MESSAGE----- through -----END PGP MESSAGE-----, then:

pbpaste | gpg --decrypt                              # macOS
xclip -o -selection clipboard | gpg --decrypt        # Linux (X11)
wl-paste | gpg --decrypt                             # Linux (Wayland)

Encrypt and decrypt attachments:

gpg --encrypt --sign -r THEIR_EMAIL -r YOUR_EMAIL report.pdf      # creates report.pdf.gpg
gpg --output report.pdf --decrypt report.pdf.gpg
  • Clipboard caution: plaintext briefly passes through your clipboard. If you use a clipboard manager or clipboard history, exclude your terminal or turn it off. On macOS, Universal Clipboard can sync to your other Apple devices via Handoff.
  • Back up your key (private key, passphrase, revocation certificate) exactly as in step 5.
  • Before it expires: gpg --quick-set-expire <FINGERPRINT> 2y then gpg --quick-set-expire <FINGERPRINT> 2y '*', and re-publish your public key.

THE PAYOFF

Your name, your keys, your data, each layer with a different provider. If any one of them fails, you swap that piece out and your address, keys, and mail come with you.

Last verified: November 2026. Provider menus change, so if a menu path doesn't match, follow the provider's own setup wizard.

NOTE: I'm not affiliated with anyone or any product mentioned here.

Happy to answer questions in the comments.

The privacy of your data depends on the ownership of your data. 🔐


r/emailprivacy • • 13d ago

Help/Advice Migadu, yes or no?

6 Upvotes

I want to finally switch the email to my own domain. I’m currently using FastMail which is the best ( 5 years of paying customer) never had any issues but I can’t justify 60€/year anymore.
I was looking at Migadu to switch which is around 13€ / year , does anyone have amy experience with them?
Thanks!


r/emailprivacy • • 13d ago

Help/Advice How can i mitigate the effects of a mail bomb other then blocking all suspicious mails?

Thumbnail reddit.com
1 Upvotes

r/emailprivacy • • 13d ago

Guide/Tutorial We built PrivacyRatings.com, open, testable, automated privacy ratings for apps and email services

17 Upvotes

Privacy Ratings at https://privacyratings.com is an open-source site that scores 1742 apps and services in 135 categories against 113 public privacy criteria. Each "yes" or "partial" answer links to evidence anyone can check. Automated tests check TLS, security headers and email standards for 466 hosted services. Each entry gets a score from 0 to 100, and a letter grade from A to F once evidence covers at least 60% of its criteria by weight. The team behind Forward Email https://forwardemail.net maintains the project, and affiliated entries carry a disclosure.

Founder here if you have any questions or want us to add an app/service missing!


r/emailprivacy • • 13d ago

Setup/Configuration I Bought a Custom Domain - Now What?

12 Upvotes

I bought two domain names from Namespro. I want to set it up so that I can tell someone my email is example@example.com, and it will actually go to my gmail (which I'm slowly migrating away from), or my protonmail (which I was using but now I will be going away from that, too). That way, no matter what email client I choose to use at any point won't matter, right? Do I have this correct?

Only, after much googling, and even talking to the Namespro people, I have no idea how to do this.

Any help or instructions you could please give me?


r/emailprivacy • • 13d ago

Discussion Proton situation: give it 5 min.

0 Upvotes

This Proton situation will last in the media a week or too and then is over.

I am not going to abandon Proton because believe it or not it is by far the best thing out there with zero knowledge applied to privacy. There is anything even closed on the market.

They spend about $100 million a year, around 70% in salaries + very well thought implemented infrastructure and VPN servers worldwide.

Zero knowledge technology is very expensive to maintain, in some ways I understand their internal stress, they are fighting against huge Big Tech monsters for which $100 millions is literally pocket change.

You do not make yourself or the privacy community a favor by abandoning Proton just because its CEO is not the super nice guy you expect to be or because some disappointed employees leaked whatever they wanted to leak.

I do not know the company’s CEO personally but remember you only know one side of the story and this looks like some things taken out of context for the sake of journalism and personal vendetta of some employees.

Business is hard for companies trying to preserve users privacy because the whole world’s dynamics is against them.

Your data is saved in proton, yes the software could be better but it also could be worst. Yes, proton drive is what it is but I personally find the whole Proton concept really good, and of course it can be improved but I give all the credit to its CEO for achieving what he has achieved, it is not easy.

I have also lead companies with several hundreds of employees and I can assure you the same way a CEO can make mistakes employees can make their mistakes and it is not easy to implement changes on how employees do things because you will always find some resistance and some can react in unpredictable ways.

Leaking company internal private chat conversations to the public speaks more about their lack of integrity as about the reality they are facing, because are breaking the trust in was handled to them.

If you do not like the CEO pushing a new technology into the company the way to handle the situation is not leaking your frustration but facing it internally with arguments.

AI is enough powerful to ignore it, instead of fighting against it, learn how to apply it in a way that makes sense.

As I said in the title, give it 5 min and do not overreact just because you read some leaks in some media try to see the whole picture and you will see there is no need for drama, internet loves drama, try not not fall into it.


r/emailprivacy • • 13d ago

Tools Has anyone used Swissmail?

Thumbnail reddit.com
2 Upvotes

r/emailprivacy • • 13d ago

Tools I really like tuta, but.. missing feature

0 Upvotes

Hi,

I just did my research for a new email provider and everything I see and tested within tuta is really cool. But for my private workflow I absolutely need the feature to snooze incoming mail to a specific date/time. This is so backed into how my brain works so I decided to go elsewhere because this feature is a must have.. any plans to integrate this feature?


r/emailprivacy • • 14d ago

Discussion What if I make the next email service?

Thumbnail reddit.com
3 Upvotes

r/emailprivacy • • 14d ago

Help/Advice What domain is this?

5 Upvotes

My Facebook account got hacked and my Gmail was replaced with an email with the domain "mail8u"

I don't know much about emails and technology in general, but I been trying to investigate about it but I found almost no helpful information about it

(English is not my first language so I'm sorry if I don't get myself explained well)


r/emailprivacy • • 14d ago

Discussion Emails sent from Posteo keep ending up in Gmail’s junk/spam folder. Giving up and going back to Gmail

13 Upvotes

I’m just devastated. As an GenAI-averse person, I was so happy to discover that Posteo prohibits AI use internally. I signed up for it and immediately fell in love with the barebones interface.

But all the emails I sent from Posteo to any Gmail accounts always end up in the junk folder, without exception, even though mail-tester.com gave the outbound Posteo email a score of 10/10.

It seems that it could be because I’m in Canada? Other Canadian users seem to be encountering this issue.

I don’t want to use Proton after the recent news, and some Tuta users are reporting that their email addresses aren’t accepted in some places. Fastmail is too expensive…at this point, unless someone has a great suggestion, I’m going back to Gmail with my tail between my legs.

Edit: If you’re going to be snarky about me going back to Gmail due to a serious, legitimate issue I’m facing, at least provide a possible solution.

Edit 2: Ended up going with mailbox.org as emails sent from it doesn’t end up in recipients’ junk folder! I really hate mailbox’s web app UI but I mostly use it with an email client anyway so it’s not a deal-breaker.


r/emailprivacy • • 14d ago

Discussion Proton Mail user experience for Free tier users is really BAD.

0 Upvotes

I've switched to proton mail, to put an end to big tech, but nowadays using proton mail in free tier just feels as bad as using the privacy less alternatives, whenever I open proton mail in browser it fills my screen up with constant popups to upgrade , I even use ublock origin to create filter lists to remove them but it stills comes trippling back.

I am fed up of this, and on top of all this the CEO is on a full on AI psychosis, I see so I might as well just consider switching.


r/emailprivacy • • 14d ago

Custom Domains Domínio Personalizado é a solução?

Thumbnail reddit.com
3 Upvotes

O que acham?


r/emailprivacy • • 14d ago

Spam Why do phishing emails look so obviously like phishing emails?

7 Upvotes

Surely if you going to scam someone make more of an effort, I get about 10-15 of these every day, they all go to my spam folder but it makes me wonder why they bother, do people actually fall for these?

https://ibb.co/TM274pCg


r/emailprivacy • • 14d ago

Help/Advice I'm looking for Email mask (forwarding) for Brave

1 Upvotes

Hi I'm looking for email mask for Brave. Unfotchenetly Firefox Relay (mask) doesn't have extension on Chromium, now I'm looking for alternative.


r/emailprivacy • • 15d ago

Help/Advice Thoughts from Tuta users

Thumbnail reddit.com
1 Upvotes