-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding smtp server without user and password #30
Comments
Thanks for reporting, will fix in next release. |
@troubleshootme Upon looking into this, found out that even if you do use gmail, you would still need to use your username, password in the SMTP user and password field. You might still be blocked by google and you may have to go to https://www.google.com/settings/security/lesssecureapps and enable it. |
This is true for free Gmail, I am referring to Google's SMTP relay service for Google Workspace. They give you the option to use smtp-relay.gmail.com and whitelist server IP requiring no SMTP auth. I prefer to use that rather than enable less secure apps. Microsoft 365 also provides a similar service. |
Fixed in latest release. Try pulling the latest docker image and you should be able to add your smtp details without user/pass. |
Thanks!
Tony Bruno / Consultant
***@***.*** / 205.876.3715
Bruno Computer Support
www.troubleshootme.com <https://troubleshootme.com/>
205.876.3715
…On Wed, Dec 21, 2022 at 8:19 AM Towfiq I. ***@***.***> wrote:
Fixed in latest release. Try pulling the latest docker image and you
should be able to add your smtp details without user/pass.
—
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZAVWCNSPEWR7SJCRWKAX2DWOMGW3ANCNFSM6AAAAAASZ2U6RQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I would like to use smtp-relay.gmail.com to send mail out but serpbear requires username and password for mail parameters but my relay auths via IP.
The text was updated successfully, but these errors were encountered: