Weekly report sent several times instead of one time

  • Resolved bendev

    (@bendev)


    1 year, 11 months ago

    Hello,

    I’ve been using Ithemes Security many times for several sites, and For now it was for me a really great and trusted tool.
    But recently, on a web site, I’ve installed the last version of IThemes security, and as I usually do, I activated weekly security report.

    On the first try of the extension to send the report, I’ve faced a huge issue, because the mail for the report has been sent more then 500 times in a row at the recipient, instead of sending only one mail.
    The result is that this has been considered as a spamming campaign from the host of the website, and so the hosting has been desactivated.
    I had to desactivated the extension for now to justify a correction and get the host back to activate the hosting.

    I may have a sending mail issue on the site (I’m on the way to manage this with a smtp mail sender tool), but my question is: how could this huge amount of mails sent occured?
    It’s like if the report had been sent as many times as the number of security issues that were found…

    I hope this a already known issue that comes with a solving tips (but I didn’t find any with few researches).

    Thanks a lot in advance for any return and help.
    Ben.

    • This topic was modified 1 year, 11 months ago by bendev.
Viewing 9 replies - 1 through 9 (of 9 total)

  • Hi @bendev,

    Without being able to put my finger on the root cause I can explain why it is possible so many Daily Security Digest emails are being send.

    It’s because the check for scheduled email notifications is (by default) hooked to the WordPress init action.

    That means EVERY (frontend or backend) request to the site can potentially send one (or more) scheduled email notification(s).

    Now, it is possible to change the default behavior. Instead of performing the scheduled email notifications check on every page load you can offload it to WP Cron. You only need to add the line below to the wp-config.php file:

    define('ITSEC_NOTIFY_USE_CRON', true);

    This should considerably lower the number of Daily Security Digest emails send (even without fixing the root cause).

    Fixing the root cause will probably require additional tracing/debugging in your env.

    +++++ To prevent any confusion, I’m not iThemes +++++

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @bendev, I hope the information provided by nlpro helped resolve your issues. Since we haven’t received a response, I’ll mark this post resolved. If you still need some assistance, feel free to open a new support topic, and we’d be happy to assist. Thank you!

    Thread Starter bendev

    (@bendev)

    Hello,
    As I had to disable the weekly report to stop the issue, and as I’m waiting for the host company to solve a mailbox creation issue to get at least one mail address related to the domain name, I haven’t tested yet the workaround you provided…

    Thread Starter bendev

    (@bendev)

    Hello,

    I’m coming back there after having solved many issues with the sending mail process of the website.

    I’m now sending all mails via Brevo (ex sendinblue), so via SMTP protocol.
    I’m still using the line below to the wp-config.php file:

    define('ITSEC_NOTIFY_USE_CRON', true);

    Each mail from every extensions is well sent (contact, newsletter, statistics) except for iThemes Security’s ones…

    Mails sent by iThemes Security seems to have an issue in xml structure, so at the end of the content, we can see a “Expected either a number, string, keyword or identifier” notification, and the mail is stated as “Error”.

    Here is the start of the xml content of the mail retrieved from Brevo log:

    28-05-2023 16:51:43
send mail to client: process message: process multi part: process part: process body: process part body: get encrypted message: render template: parse render template: Pub/Sub ack: parse render template: parse: body: from string: tpl: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" lang="fr-FR"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>Sauvegarde de base de données</title> <meta name="viewport" content="width=device-width"> <style type="text/css"> /* From: https://litmus.com/community/learning/13-foundations-email-coding-101 */ /* GENERAL STYLE RESETS */ body,#body-table,#body-cell{height:100%!important;width:100%!important;margin:0;padding:0;} img,aimg{border:0;outline:none;text-decoration:none;} .imageFix{display:block;} table,td{border-collapse:collapse;border-spacing:0;} /* CLIENT-SPECIFIC RESETS */

    And here is the end of the xml content of the mail retrieved from Brevo log:

     Cet e-mail a été généré par l’extension iThemes Security.<br>Pour vous désabonner de ces notitications, rendez-vous dans <a  style="color: #0084CB">les réglages</a> de l’extension iThemes Security. </span> </td> </tr> </table> </td> </tr> </table> </td> </tr> </table> </td> </tr> </table> </td> </tr> </table> </center> </body> </html> '] Expected either a number, string, keyword or identifier.

    If it helps, I can give the whole xml content of the xml content of the mail retrieved from Brevo log…

    Thanks in advance for any help or tick to solve this issue…

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @bendev, does the error show when you view the iTSec emails on different browsers? It looks like a JS error, but I couldn’t find any related ticket of the same issue on iTSec, so I’ll ask our developers for advice. Please send a copy of the whole XML content here and mention my username. Thank you.

    Thread Starter bendev

    (@bendev)

    HI @shanedelierrr ,

    Thanks for this answer.
    So, the mail content is well display if I put it in a html file and open it in a browser.

    But it seems that there is something wrong in it that put it in error when the SMTP service tries to send it (maybe a structural balise issue ?).

    I tried the link to send you the whole mail content, but the contact form does not permit to send a mail in the case “I have a technical theme or plugin question.”.
    Other cases are more dedicated to sale of the product or client account and other…
    Should I use any of them whatever to send you the mail?

    Ben.

    • This reply was modified 1 year, 9 months ago by bendev.
    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @bendev, I see. You can email the sales team and mention my username. Looking forward to hear from you!

    Thread Starter bendev

    (@bendev)

    Ok, sorry, I looked badly first, on the html version displayed on a navigator, I didn’t see that there was an error message displayed :

    : [Error (where: parser) in | Line 297 Col 30 near '$href }}" target="_blank" class="border-radius" style="-ms-text-size-adjust: 100%;-webkit-text-size-adjust: 100%;color: #2E280E;font-family: Helvetica;font-size: 30px;line-height: 100%;text-align: center;text-decoration: none;background-color: #FFCD08;border: 1px solid #FFCD08;display: inline-block;font-weight: bold;padding-top: 20px;padding-right: 30px;padding-bottom: 20px;padding-left: 30px;-webkit-border-radius: 5px;-moz-border-radius: 5px;border-radius: 5px;">Passez à iThemes Security Pro

    Here is the image which shows the location of the error :

    Thread Starter bendev

    (@bendev)

    @shanedelierrr : mail sent from the sales team form

    • This reply was modified 1 year, 9 months ago by bendev.
Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Weekly report sent several times instead of one time’ is closed to new replies.