Procédure

LPI-RATE01 and LPI-RATE11 error codes: too many emails sent from your site

The LPI-RATE01 and LPI-RATE11 codes appear when a site sends a large number of emails using the PHP mail() function.

They can be triggered by particularly high normal activity, but also by a hijacked form, a poorly configured extension, or a compromised site. This help article lets you find the source of the sends and prevent the problem from happening again.

Understanding the LPI-RATE01 and LPI-RATE11 codes

These two codes monitor emails sent with the PHP mail() function, also referred to as mail_php in LWS tools.

The temporary block protects your hosting and the reputation of its sending servers. Waiting for it to end is not enough, however: you must look for the cause [PERSON_NAME] reproduise.

[PERSON_NAME] emails sent by your site

From your hosting management in the LWS Panel, open the Mail tracking tool.

Select a period corresponding to the time when the code was detected, then look for emails sent from your domain.

Messages coming from the PHP mail() function are identified with a technical sender in the form:

[EMAIL]

This sender is not a real email mailbox. It indicates that the message was generated directly by a site or script installed on your hosting.

[PERSON_NAME] notably:

• the date and time of the sends;
• the number of messages concerned;
• the recipients;
• the subject of the messages, when available;
• their delivery status.

[PERSON_NAME] then determine whether these sends correspond to expected activity on your site.

You recognize the sends

The emails may come from normal activity, for example:

• order confirmations;
• notifications sent to administrators;
• messages coming from a form;
• alerts generated by an extension;
• a campaign launched from the site;
• an automatic task.

When the volume is intentional, check that the site is not sending the same message multiple times. A misconfigured extension, an automatic task that runs too often, or a loop in a script can cause thousands of sends in a short time.

Reduce the frequency of notifications or fix the extension concerned. For regular sends, preferably configure authenticated SMTP sending or use a specialized service suitable for mass campaigns.

You do not recognize the sends

Unknown sends may come from:

• a form used by bots;
• a vulnerable or misconfigured extension;
• a malicious file;
• a CMS that is no longer up to date;
• compromised administration credentials.

Start by updating your CMS, its extensions and its [PERSON_NAME]. Temporarily disable recently installed extensions or those that manage forms and notifications, then check [PERSON_NAME]>

If your site has a form, add anti-spam protection or a CAPTCHA. Also check that the form limits the number of submissions and does not allow the recipient address to be chosen freely.

[PERSON_NAME] then run a scan with the antivirus and anti-malware tool available in the LWS Panel.

If a compromise is confirmed, also change the passwords associated with the site:

• CMS administration;
• FTP accounts;
• databases;
• accounts with access to the hosting.

Use different and sufficiently long passwords for each access.

Waiting for the end of the LPI-RATE11 block

The block associated with the LPI-RATE11 code lasts one hour.

[PERSON_NAME] to find and fix the source of the sends. Once the delay has ended, emails generated by PHP can again be [PERSON_NAME] overrun is detected.

Avoid immediately restarting a large send. Start by performing a single test.

Checking that the problem is resolved

After the block ends, send a test message from the relevant function: contact form, order, notification, or another site action.

Then open Mail tracking and check that:

• the test message appears with the sender [EMAIL];
• its status indicates that it was processed;
• no new mass or unexpected send is recorded;
• the LPI-RATE11 code does not reappear.

Common issues

The LPI-RATE11 code reappears after one hour

[PERSON_NAME] [ADDRESS] cause of the sends is still present. Check the mail tracking again and inspect the forms, extensions, automatic tasks and files on the site.

If necessary, temporarily disable the sending function or extension responsible in order to stop the sends during diagnosis.

My form is still not sending any message

First check [PERSON_NAME]. [PERSON_NAME] then a single test and check its status in mail tracking.

If the message does not appear, the problem may come from the form or the script [PERSON_NAME]. If it appears with another error, see the help corresponding to the new code displayed.

[PERSON_NAME] site is responsible

When several sites are installed on the same hosting, compare the time and subject of the messages with the forms and notifications used on each site.

You can also temporarily disable sending functions on one site at a time in order to identify the one generating the messages.

I cannot identify the source of the sends

[ADDRESS] LWS support with the following information:

• the exact [PERSON_NAME] code;
• the domain concerned;
• the approximate date and time of the overrun;
• the CMS or application used;
• the sends observed in mail tracking;
• the checks already carried out.