Use go-smtp for UTF8 support and LOGIN authentication implementation #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR suggests using https://github.com/emersion/go-smtp and https://github.com/emersion/go-sasl/ libs for SMTP. It will benefits from :
auth.go)SMTPUTF8 is great to add support for homoglyph attack in Gophish (see gophish/gophish#2110). However, this need both the sender SMTP server and the recipient mail server to support SMTPUTF8 (successfully tested with Office 365 and Gmail) :
One caveat though, CRAM-MD5 support is not enabled in go-smtp (but this could be externally implemented). See emersion/go-sasl#15