Provide SMTP access

[EthraZa]

This is a request for a much needed SMTP access feature to take Simplelogin.co to an all new enterprise level.

Right now, if we migrate our company emails to SL, for example, if we need to send a single email to a random costumer or partner and have to go all the way to create a reverse-alias, that would be a pain and basically prevent us to adopt SL as our enterprise email solution.

If SL opens up SMTP so we can login with aliases, even with a heavy limit on sending amount by hour/day and even in a new paying tier, that would be superb.
SL already allow us to send e-mails, so it would be nothing really new, it would just send e-mail using our aliases instead of using our reverse-aliases - Simple like that.

For all of you who would like to send daily email with your alias, without resorting to the reverse-alias feature, please,

• vote it up.

Then It would be possible to do something like this:

ie. on Gmail, on Config, Send E-mail as...

SMTP host: smtp.simplelogin.co
Port: 587
User: [email protected]
Password: "An API Key"

• Edited to be a feature request

[nguyenkims]

@EthraZa SimpleLogin doesn't provide a direct SMTP access and currently, the only way of sending emails is to use reverse alias. As SimpleLogin isn't a transactional email service (e.g. SendGrid), we don't open SMTP access.

[ghost]

i hope you will make this opt-in if you do it (or protect it by at least some 2FA mechanism) like for instance concat APIkey and OTP" in the api key (first time only) like that your server check the api key if valid check the otp first time to identify and after that totally ignore the otp part of the api key.

[xenstar]

@EthraZa SimpleLogin doesn't provide a direct SMTP access and currently, the only way of sending emails is to use reverse alias. As SimpleLogin isn't a transactional email service (e.g. SendGrid), we don't open SMTP access.

Just like Esthraza said, we just need it for daily use. Maybe you can limit the sending to 20-50 emails per hour, in this way, people will not abuse the service. But SMTP feature will take simple login to another level for sure.

[trikotret]

I doubt they'll add it since simpelogin joined Protonmail.

[xenstar]

I doubt they'll add it since simpelogin joined Protonmail.

I contacted their support, they said they already have it on the timeline and they will launch it after a few months. It seems like they are just afraid, that people will abuse their SMTP server.

[edsimpsons83]

I doubt they'll add it since simpelogin joined Protonmail.

I contacted their support, they said they already have it on the timeline and they will launch it after a few months. It seems like they are just afraid, that people will abuse their SMTP server.

Protonmail provides SMTP access, you think they could just duplicate the quota / throttling that they use.

[trikotret]

This would be sick if you can add smtp access to SL. You definitely would not need google workspace anymore

[xenstar]

You are right.

[mygrexit]

That would be so awesome. Especially for people with websites/forums.

[armandolas]

That would be great, ImprovMX has this feature, which allows the use of "send mail as" in Gmail instead of having to create a reverse-alias to every new email we want to write

[trikotret]

This is the perfect time to get it done since google is dropping the free legacy Gsuite accounts on July. Im sure lots of gsuite users are looking for alternatives to take their domains.

[ghost]

Me for that i use a paid tier of tutanota (because twelve buks to support them isn't really much, but nothing prevent you to do the same on free tiers), and reverse alias to send message from my mail.

You can do it too with proton if you prefer (i have choosen tutanota for their "in dev" quantum resistent encryption algo and because it's cheaper than protonmail overpriced).

[twratl]

I came here looking for this! I agree it is an opportunity to steal some business from Google. I am most certainly looking for alternatives and would love to see SimpleLogin build out this feature.

[ghost]

I came here looking for this! I agree it is an opportunity to steal some business from Google. I am most certainly looking for alternatives and would love to see SimpleLogin build out this feature.

The problem it's the feature request hitself to replace google Simple login must pass from "alias services" to "email provider".
So instead of "provide SMTP access" you must ask "Provide Email services".

[edsimpsons83]

Agreed, with Google getting rid of the free legacy Gsuite, I am looking to move and this feature would be awesome.

[developStorm]

+1 for this. Implementing SMTP will also allow better forwarding. It will not be necessary to modify any of the original mail headers, remove need for changing sender address and keep the original DKIM signature valid, as the replacement can be done by inbond SMTP server transparently.

[jbarr]

Obviously this would change the scope of SL, but it would make SL a one stop shop, so please take my money. BUT I do get it that you should also focus on doing one or a few things extremely well instead of trying to be ineffectively all things. Still I'm up voting.

[sahilph]

Hello all,

I have created a PR #869 for this. Please check.

Thanks.

[xenstar]

Thank you so much. It looks promising, hope the team will add this feature soon.

[EvilAaron]

edit: just reading PR #869 , looks exciting, can't wait for it to roll out will solve that 1 fly ;)

Just setting up SimpleLogin here for the first time, imported some domain names and really like it and likely buying a year plan.

The fly in the ointment is no SMTP for "reply as" support. reverse-alias is very clunky and in no way can ever pass WAF factor here. NEED a better solution :/

[kwanm84]

Just like to add my support for this feature.

I'd like to be able to have my wife use my custom domain without having to add new reverse alias every time she wants to email someone. Happy to pay (a little) extra for SMTP access.

[argarner]

Considering the Proton acquisition of SimpleLogin, how mutually beneficial this would be to both services value proposition, and the significant value-add to all domain owners, it would make a lot of sense to enable the SMTP capability for all Proton premium/paid accounts at no additional cost, while charging an additional fee for standalone SimpleLogin SMTP (which I imagine could still leverage a lot of the same Proton SMTP infra/code).

This would fill the gap for consumers and businesses who want to move to a privacy oriented email provider, but don't want to be forced to use Protons extremely limited suite of client applications and capabilities.

I would strongly urge both Proton and SimpleLogin to look into designing a next-generation SMTP component that encapsulates the features of both ProtonMail & SimpleLogin to supercharge the privacy and security of all users, while expanding on their existing featuresets – the capability for consumers and businesses to own their private encryption keys and data, allow the use of any client-side application, etc. The fact that Proton requires hosting of private keys has been the main criticism and limitation of Proton since it's inception (a truly private, future proof, service provider would offer the capability to function solely as a encrypted data store/relay, instead of the E2E owner of all that data stores integrations). The fact that SimpleLogin does not have zero-access encryption, and is susceptible to breaches exposing user data (including which emails are associated with every single alias) is the single largest risk in using email aliases (A single breach could destroy all of the efforts of SimpleLogin's users, in trying to obfuscate their identities from big tech and surveillance capitalism, as well as the entire value proposition of the service).

[adriy-be]

Hope this feature come soon 😁

[leoleoasd]

Hi all, for anyone who needs it, I wrote an SMTP relay for simple login:
https://github.com/leoleoasd/simple-login-smtp-relay/

It works like a regular SMTP server: you send an email to it, it reads the alias from the email and automatically creates reverse alias for all your recipients, then forward it to your actual mailbox (such as Gmail).
And I don't think that this brings people the ability to abuse it. People can already programmingly create reverse alias and send emails with their own mailbox in bulk. If we are going to avoid being abused, I think we need to limit the API calls to create contacts and a rate limit for replying to emails.

[trikotret]

I am actually using SMTP2GO Smtp access on Gmail. I setup a SMTP email on Gmail. If I need to email anyone, Ill start the email with SMTP email. When someone replies,I will then get a reverse email to reply. I then use my main default address to reply and so on. I set up always reply from default address. SMTP2GO is free for 1000 emails a month.

[hax4dazy]

@simple-login any chance this can be looked at again? I'd assume that the PR at #869 has to be reworked a bit because its heavily out of date but I am actually interested in this feature

[numanzahid]

Hope to see this feature implemented soon.