Additions:
A confirmation report will be sent to the email address(es) entered on the [[ConfigurePhplistInfo configuration page]] for "Who gets the reports". In addition, you can also be alerted by email when the message sending starts and ends, by entering one or more email addresses on the [[SendMessageMiscInfo "Misc" tab]] of the "Send a message" page.
Deletions:
Revision [1121]
Edited on 2007-04-29 22:28:39 by AlStillero [Added Tips & Tricks from the forum - New subscriber gets last list email automatically]Additions:
===Tips & Tricks from the forum===
[[http://mantis.phplist.com/view.php?id=7903 New subscriber gets last list email automatically]] - This mod will automatically requeue the last list message when a subscriber confirms his subscribtion.
[[http://mantis.phplist.com/view.php?id=7903 New subscriber gets last list email automatically]] - This mod will automatically requeue the last list message when a subscriber confirms his subscribtion.
Additions:
==Message sending speed and batch processing==
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the 'mail queue batch size' and 'batch period' settings in config.php, you will be able to keep the number of sent messages within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
Instead of processing the queue manually through your web browser, you can use a cron job or a commandline script. Or both. If you have more than 1000 users, it is recommended to use commandline queue processing. There are several reasons you might prefer processing the message queue with a cron job and/or commandline script, for instance: It will reduce the problem of timeouts, and -if your server is running PHP-cgi- you'll avoid having to leave the browser window open for hours.
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the 'mail queue batch size' and 'batch period' settings in config.php, you will be able to keep the number of sent messages within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
Instead of processing the queue manually through your web browser, you can use a cron job or a commandline script. Or both. If you have more than 1000 users, it is recommended to use commandline queue processing. There are several reasons you might prefer processing the message queue with a cron job and/or commandline script, for instance: It will reduce the problem of timeouts, and -if your server is running PHP-cgi- you'll avoid having to leave the browser window open for hours.
Deletions:
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the 'mail queue batch size' en 'batch period' settings in config.php, you will be able to keep the number of sent messages within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
Instead of processing the queue manually through your web browser, you can use a cron job or a commandline script. Or both. If you have more than 1000 users, it is recommended to use commandline queue processing. There are several other reasons you might prefer processing the message queue with a cron job and/or commandline script:
''enumerate briefly the reasons (long processing time due to high message load, use of batches due to mail limits set by ISP, etc.)''
Additions:
To help avoid server overloads you can configure PHPlist to slow down the rate at which it feeds messages to the mail server, by using 'mail queue throttle' setting in config.php.
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the 'mail queue batch size' en 'batch period' settings in config.php, you will be able to keep the number of sent messages within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
''enumerate briefly the reasons (long processing time due to high message load, use of batches due to mail limits set by ISP, etc.)''
An alternative to using your web browser for queue processing is a [[CommandLineScriptInfo commandline script]], which you can execute on a scheduled time by using a cron job. A [[CommandLineScriptInfo sample commandline script]] is included in the PHPlist distribution. To be able to use a command line script, the command line version of PHP (PHP-cli) must be installed on your server. Please read [[PhpInterfacesInfo the three interfaces of PHP]] for a brief discussion of differences between PHP-cli and PHP-cgi. A second (obvious) requirement is that you must have access to the command line itself (shell access). For more info, see [[CommandLineScriptInfo Using a commandline script]].
A [[SetupCronJob cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. While you can use a cron job to execute commands embedded in a commandline script, you can also place the commands directly in the crontab file. The latter method is useful when your server is running PHP-cgi instead of PHP-cli. For more info, see [[SetupCronJob Setting up a cron job]].
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the 'mail queue batch size' en 'batch period' settings in config.php, you will be able to keep the number of sent messages within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
''enumerate briefly the reasons (long processing time due to high message load, use of batches due to mail limits set by ISP, etc.)''
An alternative to using your web browser for queue processing is a [[CommandLineScriptInfo commandline script]], which you can execute on a scheduled time by using a cron job. A [[CommandLineScriptInfo sample commandline script]] is included in the PHPlist distribution. To be able to use a command line script, the command line version of PHP (PHP-cli) must be installed on your server. Please read [[PhpInterfacesInfo the three interfaces of PHP]] for a brief discussion of differences between PHP-cli and PHP-cgi. A second (obvious) requirement is that you must have access to the command line itself (shell access). For more info, see [[CommandLineScriptInfo Using a commandline script]].
A [[SetupCronJob cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. While you can use a cron job to execute commands embedded in a commandline script, you can also place the commands directly in the crontab file. The latter method is useful when your server is running PHP-cgi instead of PHP-cli. For more info, see [[SetupCronJob Setting up a cron job]].
Deletions:
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the mail queue batch size en batch period settings in config.php, you will be able to keep number of sent messages within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
- ''enumerate briefly the reasons (long processing time due to high message load, use of batches due to mail limits set by ISP, etc.)''
An alternative to using your web browser for queue processing is a commandline script, which you can execute on a scheduled time by using a cron job. A [[CommandLineScriptInfo sample commandline script]] is included in the PHPlist distribution. To be able to use a command line script, the command line version of PHP (PHP-cli) must be installed on your server. Please read [[PhpInterfacesInfo the three interfaces of PHP]] for a brief discussion of differences between PHP-cli and PHP-cgi. A second (obvious) requirement is that you must have access to the command line itself (shell access). For more info, see [[CommandLineScriptInfo Using a commandline script]].
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. While you can use a cron job to execute commands embedded in a commandline script, you can also place the commands directly in the crontab file. The latter method is useful when your server is running PHP-cgi instead of PHP-cli. For more info, see [[SetupCronJob Setting up a cron job]].
Additions:
An alternative to using your web browser for queue processing is a commandline script, which you can execute on a scheduled time by using a cron job. A [[CommandLineScriptInfo sample commandline script]] is included in the PHPlist distribution. To be able to use a command line script, the command line version of PHP (PHP-cli) must be installed on your server. Please read [[PhpInterfacesInfo the three interfaces of PHP]] for a brief discussion of differences between PHP-cli and PHP-cgi. A second (obvious) requirement is that you must have access to the command line itself (shell access). For more info, see [[CommandLineScriptInfo Using a commandline script]].
Deletions:
Additions:
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the mail queue batch size en batch period settings in config.php, you will be able to keep number of sent messages within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
Deletions:
Additions:
An alternative to using your web browser for queue processing is a commandline script, which you can execute on a scheduled time by using a cron job. A [[CommandLineScriptInfo sample commandline script]] is included in the PHPlist distribution. To be able to use a command line script, the command line version of PHP (PHP-cli) must be installed on your server. Please read [[PhpInterfacesInfo the three face of PHP]] for a brief discussion of differences between PHP-cli and PHP-cgi. A second (obvious) requirement is that you must have access to the command line itself (shell access). For more info, see [[CommandLineScriptInfo Using a commandline script]].
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. While you can use a cron job to execute commands embedded in a commandline script, you can also place the commands directly in the crontab file. The latter method is useful when your server is running PHP-cgi instead of PHP-cli. For more info, see [[SetupCronJob Setting up a cron job]].
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. While you can use a cron job to execute commands embedded in a commandline script, you can also place the commands directly in the crontab file. The latter method is useful when your server is running PHP-cgi instead of PHP-cli. For more info, see [[SetupCronJob Setting up a cron job]].
Deletions:
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. You can set up a cron job to execute a command line script, but you can also use it to process the queue without the commandline script. This makes thee latter , by entering the calls to PH. and for executing specific phplist commands, like message queue processing and bounce processing. For more info, see [[SetupCronJob Setting up a cron job]].
Additions:
When processing of the queue has started you should leave the browser window open till the result is displayed Depending on the load of messages to be processed, this can take from a few minutes up to an hour or more.
**Note**: phplist does not send any message to people who have not confirmed their subscription.
A confirmation report will be sent to the email address(es) entered on the [[ConfigurePhplistInfo configuration page]] for "Who gets the reports". You can also be alerted by email when the message sending starts and ends, by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
==Message sending speed an batch processing==
To help avoid server overloading you can configure PHPlist to slow down the rate at which it feeds messages to the mail server, by using mail queue throttle setting in config.php.
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the mail queue batch size en batch period settings in config.php, you will be able to keep message sending within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
Instead of processing the queue manually through your web browser, you can use a cron job or a commandline script. Or both. If you have more than 1000 users, it is recommended to use commandline queue processing. There are several other reasons you might prefer processing the message queue with a cron job and/or commandline script:
An alternative to using your web browser for queue processing is a commandline script, which you can execute on a scheduled time by using a cron job. A [[CommandLineScriptInfo sample commandline script]] is included in the PHPlist distribution. To be able to use a command line script, the command line version of PHP (PHP-cli) must be installed on your server. A second (obvious) requirement is that you must have access to the command line itself (shell access). For more info see: [[CommandLineScriptInfo Using a commandline script]].
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. You can set up a cron job to execute a command line script, but you can also use it to process the queue without the commandline script. This makes thee latter , by entering the calls to PH. and for executing specific phplist commands, like message queue processing and bounce processing. For more info, see [[SetupCronJob Setting up a cron job]].
**Note**: Keep in mind that whatever queue processing method you use, you still need to put the messages to be sent in the queue.
- [[PhpListConfigSendRate Setting the send speed]]
**Note**: phplist does not send any message to people who have not confirmed their subscription.
A confirmation report will be sent to the email address(es) entered on the [[ConfigurePhplistInfo configuration page]] for "Who gets the reports". You can also be alerted by email when the message sending starts and ends, by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
==Message sending speed an batch processing==
To help avoid server overloading you can configure PHPlist to slow down the rate at which it feeds messages to the mail server, by using mail queue throttle setting in config.php.
If you are on a shared hosting service, it is likely you will face limits in the number of emails you may send per hour or per day. By using the mail queue batch size en batch period settings in config.php, you will be able to keep message sending within these limits. For more info, see [[PhpListConfigSendRate Setting the send speed]].
Instead of processing the queue manually through your web browser, you can use a cron job or a commandline script. Or both. If you have more than 1000 users, it is recommended to use commandline queue processing. There are several other reasons you might prefer processing the message queue with a cron job and/or commandline script:
An alternative to using your web browser for queue processing is a commandline script, which you can execute on a scheduled time by using a cron job. A [[CommandLineScriptInfo sample commandline script]] is included in the PHPlist distribution. To be able to use a command line script, the command line version of PHP (PHP-cli) must be installed on your server. A second (obvious) requirement is that you must have access to the command line itself (shell access). For more info see: [[CommandLineScriptInfo Using a commandline script]].
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. You can set up a cron job to execute a command line script, but you can also use it to process the queue without the commandline script. This makes thee latter , by entering the calls to PH. and for executing specific phplist commands, like message queue processing and bounce processing. For more info, see [[SetupCronJob Setting up a cron job]].
**Note**: Keep in mind that whatever queue processing method you use, you still need to put the messages to be sent in the queue.
- [[PhpListConfigSendRate Setting the send speed]]
Deletions:
Note: phplist does not send any message to people who have not confirmed their subscription.
A confirmation report will be sent to the email address(es) entered on the configuration page for "Who gets the reports". You can also be alerted by email when the message sending starts and ends by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
''add remarks on batch processing and link to config file''
Instead of processing the queue manually, you can use a Cron job or a command line script. Or both. There are several reasons you might prefer processing the message queue with a cron job or command line script:
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. For more info, see [[SetupCronJob Setting up a cron job]].
''short descriptionneeds to be added'' For more info see: [[CommandLineScriptInfo Using a commandline script]].
Additions:
''short descriptionneeds to be added'' For more info see: [[CommandLineScriptInfo Using a commandline script]].
- [[CommandLineScriptInfo Using a commandline script]]
- [[CommandLineScriptInfo Using a commandline script]]
Deletions:
Revision [853]
Edited on 2006-10-19 06:06:21 by AlStillero [Several edits, some additions and preparation for references to other pages]Additions:
Clicking on 'process queue' will send all queued messages, provided they are not under embargo, i.e., scheduled to be sent later on. Once you have clicked on ##process queue##, the sending process cannot be canceled. If you do not process the message queue, messages will remain in the queue. The idea of a queue is that you can prepare messages for sending, and then have them actually sent by a scheduler or cron job.
When processing of the queue has started you should leave the browser window open till the result is displayed Depending on the load of messages to be processed, this can take from a few minutes up to more than an hour or more.
A confirmation report will be sent to the email address(es) entered on the configuration page for "Who gets the reports". You can also be alerted by email when the message sending starts and ends by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
===Alternatives to processing the queue manually===
Instead of processing the queue manually, you can use a Cron job or a command line script. Or both. There are several reasons you might prefer processing the message queue with a cron job or command line script:
- ''enumerate briefly the reasons (long processing time due to high message load, use of batches due to mail limits set by ISP, etc.)''
==Cron job==
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. For more info, see [[SetupCronJob Setting up a cron job]].
==Command line script==
''short description and a reference to "using a command line script" needs to be added''
==Related pages==
- [[MessageFunctionsInfo Message functions]]
- [[SetupCronJob Setting up a cron job]]
When processing of the queue has started you should leave the browser window open till the result is displayed Depending on the load of messages to be processed, this can take from a few minutes up to more than an hour or more.
A confirmation report will be sent to the email address(es) entered on the configuration page for "Who gets the reports". You can also be alerted by email when the message sending starts and ends by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
===Alternatives to processing the queue manually===
Instead of processing the queue manually, you can use a Cron job or a command line script. Or both. There are several reasons you might prefer processing the message queue with a cron job or command line script:
- ''enumerate briefly the reasons (long processing time due to high message load, use of batches due to mail limits set by ISP, etc.)''
==Cron job==
A [[SetupCronJob Cron job]] is a scheduler for unix/linux operating systems, that will execute commands on a predefined time. For more info, see [[SetupCronJob Setting up a cron job]].
==Command line script==
''short description and a reference to "using a command line script" needs to be added''
==Related pages==
- [[MessageFunctionsInfo Message functions]]
- [[SetupCronJob Setting up a cron job]]
Deletions:
When the processing of the queue has started you should leave the browser window open till the result is displayed (depending on the load of messages to be processed, this can last a few seconds up to more than an hour).
A confirmation report will be sent to the email address(es) entered on the configuration page for "Who gets the reports (email address, separate multiple emails with a comma)". You can also be alerted by email when the message sending starts and ends by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
*Cron job: ''please add definition, as well as example of code to add in the commandline?''
Additions:
==[[PhplistDocumentation Phplist Documentation]] » [[MessageFunctionsInfo Message functions]] » ==
Deletions:
Revision [746]
Edited on 2006-09-22 01:51:41 by AlStillero [Leave browser window op during process queue]Additions:
Clicking this link will send queued messages. If you do not click this link, a message you tried to send will remain in the "queue". The idea of the queue is that you can prepare messages for sending, and then have them actually sent by e.g. a scheduler or cron job*. Once you have clicked on ##process queue##, the send process cannot be canceled.
When the processing of the queue has started you should leave the browser window open till the result is displayed (depending on the load of messages to be processed, this can last a few seconds up to more than an hour).
A confirmation report will be sent to the email address(es) entered on the configuration page for "Who gets the reports (email address, separate multiple emails with a comma)". You can also be alerted by email when the message sending starts and ends by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
When the processing of the queue has started you should leave the browser window open till the result is displayed (depending on the load of messages to be processed, this can last a few seconds up to more than an hour).
A confirmation report will be sent to the email address(es) entered on the configuration page for "Who gets the reports (email address, separate multiple emails with a comma)". You can also be alerted by email when the message sending starts and ends by entering one or more email addresses on the "Misc" tab of the "Send a message" page.
Deletions:
When the processing of the queue has started you can close the browser window or just wait till the result is displayed (depending on the load of messages to be processed, this can last a few seconds up to several tens of minutes).
A confirmation email will be sent to ''whom?''
Revision [646]
Edited on 2006-07-17 18:25:31 by HernoLAdditions:
[[PhplistDocumentation phplist Documentation]]
Note: phplist does not send any message to people who have not confirmed their subscription.
Note: phplist does not send any message to people who have not confirmed their subscription.
Deletions:
Note: PHPlist does not send any message to people who have not confirmed their subscription.
Additions:
Clicking this link will send queued messages. If you do not click this link, a message you tried to send will remain in the "queue". The idea of the queue is that you can prepare messages for sending, and then have them actually sent by e.g. a scheduler or cron job*. Clicking the link is undoable: you cannot stop the send process once you click on ##process queue##.
''add remarks on batch processing and link to config file''
A confirmation email will be sent to ''whom?''
Note: PHPlist does not send any message to people who have not confirmed their subscription.
*Cron job: ''please add definition, as well as example of code to add in the commandline?''
''add remarks on batch processing and link to config file''
A confirmation email will be sent to ''whom?''
Note: PHPlist does not send any message to people who have not confirmed their subscription.
*Cron job: ''please add definition, as well as example of code to add in the commandline?''
Deletions:
Note: PHPlist does not send any message to people who have not confirmed their subscription
Note: the administrator can configue PHPlist in order to have this automated, and that all messages are "processed" immediately
~& to YanB : I 'm not really sure about this... how and where can the administrator do this?
---
(en français:)
Ce lien vous permet d'envoyer effectivement votre message. Si vous ne cliquez pas sur Process queue , votre message ne sera jamais réellement envoyé.
Attention: Lorsque vous cliquez sur Process queue , vous lancez la procédure d'envoi effectif de tous les messages en attente. Vous ne pouvez pas revenir en arrière.
Lorsque le processus est enclenché, vous pouvez:
1/ quitter PHPlist,
2/ attendre plusieurs minutes le résultat de votre envoi (ça peut aller de 1 mn à 30 mn, selon la complexité de l'envoi).
Note: PHPlist n'envoie aucun message aux personnes qui n'ont pas confirmé leur inscription sur la base de données.
Note: l'administrateur peut configurer PHPlist pour que cette étape se fasse automatiquement, et que tous les Messages envoyés soient directement 'processed'.
Revision [176]
Edited on 2005-04-12 09:41:26 by PascalVanHeckeDeletions:
Revision [171]
Edited on 2005-04-11 21:40:46 by PascalVanHeckeAdditions:
(en français:)
Revision [170]
Edited on 2005-04-11 21:40:24 by PascalVanHeckeAdditions:
Clicking this link will send queued messages. If you do not click this link, a message you tried to send will remain in the "queue". The idea of the queue is that you can prepare messages for sending, and then have them actually sent by e.g. a scheduler or cron job. Clicking the link is undoable: yo cannot stop the send process then.
When the processing of the queue has started you can close the browser window or just wait till the result is displayed (depending on the load of messages to be processed, this can last a few seconds up to several tens of minutes).
Note: PHPlist does not send any message to people who have not confirmed their subscription
Note: the administrator can configue PHPlist in order to have this automated, and that all messages are "processed" immediately
~& to YanB : I 'm not really sure about this... how and where can the administrator do this?
If you are a technically inclined person, you might want read ProcessQueueWorkFlowDescription to learn what actually happens when sending emails.
---
When the processing of the queue has started you can close the browser window or just wait till the result is displayed (depending on the load of messages to be processed, this can last a few seconds up to several tens of minutes).
Note: PHPlist does not send any message to people who have not confirmed their subscription
Note: the administrator can configue PHPlist in order to have this automated, and that all messages are "processed" immediately
~& to YanB : I 'm not really sure about this... how and where can the administrator do this?
If you are a technically inclined person, you might want read ProcessQueueWorkFlowDescription to learn what actually happens when sending emails.
---
Additions:
=====Process the Message Queue=====
Ce lien vous permet d'envoyer effectivement votre message. Si vous ne cliquez pas sur Process queue , votre message ne sera jamais réellement envoyé.
Attention: Lorsque vous cliquez sur Process queue , vous lancez la procédure d'envoi effectif de tous les messages en attente. Vous ne pouvez pas revenir en arrière.
Lorsque le processus est enclenché, vous pouvez:
1/ quitter PHPlist,
2/ attendre plusieurs minutes le résultat de votre envoi (ça peut aller de 1 mn à 30 mn, selon la complexité de l'envoi).
Note: PHPlist n'envoie aucun message aux personnes qui n'ont pas confirmé leur inscription sur la base de données.
Note: l'administrateur peut configurer PHPlist pour que cette étape se fasse automatiquement, et que tous les Messages envoyés soient directement 'processed'.
Ce lien vous permet d'envoyer effectivement votre message. Si vous ne cliquez pas sur Process queue , votre message ne sera jamais réellement envoyé.
Attention: Lorsque vous cliquez sur Process queue , vous lancez la procédure d'envoi effectif de tous les messages en attente. Vous ne pouvez pas revenir en arrière.
Lorsque le processus est enclenché, vous pouvez:
1/ quitter PHPlist,
2/ attendre plusieurs minutes le résultat de votre envoi (ça peut aller de 1 mn à 30 mn, selon la complexité de l'envoi).
Note: PHPlist n'envoie aucun message aux personnes qui n'ont pas confirmé leur inscription sur la base de données.
Note: l'administrateur peut configurer PHPlist pour que cette étape se fasse automatiquement, et que tous les Messages envoyés soient directement 'processed'.
Deletions:
//This page is a **template** intended for documentation of **official phplist features**. This page belongs to CategoryTemplate (which contains more handy templates). To create a phplist **documentation** page, [[http://docs.phplist.com/DocumentationTemplate/clone clone this page]], replace the title with a meaningful one and replace this paragraph with the actual page content.//
