larger smaller normal text version of this page

Revision [922]

Last edited on 2006-10-26 14:52:12 by AlStillero [minor edits]
Additions:
Each time you send out a message to a substantial number of users, you should use 'Process Bounces' to check for bounced messages. If you don't see any bounces right away, check again in a few days, as bounced messages may take a while to arrive.
If you do have bounces, do not remove them till a few days later. Otherwise the system will not be able to identify the __consecutive bounces__ (bounces in a row) for a given user's email address.
You can also create rules for bounces. To learn more about this, please see [[AdvancedBounceHandlingInfo Advanced Bounce Handling]].
If you have many bounces you can run a scheduler -like a cron job- to process bounces, instead of having to do this manually. In that case you should disable manual processing of bounces in the config.php file:
- [[SetupCronJob Setting up a cron job]]
Deletions:
Each time you send out a message to a substantial number of users, you should go to 'Process Bounces' to check for bounced messages. If you don't see any bounces right away, check again in a few days, as they may take a while to arrive.
If you do have bounces, do not remove them till a few days later, otherwise the system will not be able to identify the __consecutive bounces__ (bounces in a row) for a given user's email address.
You can also create rules for bounces. To learn about this, please see [[AdvancedBounceHandling Advanced Bounce Handling]].
If you have many bounces you can run a scheduler -like cron job- to process bounces, instead of having to do this manually. In that case you should disable manual processing of bounces in the config.php file:
- [[SetupCronJob Settin up a cron job]]


Revision [859]

Edited on 2006-10-20 04:57:24 by AlStillero [Some additions]
Additions:
Each time you send out a message to a substantial number of users, you should go to 'Process Bounces' to check for bounced messages. If you don't see any bounces right away, check again in a few days, as they may take a while to arrive.
If you do have bounces, do not remove them till a few days later, otherwise the system will not be able to identify the __consecutive bounces__ (bounces in a row) for a given user's email address.
You can also create rules for bounces. To learn about this, please see [[AdvancedBounceHandling Advanced Bounce Handling]].
===Using a cron job to process bounces===
If you have many bounces you can run a scheduler -like cron job- to process bounces, instead of having to do this manually. In that case you should disable manual processing of bounces in the config.php file:
**This code in config.php**
%%(php)
# set this to 0, if you set up a cron to download bounces regularly by using the
# commandline option. If this is 0, users cannot run the page from the web
# frontend. Read README.commandline to find out how to set it up on the
# commandline
define ("MANUALLY_PROCESS_BOUNCES",1);
%%
==Related pages==
- [[SetupCronJob Settin up a cron job]]
Deletions:
Each time you send out a message to a substantial number of users, you should go to 'Process Bounces' to check for bounced messages. If you don't see any bounces right away, check again in a few days, as they may take a while to arrive.
If you do have bounces, do not remove them till a few days later, otherwise the system will not be able to identify the __consecutive bounces__ (bounces in a row) for a given user's email address.
You can also create rules for bounces. To learn about this, please see [[AdvancedBounceHandling Advanced Bounce Handling]].
Related pages


Revision [839]

Edited on 2006-10-17 19:47:46 by AlStillero [added breadcrumb trail , some links, and minor edits]
Additions:
==[[PhplistDocumentation Phplist Documentation]] » [[MessageFunctionsInfo Message functions]] » ==
=====Process Bounces=====
Each time you send out a message to a substantial number of users, you should go to 'Process Bounces' to check for bounced messages. If you don't see any bounces right away, check again in a few days, as they may take a while to arrive.
If you do have bounces, do not remove them till a few days later, otherwise the system will not be able to identify the __consecutive bounces__ (bounces in a row) for a given user's email address.
You can also create rules for bounces. To learn about this, please see [[AdvancedBounceHandling Advanced Bounce Handling]].
Related pages
- [[ViewBouncesInfo View bounces]]
- [[PhpListConfigBounces Settings for handling bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]
[[CategoryDocumentation]]
Deletions:
[[PhplistDocumentation phplist Documentation]]
==========**Process Bounces Info:**==========
Everytime you send a message you should go to 'Process Bounces' to check for bounced emails. If you don't see any bounces check again in a few days, as they may take a while to arrive. If you do have bounces do not remove them till a few days later, otherwise the system will not be able to identify the consecutive bounces that occur.
In the Config file you have to congurate this:
%%(php) // Settings for handling bounces
=========================================================================
*/
# Message envelope. This is the email that system messages come from
# it is useful to make this one where you can process the bounces on
# you will probably get a X-Authentication-Warning in your message
# when using this with sendmail
# NOTE: this is *very* different from the From: line in a message
# to use this feature, uncomment the following line, and change the email address
# to some existing account on your system
# requires PHP version > "4.0.5" and "4.3.1+" without safe_mode
# $message_envelope = 'listbounces@yourdomain';
# Handling bounces. Check README.bounces for more info
# This can be 'pop' or 'mbox'
''$bounce_protocol = 'pop';
# set this to 0, if you set up a cron to download bounces regularly by using the
# commandline option. If this is 0, users cannot run the page from the web
# frontend. Read README.commandline to find out how to set it up on the
# commandline
define ("MANUALLY_PROCESS_BOUNCES",1);
# when the protocol is pop, specify these three
$bounce_mailbox_host = 'localhost';
$bounce_mailbox_user = 'popuser';
$bounce_mailbox_password = 'password';
# the "port" is the remote port of the connection to retrieve the emails
# the default should be fine but if it doesn't work, you can try the second
# one. To do that, add a # before the first line and take off the one before the
# second line
$bounce_mailbox_port = "110/pop3/notls";
#$bounce_mailbox_port = "110/pop3";
# when the protocol is mbox specify this one
# it needs to be a local file in mbox format, accessible to your webserver user
$bounce_mailbox = '/var/spool/mail/listbounces';
# set this to 0 if you want to keep your messages in the mailbox. this is potentially
# a problem, because bounces will be counted multiple times, so only do this if you are
# testing things.
$bounce_mailbox_purge = 1;
# set this to 0 if you want to keep unprocessed messages in the mailbox. Unprocessed
# messages are messages that could not be matched with a user in the system
# messages are still downloaded into PHPlist, so it is safe to delete them from
# the mailbox and view them in PHPlist
$bounce_mailbox_purge_unprocessed = 1;
# how many bounces in a row need to have occurred for a user to be marked unconfirmed
$bounce_unsubscribe_treshold = 5;%%

You can also create rules for bounces. To learn about that try this: [[AdvancedBounceHandling Advance Bounce Handling]]
[[PhpListConcepts Basic phplist Concepts]]
[[PhplistDocumentation phplist Documentation pages]]


Revision [677]

Edited on 2006-08-01 22:23:40 by AlmostatiC [edit for clarity]
Additions:
Everytime you send a message you should go to 'Process Bounces' to check for bounced emails. If you don't see any bounces check again in a few days, as they may take a while to arrive. If you do have bounces do not remove them till a few days later, otherwise the system will not be able to identify the consecutive bounces that occur.
Deletions:
Everytime you send a message you will hve to go to 'Process Bounces' to get the bounces emails. If you don't have any bounces don't alarm they might appear in a few days if you process again. If you do have bounces do not eliminate them, otherwise the system will not be able to identify the consecutive bounces when these take place.


Revision [579]

Edited on 2006-07-17 15:17:26 by HernoL
Additions:
[[PhplistDocumentation phplist Documentation]]
[[PhpListConcepts Basic phplist Concepts]]
[[PhplistDocumentation phplist Documentation pages]]
Deletions:
[[PhplistDocumentation Phplist Documentation]]
[[PhpListConcepts Basic phpList Concepts]]
[[PhplistDocumentation PHPlist Documentation pages]]


Revision [564]

Edited on 2006-07-13 01:26:46 by YanB [minor formatting]
Additions:
%%(php) // Settings for handling bounces
Deletions:
%%(PHP)Settings for handling bounces


Revision [554]

Edited on 2006-06-28 16:18:36 by HernoL
Additions:
[[PhplistDocumentation Phplist Documentation]]
----


Revision [546]

Edited on 2006-06-21 14:21:33 by HernoL
Additions:
[[PhpListConcepts Basic phpList Concepts]]
[[PhplistDocumentation PHPlist Documentation pages]]


Revision [537]

The oldest known version of this page was created on 2006-06-16 17:03:41 by HernoL
Page was generated in 0.0326 seconds