You Cannot Send More Than 5 Messages in 1 Hour Try Again Later Drupal 8

In our previous commodity, we installed phpList. Before we proceed with creating a mailing list that users tin subscribe to, there are some default settings that we must alter within the phpList configuration.

By default, phpList will effort to send out equally many emails every bit fast as possible. To foreclose possible problems with spam, accounts on our shared servers accept a limit set to the maximum number of emails that can be sent per hour. That limit is set to 250 per domain per hr. What this ways is that if you lot have 700 people in your mailing list and yous endeavour to send all of the emails at in one case with phpList, 250 emails will be sent and the other 450 volition neglect. To resolve this event, nosotros demand to tell phpList to only send 250 emails per hr.

Delight note that we do on a case past case basis increment this number for our users. If you're interested in being able to ship more than 250 emails per hour per domain, please encounter our Bulk Mailing Request article.

Please also keep in mind that if you normally ship ten emails per hr during your daily routine, then you may demand to set phpList to only ship 240 emails per 60 minutes. In the instance beneath, we will walk y'all through the steps to configure phpList to send 204 emails per hour at a rate of 17 emails every five minutes.

How to edit batch settings in phpList

1. Log into your cPanel
2. Access your File Managing director past clicking the "File Manager" icon.
3. Navigate to the directory you installed phplist into. Then navigate to the config directory within that. From there, right click on config.php and click edit. If yous're prompted with a "Text-Editor" window, ensure "utf-eight" is selected in the drop down and so click "Edit"
4. You lot are now looking at the phpList configuration file. There is quite a fleck of content in this file, your focus is on finding these two lines:

   ascertain("MAILQUEUE_BATCH_SIZE",0); ascertain("MAILQUEUE_BATCH_PERIOD",100); Change these values to what we accept below: ascertain("MAILQUEUE_BATCH_SIZE",17); define("MAILQUEUE_BATCH_PERIOD",300);                    

   The changes that nosotros made told phpList to send 17 emails every 300 seconds (5 minutes).

5. Click "Save Changes".

Please exist aware that y'all volition see the above lines several places in the config file. Please be certain to edit the lines that do not start with a pound sign. There is only ane line for each setting that does not begin with #.  In the example below, the green lines are where we made the edit, and the red lines are where we DID Non brand any edits due to the line starting with #.

# batch processing
# if you are on a shared host, it volition probably be appreciated if you don't transport
# out loads of emails in one go. To practice this, you can configure batch processing.
# Delight annotation, the following two values can be overridden by your ISP by using
# a server wide configuration. Then if y'all detect these values to be different
# in reality, that may exist the case

## if you transport the queue using your browser, y'all may want to consider settings like this
## which will transport 10 letters and then reload the browser to transport the adjacent ten. However, this
## will not restrict the sending to any limits, so there'south a good chance you will
## go over the limits of your ISP
# define("MAILQUEUE_BATCH_SIZE",10);
# define("MAILQUEUE_BATCH_PERIOD",1);

## if you transport the queue using commandline, you can set it to something that complies with the
## limits of your Isp, eg 300 messages an 60 minutes would be
# define("MAILQUEUE_BATCH_SIZE",300);
# define("MAILQUEUE_BATCH_PERIOD",3600);
# so you need to set the cron to run every five minutes

# define the amount of emails you want to send per period. If 0, batch processing
# is disabled and messages are sent out as fast every bit possible
ascertain("MAILQUEUE_BATCH_SIZE",17);

# define the length of 1 batch processing flow, in seconds (3600 is an hr)
# Please annotation: this setting has two consequences:
# 1. it will enforce that the amount of emails sent in the period identified hither does non exceed the corporeality
#  set up in MAILQUEUE_BATCH_SIZE
# ii. there will exist a filibuster of MAILQUEUE_BATCH_PERIOD when running the queue.
#
# number 1 is by and large when using commandline queue processing (strongly recommended)
# number two is when using browser queue processing. The browser will reload to send the adjacent
# batch subsequently the corporeality of seconds set here

define("MAILQUEUE_BATCH_PERIOD",300);

How does charge per unit limiting work in phpList?

Later in our tutorial serial, we'll show you how to send a message to a mailing list in phpList. Because we're talking about rate limiting right now, we'd like to give you a sneak height at what it will look like when you transport to 400+ users with the in a higher place options ready.

We initiall sent a bulletin to our list at 9:xx am. The confirmation bulletin below mentions that phpList sent 17 emails, and and so volition wait 300 seconds (5 minutes) before sending more.

Started
Sending in batches of 17 emails
Processing has started, 1 message(s) to process.
Please leave this window open. You accept batch processing enabled, so it will reload several times to send the messages. Reports will exist sent by electronic mail to [email protected]
Processing message 7
Looking for users
Establish them: 403 to process
batch limit reached: 17 (17)
Script phase: 5
17 messages sent in 4.38 seconds (13961 msgs/hour)
Finished this run
Waiting for 300 seconds before reloading

After 5 minutes (it is now 9:25 am), your browser will reload, and you will run across another message similar to the beneath. This bulletin states that in the last run 17 letters were sent, and some other 17 letters have been sent now:

Started
Sending in batches of 17 emails
Sent in terminal run: 17
Skipped in last run: 0
Processing has started, 1 message(s) to process.
Please leave this window open. Yous have batch processing enabled, so information technology volition reload several times to transport the messages. Reports will be sent by e-mail to [email protected]
Processing message 7
Looking for users
Found them: 386 to process
batch limit reached: 17 (17)
Script stage: 5
17 letters sent in 0.51 seconds (119386 msgs/hr)
Finished this run
Waiting for 300 seconds before reloading

At this point, you but need to leave your browser open. Every five minutes, your browser will reload and another 17 emails volition be sent.

What happens if my browser closes during sending of my messages?

We had the same question. Correct now nosotros're in the center of sending 400+ emails at a rate of 17 emails every 5 minutes. We've already sent about 51 emails, and nosotros just airtight our browser. With the browser closed, phpList volition not be able to process the rest of the messages nosotros demand sent.

To continue sending your list, merely log dorsum into yous phpList admin and click the "process queue" link in the right sidebar:

hoganfroving.blogspot.com

Source: https://www.inmotionhosting.com/support/email/rate-limit-phplist/

Bagikan Artikel ini