In short: A working mailbox does not prove that a website form successfully generated and sent a message. Test the form, application, SMTP submission and final mailbox as separate stages.
Check the form itself
- Submit one controlled test with a unique subject or reference.
- Confirm that required fields reject blank submissions.
- Check the destination address in the form or plugin settings.
- Review the website or plugin log for a message ID, success result or exact error.
Use authenticated SMTP
Websites should normally submit mail using an authenticated mailbox rather than relying on unauthenticated local delivery. Use the complete mailbox address as the username and a From address that the mailbox is permitted to send.
For Virgo Networks hosted mail, follow the email server settings. Never put mailbox credentials in a public ticket or screenshot.
Check the receiving side
- Look in Spam, Junk and quarantine folders.
- Check mailbox quota, forwarding rules and aliases.
- Test delivery directly to the final mailbox rather than through a forwarder.
- If a bounce exists, keep the complete SMTP diagnostic.
Sender alignment matters
Do not use a visitor's address as the message From address. Put it in Reply-To instead. The From domain should have appropriate SPF and DKIM configuration, with DMARC considered for policy and reporting.
What to send support
Provide the form URL, test time and timezone, expected destination, unique subject, application log result and any bounce. Redact the submitted personal message unless it is necessary to reproduce the fault.
