Failed to send notification email

[pixelandbrick]

Question

When processing an email notification on form submit, I receive the following error when sending to the System Email assigned in Craft > Settings > Email:

"Failed to send notification email: {"error":"Notification email error. No recipient email address found."}."

I can successfully send a email to a manual address. I'm assuming this is not a bug, but I'm stumped even after some research.

Formie v3.0.14
Craft Solo v5.5.5

Additional context

[engram-design]

That all seems pretty straightforward. One thing you can check, which is to isolate whether this is an issue with the Queue, is head to a submission in the control panel, and manually trigger the email notification (right-hand sidebar when editing a submission). This won't use the Craft Queue, and can be useful in determining if it's just an issue resolving the system email within the context of the queue.

Let me know if sending the email notification manually helps?

[ul8]

@engram-design I have the same issue and tried what you suggested. It still does not work (and I get the same error in the web log file) but I get a success message on the UI (message successfully sent), so at least that is probably a bug.

Where does error even originate from, I cannot find it in a code search of the vendor folder..?

[engram-design]

The error is raised here. How are you setting the system email? Through an .env variable, or other means?

[ul8]

@engram-design we've set it in project config (no env)

[engram-design]

Does hard-coding it into Formie's email notification make any difference?

[pixelandbrick]

I ended up having quite a few problems to solve in conjunction with this one, so I can't provide a straightforward solution. The more direct pieces ended up being to follow @engram-design 's advice about triggering a manual notification, which led to some additional answers, as well as making sure my queue was configured properly.

For the record, I also discovered DNS issues that I inherited, a problem with a forwarder using ImprovMX, and more. Lots of moving parts to make sure this works well, but the specific issue here was solved using the first paragraph in this response.

Thanks @engram-design for your time, and for your wonderful products.