What does this service cover?
Email delivery fails in layers, and each layer belongs to a different owner. WordPress or the sending application creates the message; the SMTP configuration authenticates it; DNS records such as SPF, DKIM and DMARC authorize it; the receiving server judges it; spam filters and mailbox rules file it. A fix aimed at the wrong layer wastes time and can make things worse — for example, changing MX records when the real problem is an unauthenticated contact form.
That is why diagnosis starts with the route, not the symptom. Confirming the domain, the mailbox provider, the website host and the exact sending path used by forms or applications takes minutes and prevents hours of fixing the wrong system. Only then are DNS records inspected against the provider configuration actually in use, and only then does the website's mail configuration change — with controlled tests proving each fix before the next layer is touched.
Trace where mail should go
Confirm the domain, mailbox provider, website host and the route used by forms or applications. This prevents fixing the wrong system.
Check DNS and authentication
Review MX, SPF, DKIM, DMARC and relevant host records for obvious conflicts or missing values. Changes are made only against the provider configuration actually in use.
Fix website mail configuration
For WordPress, this may include SMTP configuration, sender alignment, plugin settings or form routing. The goal is reliable delivery with credentials stored outside public code where possible.
Test and document
Send controlled tests, check the expected destination and document any provider-side limitation or propagation delay that remains outside the website itself.
What is the typical scope?
Every engagement starts from the same place: a clear, agreed list of what is included before any work begins.
- Website forms not delivering mail
- MX, SPF, DKIM and DMARC records
- Domain, nameserver and DNS configuration
The exact scope is confirmed from the real site and problem before changes are made.
How does the work proceed?
- Map the mail path: confirm the domain, mailbox provider, website host and how forms or applications send mail, so the right system gets fixed.
- Inspect DNS and authentication: check MX, SPF, DKIM, DMARC and host records for conflicts or missing values against the provider actually in use.
- Fix the sending side: configure SMTP, sender alignment, plugin settings or form routing, keeping credentials out of public code.
- Test and document: send controlled tests to the expected destination and document any provider-side limits or propagation delays.
What you need to provide
Most of the technical work is on my side. To start, I usually need:
- The affected domain and a description of the symptom
- Access to DNS management, or a current export of the records
- WordPress admin access if website forms are involved
- Mailbox provider details (Google Workspace, Microsoft 365, cPanel mail, etc.)
Typical timelines
Most email and domain issues are diagnosed within a day and resolved in 1–3 days. DNS changes can add propagation time, which is accounted for in the plan rather than billed as waiting.
Frequently asked questions
My contact form says “sent” but I never receive anything — why?
The message is usually generated but fails later: unauthenticated SMTP, a From address the provider rejects, spam filtering, or a broken mail route. I trace each stage to find exactly where it stops.
What are SPF, DKIM and DMARC?
DNS records that tell receiving servers your mail is legitimate. SPF lists allowed senders, DKIM cryptographically signs messages, and DMARC tells receivers what to do with failures. Missing or conflicting records are a top cause of mail landing in spam.
Can you fix email going to spam?
I can fix the technical causes — authentication records, sender alignment, SMTP configuration. Reputation problems from past bulk sending are a separate, slower recovery process, which I will identify honestly.
Will fixing website email affect my company's mailboxes?
No, when done carefully. Website (transactional) mail and mailbox mail are separate flows; I keep them that way and verify both after changes.
Do I need an SMTP plugin for WordPress?
Usually yes. PHP mail from shared hosting is unreliable and often unauthenticated. A proper SMTP setup with your provider's credentials dramatically improves delivery.
How do you test without emailing real customers?
With controlled test addresses and log inspection — never by sending to your real contact list.
Keep the scope proportionate
This covers normal website, domain and mailbox configuration issues. Enterprise mail migrations, large Microsoft 365 or Google Workspace tenant projects and advanced mail-server administration are outside this focused service.
Before starting, we agree on access, the requested outcome, testing and anything clearly outside the job. Hosting subscriptions, premium software and third-party charges remain separate unless stated otherwise.
Start with a clear scope
Describe your website and what needs to happen. You will receive a fixed scope, price and timeline before any work starts — no passwords needed at the enquiry stage.