Send verification email using Mailgun #195
Merged
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.
Resolves #164.
Encountered a couple of issues implementing this, mostly due to the Mailgun docs.
Relevant issues:
v18.0.0mailgun/mailgun.js#269.The FormData object used by the
Mailgunconstructor should be the FormData Web API and not the FormData object made available through thenpmdependency. The import used within the Mailgun guide is thus unnecessary.Currently, the emails sent using Mailgun ends up in the spam folder, so that is something we can maybe look into in the near future. The email addresses that we are sending to should be added to the Authorized Recipients and under the Mailgun free plan, we can also send emails to a maximum of five users per month.