Email faults can be local to one device, one mailbox, DNS or the whole service.
Applies to: Web Hosting troubleshooting
Troubleshooting is fastest when you identify the layer that failed: DNS, TLS, web server, PHP, application, database or local device. Record exact error text and timestamps before changing configuration.
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.
Work through these checks
- Test webmail first.
- Check mailbox quota and password. Do not include the secret in a ticket, email or screenshot.
- Confirm MX, SPF and related DNS records.
- Record the sender, recipient, time and full error for support.
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
- Read website access and error logs
- Fix a 403 Forbidden error
- Fix a 404 Not Found error
- Fix a 500 Internal Server Error
- Website not loading after a DNS change
Last reviewed: 2026-07-18.
