Email Testing Configuration

CheckView utilizes webhooks to simulate incoming email servers during the testing of emails triggered by form submissions. This process redirects email notifications from the original recipients to our secure test inbox, enabling us to verify successful email delivery. However, this method has certain limitations regarding the volume and content of emails that can be effectively tested.

Current Testing Capabilities

When testing form submissions that send emails, CheckView’s webhook integration is designed to confirm:

• Email Delivery: We verify that an email is indeed sent and received via our webhook, ensuring that the form submission triggers the expected email action.

However, please note:

• Email Content: CheckView does not inspect or validate the content of the emails sent. Our testing focuses solely on the email’s successful delivery rather than specific text, attachments, or formatting within the email.
• Email Quantity: We do not track the number of emails sent. CheckView simply verifies that an email has been received, without checking if multiple instances or duplicates were sent.

Webhook Limitations

While webhooks are effective for basic email delivery confirmation, they may not cover all email-related scenarios. For instance, certain email services or configurations may handle emails differently, potentially affecting the way they interact with our webhook-based simulation.

Email Diversion Limitations

While we make every effort to redirect all email notifications to our test inbox for verification, the process is not entirely failproof. Certain emails, particularly those sent via CC or BCC, may bypass the redirection and reach their original recipients. If this is a concern, we recommend conducting tests using your own email address as the recipient to ensure complete accuracy.