Meetin.gs logs every delivery attempt: accepted, rejected, or skipped. Start there before assuming the email was never sent. Delivery requires configured credentials; the reminders page says which messages exist, and the Gmail guide covers sender authentication.
Before you start
- The recipient address, spelled as entered.
- The event that should have triggered the message.
- A second mailbox provider to test with.
How to complete this task
- Confirm the recipient spelling and the event that should have triggered mail.
- Inspect delivery status for accepted, rejected, or skipped state.
- Review sender-domain authentication and provider suppression lists.
- Retry only after fixing the cause, then test with another mailbox provider.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
Mail was accepted but never arrived.
Accepted means the provider took it, not that it landed. Check spam placement, the recipient's filters, and sender-domain authentication.
One provider receives mail and another does not.
That points at domain authentication or reputation rather than the application. Verify SPF, DKIM, and DMARC alignment for the sending domain.
A recipient is suppressed.
A prior bounce or complaint blocks delivery until the suppression is cleared. Fix the cause first — retrying into a suppression achieves nothing.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
