4 ms·

From [1]: > Does Helm have access to my emails? > The architecture of the system has been designed so that it's not possible for Helm to access your emails. E

From [1]: > Does Helm have access to my emails? > The architecture of the system has been designed so that it's not possible for Helm to access your emails. Email senders now support sending emails over an encrypted SSL/TLS channel where the email is only decrypted once it reaches your personal email server. Helm is not able to decode these emails because we don't have access to the encryption key. In the limited situations where the sender's email server doesn't send the email to you over SSL/TLS, Helm does not log or store these messages and therefore we are still not able to access them. SSL/TLS is transport security, and email is inherently multi-hop, so this reads as bogus to me: each hop might use SSL/TLS but that doesn't mean the message content or metadata is end-to-end encrypted until it gets to my Helm server. [1] https://thehelm.com/products/helm-personal-server-v2 https://thehelm.com/products/helm-personal-server-v2

gsreenivas 5y ago
There are no hops for Helm customers. The TLS connections for their domains terminate on their Helm server.
smitop 5y ago
I don't know how this is actually implemented, but it would be possible to do this as described if the static IP provided by Helm just proxied all incoming packets directly to the personal server, without acting as a relay server at the SMTP protocol level but instead just being a dumb proxy. There's no reason that Helm would need to act as a mail hop at the SMTP layer or do TLS termination anyways. The reason that the using the server's actual IP wouldn't work is that most residential IP ranges are responsible for mostly spam (so most outgoing email would likely be filtered), and some ISPs don't assign static IPv4 addresses to residential users (IPv6 would fix the later issue, but mass IPv6 adoption isn't going to happen for a while).
wmf 5y ago
Realistically email is one hop from the sender's MTA to the receiver's.

gsreenivas 5y ago

There are no hops for Helm customers. The TLS connections for their domains terminate on their Helm server.

smitop 5y ago

I don't know how this is actually implemented, but it would be possible to do this as described if the static IP provided by Helm just proxied all incoming packets directly to the personal server, without acting as a relay server at the SMTP protocol level but instead just being a dumb proxy. There's no reason that Helm would need to act as a mail hop at the SMTP layer or do TLS termination anyways. The reason that the using the server's actual IP wouldn't work is that most residential IP ranges are responsible for mostly spam (so most outgoing email would likely be filtered), and some ISPs don't assign static IPv4 addresses to residential users (IPv6 would fix the later issue, but mass IPv6 adoption isn't going to happen for a while).

wmf 5y ago

Realistically email is one hop from the sender's MTA to the receiver's.