![]() ![]() Usually these providers have free plans available that are comparable to the daily sending limits of Gmail. ![]() To prevent having login issues you should either use OAuth2 (see details here) or use another delivery provider and preferably a dedicated one. So if you authenticate as and set as the from: address, then Gmail reverts this and replaces the sender with the authenticated user. Gmail also always sets authenticated username as the From: email address. If you are using 2FA you would have to create an “Application Specific” password for Nodemailer to work. Without this, less secure connections probably would not work. ![]() When using this method make sure to also enable the required functionality by completing the “Captcha Enable” challenge. You can configure your Gmail account to allow less secure apps here. ![]() For example you might run into trouble if your server is in another geographical location – everything works in your dev machine but messages are blocked in production.Īdditionally Gmail has came up with the concept of “Less Secure” apps which is basically anyone who uses plain password to login to Gmail, so you might end up in a situation where one username can send mail (support for “less secure” apps is enabled) but other is blocked (support for “less secure” apps is disabled). Gmail expects the user to be an actual user not a robot so it runs a lot of heuristics for every login attempt and blocks anything that looks suspicious to defend the user from account hijacking attempts. Even though Gmail is the fastest way to get started with sending emails, it is by no means a preferable solution unless you are using OAuth2 authentication. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |