WordPress website sending spam: what to check on the server
Has your host reported spam sent from your WordPress website or server? What to check before re-enabling email.

Your hosting provider tells you that your WordPress site or server is sending spam. The message can talk about abnormal outgoing emails, saturated queues, PHP scripts that send messages, degraded email reputations or temporary blocking of mailings.
However, the site may seem normal. The home page appears, the administration answers, the form still exists. The problem is mainly on the server side, in the logs, in the email returns or in the hosting provider panel.
Installing an SMTP plugin or restarting email without identifying the source is the wrong response. If spam comes from an abused form, injected file, compromised account or scheduled task, sending can restart as soon as restrictions are lifted.
Quick response
Signal
Outgoing spam
Emails sent from the server, form, script or compromised account.
Priority
Find Source
An email block does not yet tell if the problem comes from the site, SMTP or server.
To be kept
Logs + examples
Keep the hosting provider message, sending times, script paths and error returns.
What a spam sent from the server means
A spam sending from the server means that messages leave, or attempt to leave, from the environment that hosts the site. This can go through the server mail function, a WordPress form, a plugin, a PHP script, an SMTP account or an automated task.
The hosting provider can only cut the sending of emails, limit the account, suspend the site or request a correction before reactivation. The subject, therefore, is not just the reception of messages. It also affects the security of the site, the reputation of the domain and the confidence of email services.
Difference with spam received by form
Receiving a lot of unwanted messages in an email box is not exactly the same as seeing the server sending spam to the outside.
If your box receives noise, the subject may be the form, the antispam or the captcha. The article on the WordPress form that sends spam deal with this scenario. Here, the signal is more server: the hosting provider sees abnormal outgoings or scripts that generate emails.
Read the message of the hosting provider before acting
The message from the hosting provider often gives the best clues. Before editing WordPress, get the available information: time of sending, volume, script path, sender address, recipients, queue, error return or blocking rule.
Frequent causes
The outgoing spam can have several origins. The correct diagnostic review is to separate them instead of correcting them at random.
Abused form
A form can be used in loops if the antispam protection is too weak or poorly adjusted.
Injected Script
A PHP file added in WordPress, theme, plugins or uploads can send messages.
Vulnerable plugin
A vulnerability in a plugin can allow sending emails or adding suspicious files.
Compromised account
A WordPress, SFTP, hosting or SMTP access can be used without the home page changing.
Scheduled task
A cron task or automated process can restart mailings after partial correction.
Domain misconfigured
Absent SPF, DKIM or DMARC settings do not necessarily create spam, but complicate deliverability.
What should not be done too quickly?
Do not assume an SMTP plugin cleans up the problem. SMTP can make email more reliable on a healthy website, but it can also provide a better sending route for a website that remains compromised.
Do not reactivate emails with hosting provider without proof of correction. Don't just change the WordPress password if the script comes from the server. Do not delete a useful form without checking if it is actually the source. Don't restore an unknown backup if you don't know how long the mailings started.
Method to stop spam without breaking the site
The goal is to stop unwanted mailings, find the source, clean what needs to be cleaned and test useful emails after correction.
- Keep hosting provider message, available logs and rejected email examples.
- Create a backup of the current status before deleting files or plugins.
- Identify whether the mailings originate from a form, script, SMTP account, WordPress or server.
- Check files, uploads, plugins, theme, admin accounts and planned tasks.
- Control the email settings: sender, SMTP, SPF, DKIM, DMARC and addresses used by the forms.
- Remove suspicious scripts, correct the form, update or replace vulnerable plugins.
- Change critical access details: WordPress, hosting, SFTP, database, SMTP and linked boxes.
- Test useful forms and emails before requesting the removal of the blockage.
To be sent for a diagnostic review
The hosting provider's message and sending times often allow you to get back to the source of the spam faster.
If the hosting provider blocked the emails or the site
If the hosting provider blocked only outgoing email, the website may remain visible while forms, notifications, orders or WordPress alerts stop sending. Test these functions after correcting the problem.
If the hosting provider has suspended the site, start with the exact reason for blocking. The article on the WordPress site blocked by hosting provider details this scenario. If suspicious files are also reported, read the guide on malicious files detected by the hosting provider.
What about the domain's email reputation?
When a server sends spam, the email reputation can be affected. Legitimate messages may then arrive in spam or be rejected, even after the technical correction.
You must check the sending settings, the addresses used by WordPress, the email DNS, the error returns and the reception tests. Then check that the useful messages are well sent and received.
When to ask for an intervention
Ask for help if hosting provider threatens to suspend the account, if logs mention an unknown script, if emails are blocked, if WooCommerce is active, if forms generate important requests or if you don't know which access is still reliable.
The budget is discussed after the first reading of the hosting provider message, logs and available access. A simple abused form, an injected script, a suspended server or a reinfection do not require the same work. In order to understand the criteria of the quote, the article on the hacked WordPress website cleanup page remains the right complement.
Frequently asked questions
Why does my WordPress site send spam?+
Spam can come from an exploited form, from an injected script, from a vulnerable plugin, from a compromised account, from a poorly protected SMTP or from a malicious file on the server.
Should we cut all WordPress emails?+
It may be useful to temporarily block the sending to stop the incident, but the source must be identified. Cutting emails without diagnostic review can mask the problem and break useful forms.
Is SMTP enough to stop outgoing spam?+
No. A SMTP can improve deliverability when the site is healthy, but it does not correct an abused form, an infected file, a compromised account or a planned task that restarts mailings.
What to answer to hosting provider after correction?+
Respond with concrete actions: identified source, deleted scripts, protected form, changed access, verified plugin, controlled logs and sent tests performed.
