Update README.md with spam prevention #35
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.
I've added a section on how you can prevent mail to be treated as spam. This can be quite common when you change the
from address
to that of a user email address. In fact, it usually will occur if thefrom address
domain is not linked to the sending hostI've spent quit some time to get this working in my old application where I used my own node-mailer solution (but with featherjs backend). That application is a multi-tenancy app, and customers can choose to use DKIM or not. If they do, the information can be entered on a settings form. Each time a mail is sent, the information is collected.