A WordPress enquiry form can appear to work after a hosting move while its email notification never reaches Microsoft 365. The visitor sees “sent”, the website records a submission, but the sales inbox stays empty. That gap deserves a separate acceptance test before a new site is considered ready.
This guide is a practical handover for small businesses in Brisbane and elsewhere. It separates form validation, WordPress mail handling, outbound delivery, domain authentication and mailbox processing. You can use it with your developer or hosting provider without sharing customer records or sending passwords over email. For assistance with a live incident, use TempWebz WordPress technical support in Brisbane and provide the affected page, approximate time and error shown.
Form submission and email delivery are different processes. A form may validate the fields, save an entry and show a success message before or independently of sending a notification. Another form might depend entirely on outgoing email. Identify which plugin is in use, whether it stores entries, and what confirmation actually means. Do not assume a successful screen proves that anybody received the enquiry.
WordPress documents that even a successful wp_mail() result only confirms the sending method accepted the request, not final recipient delivery. Start with four checkpoints: browser submitted the form, WordPress processed the entry, the outgoing mail service accepted the message, and the intended mailbox received it. Record each separately.
Agree on one real public enquiry page and one authorised test recipient. Use a synthetic contact name such as “Website Test”, a clearly labelled subject and a unique reference code such as TEST-2026-11-09-A. Choose a time when the business owner can check their inbox. Do not include real customer details, financial information, attachments or credentials in a test submission.
Record the form URL, browser, test time with time zone, expected notification address and whether the entry was saved. If the website uses payment processing, booking or paid lead routing, do not submit a test that creates a charge or a real booking. Request a dedicated test mode or an approved non-transactional path instead.
A hosting move may change the server IP address, outbound mail restrictions, PHP version, DNS records, security rules and the sender identity available to WordPress. The site can load correctly despite a broken mail path. Ask for the migration change log and compare the previous and new mail delivery methods, not just the visible form configuration.
Before editing DNS, note where the authoritative zone is managed and keep a copy of the existing records. Verify domain ownership, MX targets and any outbound mail provider requirements with the appropriate administrators. A website hosting migration does not automatically mean Microsoft 365 mailboxes must move. Our web hosting migration service covers the planning of DNS, backups, acceptance testing and rollback.
In the form plugin, confirm the notification is enabled and triggered by the correct event. Check the configured recipient address, conditional routing, form confirmation and reply-to address. A rule such as “send to sales when service equals hosting” may silently skip a submission if the field values changed during a redesign.
Check the form’s entry record only within authorised administrator access. An entry present with no notification evidence suggests the submission stage worked, but it does not identify which mail component failed. If no entry exists, prioritise browser validation, JavaScript, spam protection and form handler errors. Keep entry data private and avoid copying it into external debugging services.
The visible From address matters. A site hosted at one provider should not pretend to send directly as an unrelated Microsoft 365 mailbox unless the configured mail transport is authorised to use that identity. SPF describes permitted sending infrastructure, DKIM adds a signature from a configured sending domain, and DMARC describes how receivers evaluate alignment and handling. These records complement delivery troubleshooting but cannot repair a missing form event.
Do not add multiple separate SPF TXT records for the same hostname or paste an example record into production. Obtain the correct instructions from your actual mail provider, identify any transactional email service already in use and plan one consistent authentication configuration. Record existing DNS values before making changes and allow for caching when testing.
Some WordPress sites use a mailer or transactional email API; others rely on the web host’s server. Determine which method is configured. Look for provider logs or a delivery event identifier without exposing keys. If the host blocks the needed outbound connection, changing an email template will not fix it. If a mail provider rejected the sender, the rejection reason is more useful than a generic WordPress error.
For Microsoft 365, review Microsoft’s SMTP AUTH guidance and the supported application-sending options. Microsoft recommends modern authentication where applicable. Do not reactivate weak authentication or lower security defaults merely to make an old connector work; use a supported transport and document who owns it.
With authorised Microsoft 365 admin access, use message trace or the appropriate mail-flow diagnostic tool for the test window. Check the sender, recipient, approximate UTC time, delivery status and rejection reason. A delivered result may indicate the next check belongs at the mailbox, junk folder, quarantine, shared mailbox permissions or inbox rules rather than WordPress.
Make sure the business is searching the right address. “sales@” could be a shared mailbox, an alias or a distribution group, each with different access and routing. Where a form sends to multiple addresses, record their delivery outcomes separately. Our Microsoft 365 setup service can help plan domain and mailbox configuration, but the diagnosis must follow actual evidence.
An inbox search immediately after pressing Submit can be misleading. Check an agreed observation window, the correct time zone, filtering rules, quarantine and provider delivery logs. If messages are delayed, capture the message IDs and timestamps rather than repeatedly re-submitting the same form. Repetition can trigger anti-spam defences and make the evidence harder to interpret.
If a notification is rejected, investigate its specific reason. If it is accepted by the provider but never appears in the mailbox, investigate downstream routing. If no message leaves WordPress, return to the notification trigger and transport. This ordering reduces unnecessary DNS changes and prevents a broad security relaxation from masking the actual defect.
Once the mail path appears healthy, repeat a controlled test on a phone and a desktop browser. Ensure the form is reachable from the relevant service page, inputs are labelled, validation errors are understandable and the confirmation text reflects the true next step. Test keyboard access as well as touch input. A functioning server integration is not enough if the customer cannot complete the form.
Keep the number of required first-contact fields proportionate to the enquiry. For urgent support, the affected URL, contact details and a short issue description are often enough to begin triage. Ask for administrator credentials only later through an approved secure channel and only if necessary. A form should never encourage visitors to email their passwords.
For each controlled test, record four results: whether the browser displayed confirmation, whether an entry was captured, whether the outgoing provider accepted the notification, and whether the receiving mailbox got the correct message. Include a screenshot only if it contains no customer or credential data. Save the outcome alongside the migration change log and the person responsible for the mail service.
A practical outcome might read: “TEST-2026-11-09-A submitted on mobile at 10:40 AEST; entry saved; provider accepted message; sales inbox received at 10:41 AEST.” Another might read: “Entry saved; mail not observed at provider; investigate WordPress notification or mail transport.” Avoid statements such as “Microsoft 365 is broken” without supporting evidence.
If you change sender configuration, a DNS record, a firewall restriction or a form notification, alter one known variable at a time. Save the previous setting and note who approved the work. Retest the original failure with a new reference code and compare the results. If a change makes the situation worse, restore the documented configuration instead of layering more guesses onto it.
For a wider checklist of the migration itself, read our hosting move preparation guide. For a focused explanation of why a “sent” message is insufficient evidence, see the WordPress form enquiry delivery guide. Those companion articles cover the broader topics; this test plan deals specifically with the handoff between a changed website host and Microsoft 365.
TempWebz helps Brisbane businesses investigate WordPress website faults, hosting moves and business email configuration. When contacting technical support, include the public form URL, the migration date, an anonymised test reference and the first checkpoint that failed. Do not submit account passwords or private customer messages in the initial request. The aim is to isolate the fault, agree the scope and verify a measured fix.