A successful-looking form submission does not by itself confirm that its email reached the intended inbox.
Steps
- Open the form settings and review the Email section. Enable email sending when required and verify the recipient address character by character.
- Use an appropriate address on your own domain as the sender. Check the edition-specific form and mail requirements before changing DNS or sender settings.
- Save or publish the correction and submit one identifiable test from the public website. Record the time and displayed result.
- Check the recipient’s inbox, junk folder, filters, and mailbox capacity. Compare with a normal message sent to the same recipient.
- Where available, inspect the form’s stored submissions and hosting mail delivery information to distinguish submission failure from email delivery failure.
Check the result
Repeat a single test after the correction and confirm both the website response and actual receipt. Remove any test submission containing personal information when finished.
Before you continue
Sitejet Studio’s customer-portal form storage is not part of the cPanel/Plesk builder. Do not assume a missing email has a recoverable stored copy, or apply Studio-specific mail records to another hosting setup.
A preview test can use Sitejet’s servers, while the published cPanel/Plesk form depends on the hosting environment’s PHP and mail configuration. Success in preview therefore does not prove live delivery. Check the live form once after publication and use a supported PHP version compatible with the integration.
Use the failure to choose the next check
If the live form rejects submission, record the displayed validation or server error and check the failing request. If submission succeeds but delivery fails, focus on the destination mailbox and available delivery evidence. Repeated test submissions can create duplicates. Use a distinct harmless test label and verify the correction with one new submission.
Official documentation: Sitejet guide.
