BuycPanel Blog

BuycPanel Blog

Latest news and updates

Preventing Spam in Failed and Deferred Outgoing Messages

Posted by Allison on 17 01 2017.

When you navigate to the “Mail” menu of your WHM account, you will find there the “Tweak Settings” interface. You can get to this interface by simply going to “Home,” then “Server Configuration,” and lastly, “Tweak Settings.”

Under the “Tweak Settings” interface, you will find five different options with various functions, but all have the same purpose: set a limit to the number of emails your server sends (outgoing email messages). When you configure any of these options, they will apply to all your server’s domains. Through the interface’s five options, you can worry less about overconsumption of bandwidth as well as would-be spammers.

One of the five choices under the “Tweak Settings” interface allows you to make changes to the failed and deferred outgoing messages.

A 101 on These Failed and Deferred Outgoing Mails

This menu contains two selections: the “Maximum percentage of failed or deferred messages a domain may send per hour”…

When you navigate to the “Mail” menu of your WHM account, you will find there the “Tweak Settings” interface. You can get to this interface by simply going to “Home,” then “Server Configuration,” and lastly, “Tweak Settings.”

Under the “Tweak Settings” interface, you will find five different options with various functions, but all have the same purpose: set a limit to the number of emails your server sends (outgoing email messages). When you configure any of these options, they will apply to all your server’s domains. Through the interface’s five options, you can worry less about overconsumption of bandwidth as well as would-be spammers.

One of the five choices under the “Tweak Settings” interface allows you to make changes to the failed and deferred outgoing messages.

A 101 on These Failed and Deferred Outgoing Mails

This menu contains two selections: the “Maximum percentage of failed or deferred messages a domain may send per hour” and the “Number of failed or deferred messages a domain may send before protections can be triggered.”

Both options allow you to dictate a time that the server will shut down temporarily and block a domain’s outgoing email messages. When any of these two are triggered, the system will verify and review all of the mails, including the local and outgoing ones, so that it can confirm whether they have met any of the following conditions:

  • The “Maximum percentage of failed or deferred messages a domain may send per hour” gives you to the choice to put a specific number in it. Once the total percentage or number of failed or deferred messages reaches or even exceeds this number, the system will temporarily cut the domain’s ability to send more messages.

 

  • The specific number that you entered in the “Number of failed or deferred messages a domain may send before protections can be triggered” option will dictate the total failed or deferred messages before the system triggers the protections.

A Quick Overview on the “Maximum percentage of failed or deferred messages a domain may send per hour”

When you make use of the “Maximum percentage of failed or deferred messages a domain may send per hour option,” you should also enable and specify something on the “Number of failed or deferred messages a domain may send before protections can be triggered option.” Your server will not block outgoing messages unless it reaches the number you have specified on these options.

Using this feature, you can specify the highest percentage you allow for failed or deferred messages your domain can send every hour. Keep in mind though, that this only applies when triggering of the “Number of failed or deferred messages a domain may send before protections can be triggered” option occurs.

 

The Basics on the “Number of failed or deferred messages a domain may send before protections can be triggered”

This option allows you to define the number of failed/deferred messages your domain can send prior to your mail server checking whether or not it has already exceeded the Maximum percentage you have specified per hour.