Protonmail

2241 readers

2 users here now

There is now an official Protonmail Community at !protonprivacy@lemmy.world

founded 5 years ago

MODERATORS

imattau@lemmy.ml

Using ProtonMail with a custom, previous imap-capable domain: what happens to the original inbox? (lemmy.ml)

submitted 2 years ago by reallyzen@lemmy.ml to c/protonmail@lemmy.ml

1 comments fedilink hide all child comments

Transitioning to PM (and generally speaking, to Proton For Everything) from Gmail, I was following the manual when I realised that PM wanted to replace my privately-owned, with mailbox service included, mail address.

What I've been doing for 15 years was hide a gmail adress behind my own domain name (quality of apps, quantity of storage, general user friendliness...); people would still see me as me@me.me, but I had the convenience of that google service while writing"as" me@me.

It also offered me a layer of safety, since downtime does happen, and hopping to the poor roundcube webmail interface of my hosting company allowed me to keep business as usual. Believe it or not, google has failed more often than that regional service provider. lol.

Now to the question: Am I right to understand PM will dutifully catch all emails to me@me.me, the DNS settings will kill my old-school IMAP mailbox to push them towards me@proton.me, and I will have to commit to trust Proton 99.95% (their current SLA for customers like me)?

Will I loose that last line of defense, Roundcube Webmail straight from my private provider?

Thanks is advance. For obvious reasons, I'm not on twitter, reddit & all that.

top 1 comments

sorted by: hot top controversial new old

[–] RagingToad 2 points 2 years ago

Yes, that's how it works. If you change the DNS settings it will send everything straight to proton.

Ofcourse you could also do auto-forwarding. But as far as I know this disables the possibility to send from me@me.

It's annoying, isn't it? :-/

I've also noticed that if you want to send from anotherme@me you have to create an identity with that name first, which cannot be done through the app (you need to log in through the browser first). I typically register at services like servicename@me and when I email them they are always confused that I am sending mail from me@me (sometimes they refuse service because they expect me to send from servicename@me) so I have to go through the hassle of creating an identity.

Sure there's reasons for protonmail to work this way - but it's very annoying. I guess there's always a trade-off between security and convenience.