Revision [1589]
Last edited on 2008-06-11 15:11:08 by JulianSAdditions:
For this reason most hosting providers will limit the number of emails a single site may send. Either limiting the number of emails per hour or per day. This is their job, to make sure that one person's use doesn't impacts needlessly the other sites on that machine.
Deletions:
Revision [1588]
Edited on 2008-06-11 15:02:35 by JulianSAdditions:
For this reason most hosting providers will limit the number of emails a single site may send. Either limiting the number of emails per hour or per day. This is their job, to make sure no 'user's use' needlessly impacts the other sites on that machine.
Deletions:
Revision [1567]
Edited on 2008-05-14 14:00:31 by JulianSAdditions:
At full speed phplist (up to version 2.10.5) will send about 3000 personalized messages per hour, or about 5000 non-personalized messages per hour. Given that most shared hosting providers will not allow that message volume to be sent and will impose an hourly or daily limit, Phplist offers two methods to deal with these message limits: //mailqueue batch// processing and //mailqueue throttle// processing. The choice in using batches or throttling is basically a personal preference, although throttling may be better suited for servers running PHP-cgi (see [[PhpInterfacesInfo The three interfaces of PHP]]).
Deletions:
Revision [1549]
Edited on 2008-05-03 22:35:12 by JulianSAdditions:
Another, perhaps, better reason providers will limit your email resources is that they don't want to host spammers. So, what does this mean to you, a non-spammer? **You must check with your hosting provider before sending your first mailing.** Ask: Is there a daily limit? Is there an hourly limit? Odds are that there is. Then use the following settings in the config.php file to safely live within these limits.
Deletions:
Additions:
At full speed phplist (up to version 2.10.5) will send about 3000 personalized messages per hour, or about 5000 non-personalized messages per hour. Given that most shared hosting providers will not allow that message volume to be sent and will impose an hourly or daily limit, Phplist offers two methods to deal with these message limits: //mailqueue batch// processing and //mailqueue throttle// processing. The choice in using batches or throttling is basically a personal preference, although throttling may be better suited for servers running PHP-cgi (see [[PhpInterfacesInfo The three interfaces op PHP]]).
With batch processing, two primary settings work together to say: Send no more than N emails every T seconds. Where:
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new sign-ups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-40 down from your hourly limit.
If your server is running PHP-cgi, you may have issues with timeouts (see [[PhpInterfacesInfo The three interfaces op PHP]]). In that case you could try a shorter batch period of for instance 10 minutes.
# Send a batch of 60 messages per batch period:
define("MAILQUEUE_BATCH_SIZE",60);
# batch period is set to 600 seconds (= 10 minutes):
define("MAILQUEUE_BATCH_PERIOD",600);
With batch processing, two primary settings work together to say: Send no more than N emails every T seconds. Where:
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new sign-ups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-40 down from your hourly limit.
If your server is running PHP-cgi, you may have issues with timeouts (see [[PhpInterfacesInfo The three interfaces op PHP]]). In that case you could try a shorter batch period of for instance 10 minutes.
# Send a batch of 60 messages per batch period:
define("MAILQUEUE_BATCH_SIZE",60);
# batch period is set to 600 seconds (= 10 minutes):
define("MAILQUEUE_BATCH_PERIOD",600);
Deletions:
With batch processing, two primary settings work together to say: Send no more than N emails every T minutes. Where:
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new signups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-40 down from your hourly limit.
If your server is running PHP-cgi, you may have issues with timeouts (see [[PhpInterfacesInfo The three interfaces op PHP]]). In that case you could try a shorter batch period of for instance 15 minutes.
# Send a batch of 90 messages per batch period:
define("MAILQUEUE_BATCH_SIZE",90);
# batch period is set to 900 seconds (= 15 minutes):
define("MAILQUEUE_BATCH_PERIOD",900);
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
Additions:
===Tips & tricks from the forum===
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
- [[ProcessQueueInfo Process the message queue]]
- [[SetupCronJob Setting up a cron job]]
- [[CommandLineScriptInfo Using a commandline script]]
CategoryDocumentation
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
- [[ProcessQueueInfo Process the message queue]]
- [[SetupCronJob Setting up a cron job]]
- [[CommandLineScriptInfo Using a commandline script]]
CategoryDocumentation
Deletions:
Revision [1251]
Edited on 2007-06-30 06:41:48 by TigH9b (unregistered user)Additions:
===Tips
Deletions:
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
- [[ProcessQueueInfo Process the message queue]]
- [[SetupCronJob Setting up a cron job]]
- [[CommandLineScriptInfo Using a commandline script]]
CategoryDocumentation
Additions:
At full speed phplist (up to version 2.10.4) will send about 3000 personalized messages per hour, or about 5000 non-personalized messages per hour. Given that most shared hosting providers will not allow that message volume to be sent and will impose an hourly or daily limit, Phplist offers two methods to deal with these message limits: mailqueue batch processing and mailqueue throttle processing. The choice in using batches or throttling is basically a personal preference, although throttling may be better suited for servers running PHP-cgi (see [[PhpInterfacesInfo The three interfaces op PHP]]).
If your server is running PHP-cgi, you may have issues with timeouts (see [[PhpInterfacesInfo The three interfaces op PHP]]). In that case you could try a shorter batch period of for instance 15 minutes.
The ##MAILQUEUE_THROTTLE## setting inserts a pause (in seconds) between each message, i.e. it will space messages apart by a number of seconds. While you can use this setting to avoid overloading the server with a sudden burst of messages, you can also use it as an alternative to batch processing. For instance, if you impose a pause of 10 seconds between messages, you will in fact send no more than 360 messages per hour.
If your server is running PHP-cgi, you may have issues with timeouts (see [[PhpInterfacesInfo The three interfaces op PHP]]). In that case you could try a shorter batch period of for instance 15 minutes.
The ##MAILQUEUE_THROTTLE## setting inserts a pause (in seconds) between each message, i.e. it will space messages apart by a number of seconds. While you can use this setting to avoid overloading the server with a sudden burst of messages, you can also use it as an alternative to batch processing. For instance, if you impose a pause of 10 seconds between messages, you will in fact send no more than 360 messages per hour.
Deletions:
If your server is running PHP-cgi, you may have issues with timeouts. In that case you could try a shorter batch period of for instance 15 minutes.
The ##MAILQUEUE_THROTTLE## setting inserts a pause (in seconds) between each message, i.e. it will space messages apart by a number of seconds. While you can use this setting to avoid overloading the server with a sudden burst of messages, you can also use it as an alternative to batch processing. For instance, if you impose a pause of 10 seconds between messages, you will send no more than 360 messages per hour.
define("MAILQUEUE_BATCH_SIZE", 0);
Revision [1126]
Edited on 2007-05-05 18:08:35 by AlStillero [Added explanation and examples of mailqueue settings - first draft]Additions:
Another, perhaps better reason providers will limit your email resources is that they don't want to host spammers. So, what does this mean to you, a non-spammer? **You must check with your hosting provider before sending your first mailing.** Ask: Is there a daily limit? Is there an hourly limit? Odds are that there is. Then use the following settings in the config.php file to safely live within these limits.
===Limiting the speed rate===
At full speed phplist (up to version 2.10.4) will send about 3000 personalized messages per hour, or about 5000 non-personalized messages per hour. Given that most shared hosting providers will not allow that message volume to be sent and will impose an hourly or daily limit, Phplist offers two methods to deal with these message limits: mailqueue batch processing and mailqueue throttle processing. The choice in using batches or throttling is a personal preference.
==Mailqueue batch processing==
With batch processing, two primary settings work together to say: Send no more than N emails every T minutes. Where:
These settings force phplist to "restrain itself" and avoid sending out all messages in one go.
So, say you have an hourly limit of 400 emails. Should you set the batch size to 400? No! Why?
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new signups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-40 down from your hourly limit.
Example:
# Send a batch of 360 messages per batch period:
define("MAILQUEUE_BATCH_SIZE",360);
# batch period is set to 3600 seconds (=1 hour):
# Pause between messages (in seconds) to avoid overloading the server:
define('MAILQUEUE_THROTTLE',1);
If your server is running PHP-cgi, you may have issues with timeouts. In that case you could try a shorter batch period of for instance 15 minutes.
Example:
# Send a batch of 90 messages per batch period:
define("MAILQUEUE_BATCH_SIZE",90);
# batch period is set to 900 seconds (= 15 minutes):
define("MAILQUEUE_BATCH_PERIOD",900);
# Pause between messages (in seconds) to avoid overloading the server:
define('MAILQUEUE_THROTTLE',1);
==Mailqueue throttle==
The ##MAILQUEUE_THROTTLE## setting inserts a pause (in seconds) between each message, i.e. it will space messages apart by a number of seconds. While you can use this setting to avoid overloading the server with a sudden burst of messages, you can also use it as an alternative to batch processing. For instance, if you impose a pause of 10 seconds between messages, you will send no more than 360 messages per hour.
Example:
# batch processing disabled:
define("MAILQUEUE_BATCH_SIZE", 0);
# Batch_period is not effective when batch processing is disabled:
# Pause between messages (in seconds) to send no more than 360 messages per hour:
define('MAILQUEUE_THROTTLE',10);
===Experimental settings: auto throttle and domain throttle===
===Limiting the speed rate===
At full speed phplist (up to version 2.10.4) will send about 3000 personalized messages per hour, or about 5000 non-personalized messages per hour. Given that most shared hosting providers will not allow that message volume to be sent and will impose an hourly or daily limit, Phplist offers two methods to deal with these message limits: mailqueue batch processing and mailqueue throttle processing. The choice in using batches or throttling is a personal preference.
==Mailqueue batch processing==
With batch processing, two primary settings work together to say: Send no more than N emails every T minutes. Where:
These settings force phplist to "restrain itself" and avoid sending out all messages in one go.
So, say you have an hourly limit of 400 emails. Should you set the batch size to 400? No! Why?
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new signups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-40 down from your hourly limit.
Example:
# Send a batch of 360 messages per batch period:
define("MAILQUEUE_BATCH_SIZE",360);
# batch period is set to 3600 seconds (=1 hour):
# Pause between messages (in seconds) to avoid overloading the server:
define('MAILQUEUE_THROTTLE',1);
If your server is running PHP-cgi, you may have issues with timeouts. In that case you could try a shorter batch period of for instance 15 minutes.
Example:
# Send a batch of 90 messages per batch period:
define("MAILQUEUE_BATCH_SIZE",90);
# batch period is set to 900 seconds (= 15 minutes):
define("MAILQUEUE_BATCH_PERIOD",900);
# Pause between messages (in seconds) to avoid overloading the server:
define('MAILQUEUE_THROTTLE',1);
==Mailqueue throttle==
The ##MAILQUEUE_THROTTLE## setting inserts a pause (in seconds) between each message, i.e. it will space messages apart by a number of seconds. While you can use this setting to avoid overloading the server with a sudden burst of messages, you can also use it as an alternative to batch processing. For instance, if you impose a pause of 10 seconds between messages, you will send no more than 360 messages per hour.
Example:
# batch processing disabled:
define("MAILQUEUE_BATCH_SIZE", 0);
# Batch_period is not effective when batch processing is disabled:
# Pause between messages (in seconds) to send no more than 360 messages per hour:
define('MAILQUEUE_THROTTLE',10);
===Experimental settings: auto throttle and domain throttle===
Deletions:
**YOU MUST CHECK WITH YOUR HOST SERVICE BEFORE SENDING YOUR FIRST MAILING**
Ask, is a daily limit? Is there an hourly limit? Odds are that there are some. Then use this block of the config.php file to safely live within these limits.
Two primary settings work together to say: Send no more than N emails every T minutes.
Where:
These settings force phpList to "pace itself".
The last setting, ##MAILQUEUE_THROTTLE##, will space messages apart by some number of seconds.
So, say you have an hourly limit of 400 emails. Should you set the batch size to 400? No!
Why?
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new signups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-30 down from your hourly limit.
Revision [1103]
Edited on 2007-04-21 14:22:13 by SaWeyAdditions:
==[[PhplistDocumentation phplist Documentation]] » [[PhpListConfiguration Configuring]] »==
----
=====Setting the Send Speed (Rate)=====
Many people are running phpList on hosted servers they do not own or manage. These are usually shared boxes: that is, one computer has lots of web sites on it. This means that if one web site attempts to dominate the CPU or otherwise behave in a non-community-minded, limited resource way, everyone suffers.
For this reason most hosting providers will limit the number of emails a single site may send. Either limiting the number of emails per hour or per day. This is their job, to make sure no one user needlessly impacts the other sites on that machine.
Another, perhaps better reason providers will limit your email resources is that they don't want to host spammers. So, what does this mean to you, a non-spammer?
**YOU MUST CHECK WITH YOUR HOST SERVICE BEFORE SENDING YOUR FIRST MAILING**
Ask, is a daily limit? Is there an hourly limit? Odds are that there are some. Then use this block of the config.php file to safely live within these limits.
Two primary settings work together to say: Send no more than N emails every T minutes.
Where:
N is ##MAILQUEUE_BATCH_SIZE##
T is ##MAILQUEUE_BATCH_PERIOD##
These settings force phpList to "pace itself".
The last setting, ##MAILQUEUE_THROTTLE##, will space messages apart by some number of seconds.
So, say you have an hourly limit of 400 emails. Should you set the batch size to 400? No!
Why?
What about other emails, such as confirmation requests, system messages, or emails sent by other applications you might have running on this site?
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new signups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-30 down from your hourly limit.
== this block in config.php ==
%%(php)
# batch processing
# if you are on a shared host, it will probably be appreciated if you don't send
# out loads of emails in one go. To do this, you can configure batch processing.
# Please note, the following two values can be overridden by your ISP by using
# a server wide configuration. So if you notice these values to be different
# in reality, that may be the case
# define the amount of emails you want to send per period. If 0, batch processing
# is disabled and messages are sent out as fast as possible
define("MAILQUEUE_BATCH_SIZE",0);
# define the length of one batch processing period, in seconds (3600 is an hour)
define("MAILQUEUE_BATCH_PERIOD",3600);
# to avoid overloading the server that sends your email, you can add a little delay
# between messages that will spread the load of sending
# you will need to find a good value for your own server
# value is in seconds (or you can play with the autothrottle below)
define('MAILQUEUE_THROTTLE',0);%%
%%(php)
# Mailqueue autothrottle. This will try to automatically change the delay
# between messages to make sure that the MAILQUEUE_BATCH_SIZE (above) is spread evently over
# MAILQUEUE_BATCH_PERIOD, instead of firing the Batch in the first few minutes of the period
# and then waiting for the next period. This only works with mailqueue_throttle off
# it still needs tweaking, so send your feedback to mantis.tincan.co.uk if you find
# any issues with it
define('MAILQUEUE_AUTOTHROTTLE',0);
# Domain Throttling
# You can activate domain throttling, by setting USE_DOMAIN_THROTTLE to 1
# define the maximum amount of emails you want to allow sending to any domain and the number
# of seconds for that amount. This will make sure you don't send too many emails to one domain
# which may cause blacklisting. Particularly the big ones are tricky about this.
# it may cause a dramatic increase in the amount of time to send a message, depending on how
# many users you have that have the same domain (eg hotmail.com)
# if too many failures for throttling occur, the send process will automatically add an extra
# delay to try to improve that. The example sends 1 message every 2 minutes.
define('USE_DOMAIN_THROTTLE',0);
define('DOMAIN_BATCH_SIZE',1);
define('DOMAIN_BATCH_PERIOD',120);
%%
===Tips & tricks from the forum===
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
- [[ProcessQueueInfo Process the message queue]]
- [[SetupCronJob Setting up a cron job]]
- [[CommandLineScriptInfo Using a commandline script]]
----
CategoryDocumentation
----
=====Setting the Send Speed (Rate)=====
Many people are running phpList on hosted servers they do not own or manage. These are usually shared boxes: that is, one computer has lots of web sites on it. This means that if one web site attempts to dominate the CPU or otherwise behave in a non-community-minded, limited resource way, everyone suffers.
For this reason most hosting providers will limit the number of emails a single site may send. Either limiting the number of emails per hour or per day. This is their job, to make sure no one user needlessly impacts the other sites on that machine.
Another, perhaps better reason providers will limit your email resources is that they don't want to host spammers. So, what does this mean to you, a non-spammer?
**YOU MUST CHECK WITH YOUR HOST SERVICE BEFORE SENDING YOUR FIRST MAILING**
Ask, is a daily limit? Is there an hourly limit? Odds are that there are some. Then use this block of the config.php file to safely live within these limits.
Two primary settings work together to say: Send no more than N emails every T minutes.
Where:
N is ##MAILQUEUE_BATCH_SIZE##
T is ##MAILQUEUE_BATCH_PERIOD##
These settings force phpList to "pace itself".
The last setting, ##MAILQUEUE_THROTTLE##, will space messages apart by some number of seconds.
So, say you have an hourly limit of 400 emails. Should you set the batch size to 400? No!
Why?
What about other emails, such as confirmation requests, system messages, or emails sent by other applications you might have running on this site?
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new signups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-30 down from your hourly limit.
== this block in config.php ==
%%(php)
# batch processing
# if you are on a shared host, it will probably be appreciated if you don't send
# out loads of emails in one go. To do this, you can configure batch processing.
# Please note, the following two values can be overridden by your ISP by using
# a server wide configuration. So if you notice these values to be different
# in reality, that may be the case
# define the amount of emails you want to send per period. If 0, batch processing
# is disabled and messages are sent out as fast as possible
define("MAILQUEUE_BATCH_SIZE",0);
# define the length of one batch processing period, in seconds (3600 is an hour)
define("MAILQUEUE_BATCH_PERIOD",3600);
# to avoid overloading the server that sends your email, you can add a little delay
# between messages that will spread the load of sending
# you will need to find a good value for your own server
# value is in seconds (or you can play with the autothrottle below)
define('MAILQUEUE_THROTTLE',0);%%
%%(php)
# Mailqueue autothrottle. This will try to automatically change the delay
# between messages to make sure that the MAILQUEUE_BATCH_SIZE (above) is spread evently over
# MAILQUEUE_BATCH_PERIOD, instead of firing the Batch in the first few minutes of the period
# and then waiting for the next period. This only works with mailqueue_throttle off
# it still needs tweaking, so send your feedback to mantis.tincan.co.uk if you find
# any issues with it
define('MAILQUEUE_AUTOTHROTTLE',0);
# Domain Throttling
# You can activate domain throttling, by setting USE_DOMAIN_THROTTLE to 1
# define the maximum amount of emails you want to allow sending to any domain and the number
# of seconds for that amount. This will make sure you don't send too many emails to one domain
# which may cause blacklisting. Particularly the big ones are tricky about this.
# it may cause a dramatic increase in the amount of time to send a message, depending on how
# many users you have that have the same domain (eg hotmail.com)
# if too many failures for throttling occur, the send process will automatically add an extra
# delay to try to improve that. The example sends 1 message every 2 minutes.
define('USE_DOMAIN_THROTTLE',0);
define('DOMAIN_BATCH_SIZE',1);
define('DOMAIN_BATCH_PERIOD',120);
%%
===Tips & tricks from the forum===
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
- [[ProcessQueueInfo Process the message queue]]
- [[SetupCronJob Setting up a cron job]]
- [[CommandLineScriptInfo Using a commandline script]]
----
CategoryDocumentation
Deletions:
Revision [1098]
Edited on 2007-04-20 06:33:13 by OslZ0m (unregistered user)Additions:
==[[PhplistDocumentation phplist Documentation]]
Deletions:
----
=====Setting the Send Speed (Rate)=====
Many people are running phpList on hosted servers they do not own or manage. These are usually shared boxes: that is, one computer has lots of web sites on it. This means that if one web site attempts to dominate the CPU or otherwise behave in a non-community-minded, limited resource way, everyone suffers.
For this reason most hosting providers will limit the number of emails a single site may send. Either limiting the number of emails per hour or per day. This is their job, to make sure no one user needlessly impacts the other sites on that machine.
Another, perhaps better reason providers will limit your email resources is that they don't want to host spammers. So, what does this mean to you, a non-spammer?
**YOU MUST CHECK WITH YOUR HOST SERVICE BEFORE SENDING YOUR FIRST MAILING**
Ask, is a daily limit? Is there an hourly limit? Odds are that there are some. Then use this block of the config.php file to safely live within these limits.
Two primary settings work together to say: Send no more than N emails every T minutes.
Where:
N is ##MAILQUEUE_BATCH_SIZE##
T is ##MAILQUEUE_BATCH_PERIOD##
These settings force phpList to "pace itself".
The last setting, ##MAILQUEUE_THROTTLE##, will space messages apart by some number of seconds.
So, say you have an hourly limit of 400 emails. Should you set the batch size to 400? No!
Why?
What about other emails, such as confirmation requests, system messages, or emails sent by other applications you might have running on this site?
No, you want to back away from that "400", which is a best case scenario. Instead give yourself some safe breathing room. For example, if you get 24 new signups a day then you should subtract 5 or so to be safe, thus 395. Running other software that sends notifications? back it down. A comfortable number for a small installation would be 20-30 down from your hourly limit.
== this block in config.php ==
%%(php)
# batch processing
# if you are on a shared host, it will probably be appreciated if you don't send
# out loads of emails in one go. To do this, you can configure batch processing.
# Please note, the following two values can be overridden by your ISP by using
# a server wide configuration. So if you notice these values to be different
# in reality, that may be the case
# define the amount of emails you want to send per period. If 0, batch processing
# is disabled and messages are sent out as fast as possible
define("MAILQUEUE_BATCH_SIZE",0);
# define the length of one batch processing period, in seconds (3600 is an hour)
define("MAILQUEUE_BATCH_PERIOD",3600);
# to avoid overloading the server that sends your email, you can add a little delay
# between messages that will spread the load of sending
# you will need to find a good value for your own server
# value is in seconds (or you can play with the autothrottle below)
define('MAILQUEUE_THROTTLE',0);%%
%%(php)
# Mailqueue autothrottle. This will try to automatically change the delay
# between messages to make sure that the MAILQUEUE_BATCH_SIZE (above) is spread evently over
# MAILQUEUE_BATCH_PERIOD, instead of firing the Batch in the first few minutes of the period
# and then waiting for the next period. This only works with mailqueue_throttle off
# it still needs tweaking, so send your feedback to mantis.tincan.co.uk if you find
# any issues with it
define('MAILQUEUE_AUTOTHROTTLE',0);
# Domain Throttling
# You can activate domain throttling, by setting USE_DOMAIN_THROTTLE to 1
# define the maximum amount of emails you want to allow sending to any domain and the number
# of seconds for that amount. This will make sure you don't send too many emails to one domain
# which may cause blacklisting. Particularly the big ones are tricky about this.
# it may cause a dramatic increase in the amount of time to send a message, depending on how
# many users you have that have the same domain (eg hotmail.com)
# if too many failures for throttling occur, the send process will automatically add an extra
# delay to try to improve that. The example sends 1 message every 2 minutes.
define('USE_DOMAIN_THROTTLE',0);
define('DOMAIN_BATCH_SIZE',1);
define('DOMAIN_BATCH_PERIOD',120);
%%
===Tips & tricks from the forum===
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
- [[ProcessQueueInfo Process the message queue]]
- [[SetupCronJob Setting up a cron job]]
- [[CommandLineScriptInfo Using a commandline script]]
----
CategoryDocumentation
Revision [925]
Edited on 2006-10-27 01:43:21 by AlStillero [Added links to tips & tricks from the forum]Additions:
===Tips & tricks from the forum===
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
- [[http://forums.phplist.com/viewtopic.php?p=17494#17494 Need more granularity for throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11182#11182 Fractional values in throttle setting]]
- [[http://forums.phplist.com/viewtopic.php?p=11369#11369 Throttled Sending Instead of Batches]]
==Related pages==
Deletions:
Additions:
- [[ProcessQueueInfo Process the message queue]]
- [[CommandLineScriptInfo Using a commandline script]]
- [[CommandLineScriptInfo Using a commandline script]]
Additions:
Many people are running phpList on hosted servers they do not own or manage. These are usually shared boxes: that is, one computer has lots of web sites on it. This means that if one web site attempts to dominate the CPU or otherwise behave in a non-community-minded, limited resource way, everyone suffers.
Deletions:
Additions:
==[[PhplistDocumentation phplist Documentation]] » [[PhpListConfiguration Configuring]] »==
=====Setting the Send Speed (Rate)=====
=====Setting the Send Speed (Rate)=====
Deletions:
==Installation » [[PhpListConfiguration Configuring]] »==
====Setting the Send Speed (Rate)====
Employing absolutely no hyperbole these are the most important settings you'll ever use IN YOUR LIFE!!
OK, got you attention? Good. Read on:
Additions:
# Mailqueue autothrottle. This will try to automatically change the delay
# between messages to make sure that the MAILQUEUE_BATCH_SIZE (above) is spread evently over
# MAILQUEUE_BATCH_PERIOD, instead of firing the Batch in the first few minutes of the period
# and then waiting for the next period. This only works with mailqueue_throttle off
# it still needs tweaking, so send your feedback to mantis.tincan.co.uk if you find
# any issues with it
define('MAILQUEUE_AUTOTHROTTLE',0);
# Domain Throttling
# You can activate domain throttling, by setting USE_DOMAIN_THROTTLE to 1
# define the maximum amount of emails you want to allow sending to any domain and the number
# of seconds for that amount. This will make sure you don't send too many emails to one domain
# which may cause blacklisting. Particularly the big ones are tricky about this.
# it may cause a dramatic increase in the amount of time to send a message, depending on how
# many users you have that have the same domain (eg hotmail.com)
# if too many failures for throttling occur, the send process will automatically add an extra
# delay to try to improve that. The example sends 1 message every 2 minutes.
define('USE_DOMAIN_THROTTLE',0);
define('DOMAIN_BATCH_SIZE',1);
define('DOMAIN_BATCH_PERIOD',120);
%%
Related pages
- [[SetupCronJob Setting up a cron job]]
# between messages to make sure that the MAILQUEUE_BATCH_SIZE (above) is spread evently over
# MAILQUEUE_BATCH_PERIOD, instead of firing the Batch in the first few minutes of the period
# and then waiting for the next period. This only works with mailqueue_throttle off
# it still needs tweaking, so send your feedback to mantis.tincan.co.uk if you find
# any issues with it
define('MAILQUEUE_AUTOTHROTTLE',0);
# Domain Throttling
# You can activate domain throttling, by setting USE_DOMAIN_THROTTLE to 1
# define the maximum amount of emails you want to allow sending to any domain and the number
# of seconds for that amount. This will make sure you don't send too many emails to one domain
# which may cause blacklisting. Particularly the big ones are tricky about this.
# it may cause a dramatic increase in the amount of time to send a message, depending on how
# many users you have that have the same domain (eg hotmail.com)
# if too many failures for throttling occur, the send process will automatically add an extra
# delay to try to improve that. The example sends 1 message every 2 minutes.
define('USE_DOMAIN_THROTTLE',0);
define('DOMAIN_BATCH_SIZE',1);
define('DOMAIN_BATCH_PERIOD',120);
%%
Related pages
- [[SetupCronJob Setting up a cron job]]
Revision [601]
Edited on 2006-07-17 16:03:48 by HernoLAdditions:
[[PhplistDocumentation phplist Documentation]]
Deletions:
Additions:
N is ##MAILQUEUE_BATCH_SIZE##
T is ##MAILQUEUE_BATCH_PERIOD##
The last setting, ##MAILQUEUE_THROTTLE##, will space messages apart by some number of seconds.
CategoryDocumentation
T is ##MAILQUEUE_BATCH_PERIOD##
The last setting, ##MAILQUEUE_THROTTLE##, will space messages apart by some number of seconds.
CategoryDocumentation
Deletions:
T is MAILQUEUE_BATCH_PERIOD
The last setting, MAILQUEUE_THROTTLE, will space messages apart by some number of seconds.
Revision [472]
Edited on 2006-02-06 04:51:19 by BuzCarterAdditions:
==Installation » [[PhpListConfiguration Configuring]] »==
