BTK Apprendre et faire apprendre

  I have confirmed access to the provided server, and I am familiarizing myself with your ticket request. While this ticket is being reviewed, we ask that you do not work on your server except in emergency situations, so as to not cause any conflicts. Please make sure to check your email in case we require access to any information that may assist us in resolving your issue. After a quick review, I noticed that the SPF record is set to soft fail ~all This will need to be adjusted as it appears the majority of the spam is due to people pretending to send on behalf of XXXXX.DZ  and using different servers to do so. With a soft fail, this prevents most servers from denying the mail outright due to a lack of "permission checking" and the mail you are receiving is a result of the "bounces" because the server is not confirming or denying that it is permitted to send. For more information about SPF records, please refer to the link below. SPF records: Hard Fa

 

  The problem isn't necessarily with one site on the server, or with any certain user accessing the site too many times, but a total of the number of connections available to Apache. One of my favorite ways to monitor Apache usage is with the "apachectl status" or "apachectl fullstatus" command, depending on how much information you'd like to receive about the current connections.  Once you take a look at that data we have an article about using that information to determine more about the Apache resources here: Understanding the Apache scoreboard We also have an article about doing some additional troubleshooting with the Max Request Workers area here: How do I troubleshoot Apache Max Request Workers errors? so between those two pages that should give you a good start and tracking down the usage.  It's best to try and do this as soon as possible as you notice the problem on the machine for the best results.

That API command can be used on the command line.  Here's one example: uapi --user=username Email passwd_pop email=user@example.com password=12345678 domain=example.com You'll just need to update the username, email address, password, and domain fields in order to make that work.