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
Remove restriction that SMTP auth requires TLS #2929
Comments
For context, on the Cloudron, we use a local mail server with auth. This doesn't work well with mattermost because of the tls restriction. In addition. mattermost also requires a valid cert (a self-signed doesn't seem to suffice). |
This allows mattermost to use a non-tls connection with a SMTP server that supports PLAIN auth (but not LOGIN). The go library explicitly allows PLAIN auth over non-tls connections - https://golang.org/src/net/smtp/auth.go#L55 Fixes mattermost#2929
Thanks @gramakri - Closing this issue, and we will accept the PR after the small changes are made. |
@lfbrock I have been tied with other things now :-( I will get to this, thanks for the feedback. |
This allows mattermost to use a non-tls connection with a SMTP server that supports PLAIN auth (but not LOGIN). The go library explicitly allows PLAIN auth over non-tls connections - https://golang.org/src/net/smtp/auth.go#L55 Fixes mattermost#2929
This allows mattermost to use a non-tls connection with a SMTP server that supports PLAIN auth (but not LOGIN). The go library explicitly allows PLAIN auth over non-tls connections - https://golang.org/src/net/smtp/auth.go#L55 Fixes mattermost#2929
This allows mattermost to use a non-tls connection with a SMTP server that supports PLAIN auth (but not LOGIN). The go library explicitly allows PLAIN auth over non-tls connections - https://golang.org/src/net/smtp/auth.go#L55 Fixes #2929
mattermost does not set auth if TLS/Starttls is disabled. It was mentioned in #187 that this is a Go library limitation.
I am wondering if this is indeed the case. There was a discussion about this in https://groups.google.com/forum/#!topic/golang-nuts/VjJC2BjmU2E and it resulted in golang/go@ca24f9e.
The text was updated successfully, but these errors were encountered: