Alex
My feedback
2 results found
-
18 votes
An error occurred while saving the comment Alex
supported this idea
·
An error occurred while saving the comment Alex
commented
Programmatic email delivery is pretty much a hard-blocker for every organization to switch to Protonmail. I've used the Gmail API to send emails programmatically which is not possible now. What prevents me from doing this now is that I cannot authorize any Gmail account to send emails on my behalf. I cannot authorize Gmail do send emails on my behalf because I cannot specify any SMTP server which would be used to send emails.
Providing SMTP should not be that difficult. I understand that the encryption voodoo won't work but I do not care and as a paying customer I want to be able to accept this disadvantage.
-
111 votesAlex
supported this idea
·
This is pretty much my 10 vote worth issue with your service and the reason why I might look for alternatives and do not prolongate my subscription as I cannot cancel for this reason unfortunately.
I just tied the ProtonMail bridge that can be hacked to use it as a poor man's email relay with just little work for ProtonMail:
Please provide a CLI version of the bridge. The auth, incl. 2FA can be done on the desktop. ~/.config/protonmail/bridge can be inserted into a service container to serve as an STMP@localhost. Still, to sleep well, I would like to constrain the bridge that is deployed in such a way to just sending (SMTP) but not receiving (IMAP) any emails.
@ProtonMail staff