I've created a new meteor site and I've realized that my email is no longer sending emails. I copied the code from one of my other sites (as that one can send emails) but I still cannot seem to get it working. I've enabled less secure apps and enabled 2-step verification on gmail - but still nothing is working. I'm currently on meteor version 1.5.2. I keep on getting the error Username and Password not accepted
Related
I have implemented the reset password link for my app (using exactly the same firebase code provided at https://firebase.google.com/docs/auth/web/manage-users). It works well when I tried it using a gmail account that I have registered previously on the app (I received the reset password link on gmail and able to change for a new password). However, when I tried it with other email domains (like professional work or school domains e.g #mycompany.com or #school.edu), it does not seem to receive the email (not in junk/spam too). It is very weird because I do receive the 'email verification' link (from firebase) using other domains when I registered using the app but not when I tried to reset the password? Any ideas on how to approach this problem?
As an FYI, currently in Jan 2023, Microsoft 365 business blocks these emails from ever reaching the target mailbox, even if you change the SMTP settings in firebase.
They still appear in your own SMTP sent section, they just never get delivered by MS
Open firebase console goto Authentication then click on Templates > Password Reset then copy given email address (it seems like, 'noreply#YOUR-PROJECT-NAME.firebaseapp.com') then open your Gmail account and paste that email id in search section the tap on 'view message > move to not spam'
This will surly help you
Thanks
Meet Patel
If the code is the same and you don't get an error message, it is extremely likely that the email gets blocked somewhere along to the way to the target mailbox. You'd have to reach out to the system administrator and see if they can find the message somewhere in their spam filters, and ask them to modify the configuration of those to no longer block these messages.
As ganey stated, the problem is that certain email filters such as MS 365 do not accept mails that contain links that are not in pair with the sender domain.
The solution is to add a customized action url that points to the same domain as your sender domain.
Then you need to redirect from that url to the url generated by firebase.
Note:
If you do this in react or another SPA, don't forget to append the query params.
I have a client with a Wordpress website. The contact form stopped sending, so I found a plugin called Mail Integration for Office 365/Outlook that could use his MS365 email to send all email from the website using that account.
I installed the plugin and followed the instructions to create an Azure AD App Registration and configure the plugin with the appropriate data from the App Registration. I tried submitting the contact form and there were no errors on the page (it gave me a success message), but the email never arrived in my inbox (yes, I checked spam). I installed a different form plugin, WP Forms, and put it on a test page. The call to admin-ajax appears to be going through successfully, receiving json with success and a confirmation message (which it outputs to the page).
So I searched the plugin's support forum where the creator mentioned using the plugin Check & Log Email to test that the emails are sending. I installed/activated the plugin and sent a test email. It shows it as sent successfully. It never arrived in my inbox (yes, I checked spam).
I have checked the error logs and didn't see anything helpful.
To fix the issue, I first need to find it:
Do I need to complete additional configuration that I've just missed?
How do I find out if the plugin can even connect to the App Registration? It doesn't have a Test Connection feature, which it clearly needs. The reviews on the plugin page are all positive and recent, so it's working for other people.
How do I troubleshoot this from the Azure Active Directory side to make sure it's receiving data?
Please help! Thanks.
I am using Firebase Authentication in my Ionic App. Some users have reported to not receive the verification email which is sent after a user signs up, or when the resendVerificationEmail is triggered.
This works fine for email providers like #gmail.com or #live.de, but for those other users with special providers like #gmx.at it's not working. The emails are sent successfully according to firebase but they are never received.
Possibly the emails get filtered?
Has anyone else ran into this problem? The message template can not be modified but would using a custom SMTP server possibly help?
The problem is solved by using my own private SMTP server for sending the Authentication emails.
I am using a hosting service for my domain that comes with email service so I am using that one. Using other services such as Mailgun or Mailjet etc. might also solve the problem.
You can set up your custom SMTP server right in the firebase console under Authentication/Templates.
I had the same problem with others emails providers (orange.fr sfr.fr free.fr ...). After deeper analysis, it appeared that it is the domain address inside the (generated) link that is detected as SPAM by emails providers (maybe everything that sounds like *.firebaseapp.com)
https://your-subdomain.firebaseapp.com/__/auth/action...
I changed it to a custom one of mine (through Authentication->templates->"Customize action URL" (bottom right)):
https://www.my-custom-domain.com/__/auth/action
and no more problem!
Some doc (note on blue background):
https://firebase.google.com/docs/auth/custom-email-handler?hl=en&authuser=0#link_to_your_custom_handler_in_your_email_templates
I use Firebase Auth for my solutions.
I get validated users every day - it's working.
I just tried to create two new accounts, using dummy email addresses from my own domain (the domain set up to send Firebase validation emails) and I do not receive messages.
That is, I do not receive the typical validation email.
I manually sent a password reset from the Firebase console to both new accounts; one email showed up.
I'm guessing this is a config issue on my hosted server / domain...but I don't know where to start looking.
Again, there is no issue with validation emails going out successfully - just not to the domain used to send those emails!
I am trying to send a verification email to users upon registration. I'm using Accounts.createUser to add users to the database and that works fine without any email verification system. HThen, when I try implementing email verification by using Accounts.sendVerificationEmail, it does not send any email. I have set MAIL_URL and I'm using Mailgun. When I try sending an email within terminal, it sends as expected. I have tried using the process provided here: https://themeteorchef.com/snippets/sign-up-with-email-verification/ where the method is server-side and then I use Meteor.call to call that method but that isn't sending the verification email. I have also tried implementing Accounts.onCreateUser() and calling Accounts.sendVerificationEmail(user._id) from within but that is also not sending the email.
In my server code I have the following in the startup function: Accounts.config({sendVerificationEmail: true, forbidClientAccountCreation: false}); I've also noticed that when I add in any kind of email verification code server-side, createUser fails and tells me the username is not defined but works 100% as expected without any email verification.
Here are some links to various sources I have been trying to use in order to get this working:
verify email using accounts.ui package
https://themeteorchef.com/snippets/sign-up-with-email-verification/
Meteor 1.3 verify email when creating user
I've also been using the Meteor docs but I can't seem to get it working. I also have installed related packages (email, accounts, accounts-ui). Any help is appreciated!
Thank you to #PankajJatav for asking me to read through the server console more carefully! The problem for me was that I am using mailgun as my smtp service. I was using the default sandbox domain when trying to implement my email verification system but the sandbox domain is only for testing purposes. In order to actually get emails sent, I had to go to mailgun and add in the recipients as an authorized recipient. If you set up mailgun with your own domain right from the start, this shouldn't be an issue.
Once again, thank you to #PankajJatav