In the latest version (24.8.11) it’s now possible to send emails using HTTP protocol in addition to SMTP protocol.
This allows much easier configuration (unlike SMTP) where you only need to enter two fields:
URL of the HTTP server
Email address to which replies should be sent to
Manager.io runs its own public HTTP server at email.manager.io.
When you use email.manager.io, emails will be sent from no-reply@email.manager.io but reply to address will be your specific email address so when your recepients reply to emails sent from Manager.io, they will still arrive to you.
This should make it easy for everyone be able to send emails from Manager.io even if they don’t have or don’t know how to configure SMTP server.
Please note that SMTP protocol’s advantage over HTTP is well-known as regards to delivery. Please note that these are Send and not Receive protocols such as IMAP and POP. As such Manager enables you to send emails but not receive them.
Just a sysadmin here thinking out loud - I hope the devs took some time to think through the security and privacy angle of this.
Are emails relayed logged/copied by NGSoftware? For how long? Do you retain records of the destination email addresses? What do you do with that? Do you keep copies of the bodies? Attachments? What third party processors does NGSoftware use? Do they log/copy emails?
What happens if a malicious actor gets onto your HTTP email relay and embeds themselves? How will you know that happened?
How is this authenticated? Presumably anyone can send mail on behalf of the domain email.manager.io regardless of the content of their message.
How is this rate limited?
I like the idea, but I feel this should instead be something that needs at least a registration method OR it should be configured by the end user. For example, the end user sets up an Azure Subscription, creates an Azure Communication Service resource (or whatever the equivalent is in another cloud) and Manager enables the user to set up the options.
Error 535:
"The 535 Incorrect Authentication Data error is a specific response code indicating an authentication issue during the email sending process. When an email client tries to send a message, this error message is the server’s way of communicating that it cannot authenticate the sender’s credentials.
Typically accompanied by a message like “535 Incorrect authentication data,” this error points to a problem with the login credentials that are being used. It’s a clear sign that the server is rejecting the access request due to a discrepancy in the authentication details provided."