Send form and notification mail through an authorised mailbox rather than relying on unauthenticated PHP mail behaviour.
Applies to: WordPress on Tudor Internet Web Hosting
WordPress problems often come from the interaction between PHP, plugins, themes, caching, scheduled tasks and database state. Change one item at a time, record what you changed and keep a known-good backup before updates or repairs.
Key information
| Username | The full mailbox address, for example enquiries@example.com. |
|---|---|
| SMTP server | The secure server hostname supplied for the Tudor Internet hosting service. |
| Encryption | Use the mode associated with the selected submission port; normally implicit TLS on 465 or STARTTLS on 587. |
| From address | Use an address authorised by the mailbox or sending service and keep it aligned with the domain. |
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- Create a dedicated mailbox or authorised sender and use a unique password rather than reusing a personal administrator password.
- Install a maintained SMTP plugin from a trusted publisher and record the current configuration before replacing an existing mail plugin.
- Enter the exact secure SMTP hostname, authenticated submission port, encryption mode, full email address and mailbox password.
- Set a consistent From address and name; avoid allowing arbitrary contact-form values to replace the authenticated sender address.
- Send the plugin’s test message to an external mailbox and confirm headers show the expected authenticated service.
- Submit each live form and test password reset, order or application notifications because a generic test message does not cover every code path.
- Store credentials using the plugin’s secure method or environment configuration where supported, and rotate them when staff or agencies change.
Confirm the result
- The intended hostname loads over HTTPS from a private browser session and serves the correct website.
- Forms, database-driven pages and the administration area work without a new PHP, permission or redirect error.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Receiving works but sending fails. | SMTP authentication, the outgoing hostname, port or encryption mode is incorrect. | Use the full email address as the username and the exact secure SMTP settings supplied for the hosting service; do not use unauthenticated port 25 from a mail client. |
| The same mailbox works in webmail but not on one device. | The mailbox is healthy and the fault is in the device profile, saved password, certificate warning or local network. | Remove only the affected account profile after recording settings, then add it again with IMAP so server mail is not deleted. |
Important notes
- Mailbox storage is part of the hosting plan's total storage allowance. Removing a device profile does not increase server quota, and POP settings can remove messages from the server.
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Hosting email settings for any email application
- Troubleshoot hosting email sending and delivery
- Set up SPF, DKIM and DMARC records
- Troubleshoot a WordPress contact form that does not send
- Recover a WordPress administrator password
Last reviewed: 2026-07-18.
