Form email notifications not received

The contact form on my site ornate-babka-d4e225.netlify.app is no longer sending notification emails even though the notifications are set up.

Also, the Netlify support form rejected my submission, claiming my email address was not associated with a Netlify account.

How can I fix these issues?

Hiya, sorry you are having trouble getting your forms to work.

This Support Guide is the first port of call to debug any forms issues. Please start here and work through these resources!

We also recommend trying to search the forums or look at topics tagged Netlify forms if you haven’t already - it’s likely your question was already asked by someone else!

If you are still having problems, please provide more information such as what you have already tried, and a link to your live form. :slight_smile:

My form is at ornate-babka-d4e225.netlify.app and I’ve searched the forums extensively without any luck, including the support guide linked above.

My form is working, since I’m instantaneously receiving submissions in the Netlify dashboard. The problem seems to be with the email notifications not being sent. The form is named “contact” in my site’s dashboard.

The only solution I can think of requires requesting support to unblock the email addresses from a block list. I recently changed email service providers, so maybe there was some downtime and therefore my emails were flagged?

Hi, @garrxtt. I’m showing successful email deliveries to both email addresses on file for the form notifications here:

https://app.netlify.com/sites/ornate-babka-d4e225/configuration/notifications#form-submission-notifications

The timestamp of the delivery confirmations was 15:44 UTC which is approximately 39 minutes after you post above. Would you please let us know if you do not see those emails in your inboxes?

Yeah, I wish I knew what happened that suddenly got it working again. Thanks.

I’m not showing that either email address was on the hard bounce list. So I’m not sure why it suddenly started working. Wish I had more news to share, checking on this I’m not showing that any changes were made on our end to resolve the issue.