Revision [1767]
Last edited on 2008-12-10 01:50:11 by MichaelColeAdditions:
#$bounce_mailbox_port = "110/pop3/novalidate-cert"; # Try this to work around "self-cert" email server...
# http://www.php.net/manual/en/ref.imap.php
# http://www.php.net/manual/en/ref.imap.php
Additions:
**Note**: phpList bounce processing connects to your mail server via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList. If you have a shared hosting account, you should ask your host to include the [[http://php.net/imap IMAP module]] in your PHP installation. Additionally, [[http://php.net/manual/en/features.safe-mode.php PHP safe mode]] must be set to OFF, otherwise automatic bounce processing will not work. See also [[SystemRequirements System requirements]]
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host. See also this [[http://forums.phplist.com/viewtopic.php?p=45136#45136 tutorial]].
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host. See also this [[http://forums.phplist.com/viewtopic.php?p=45136#45136 tutorial]].
Deletions:
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host. See also this brief [[http://forums.phplist.com/viewtopic.php?p=45136#45136 tutorial]].
Additions:
**Note**: phpList bounce processing connects to your mail server via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList. If you have a shared hosting account, you should ask your host to include the [[http://php.net/imap IMAP module]] in your PHP installation. Additionally, [[http://php.net/manual/en/features.safe-mode.php PHP safe mode]] must be set to OFF, otherwise automatic bounce processing will not work.
Deletions:
Revision [1697]
Edited on 2008-10-31 05:57:49 by AlStillero [link to tutorial on forum + minor edits]Additions:
A **bounce** is an email message that is returned because it could not be delivered for a number of reasons: The mailbox of the recipient might be full, the email address might no longer be valid or temporarily disabled, the email address might be misspelled, etc. A bounce is not the same as an out-of-office reply. For more info, see this [[http://en.wikipedia.org/wiki/Bounce_message Wikipedia article on bounces]].
**Note**: phpList bounce processing connects to your mail server via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList. If you have a shared hosting account, you should ask your host to include the [[http://php.net/imap IMAP module]] in your PHP installation.
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host. See also this brief [[http://forums.phplist.com/viewtopic.php?p=45136#45136 tutorial]].
**Note**: in older versions of phplist (<= v2.10.2) the first "h" of THRESHOLD was missing, so if you are using it please change it to make it work properly.
While the above settings are the ones you will usually need to be changed, you may also need to review the defaults for the other bounce handling settings, like the protocol, mailbox port, using cron processing, etc. These settings can be found in:
**Note**: phpList bounce processing connects to your mail server via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList. If you have a shared hosting account, you should ask your host to include the [[http://php.net/imap IMAP module]] in your PHP installation.
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host. See also this brief [[http://forums.phplist.com/viewtopic.php?p=45136#45136 tutorial]].
**Note**: in older versions of phplist (<= v2.10.2) the first "h" of THRESHOLD was missing, so if you are using it please change it to make it work properly.
While the above settings are the ones you will usually need to be changed, you may also need to review the defaults for the other bounce handling settings, like the protocol, mailbox port, using cron processing, etc. These settings can be found in:
Deletions:
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host.
**Note**: in older versions of phplist (<= v2.10.2) the first "h" of THRESHOLD was misssing, so if you are using it please change it to make it work properly.
**Note**: phpList bounce processing connects to your mail sever via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList.
While the above settings are the ones you will ususally need to change, you may also need to review the defaults for the other bounce handling settings, like the protocol, mailbox port, using cron processing, etc. These settings can be found in:
Additions:
In the ##config.php## file you can set a special email address called the "message envelope address". The "message_envelope" address is included in the message header as the "''Return-Path''" address, and will be used to receive bounces. Make sure you create this email account. You can set the ''$message_envelope'' in your config.php file. Don't forget to uncomment that line, i.e. remove the ''#'' at the start of that line.
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code. See also [[http://tools.ietf.org/html/rfc2076 RFC 2076]] and [[http://tools.ietf.org/html/rfc3834 RFC 3834]].
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From:" address, i.e., the one recipients see in the From field of a message. The email address in the "From:" field is the one you tell users to place on their "safe list". It's a good idea to check your "From:" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code. See also [[http://tools.ietf.org/html/rfc2076 RFC 2076]] and [[http://tools.ietf.org/html/rfc3834 RFC 3834]].
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From:" address, i.e., the one recipients see in the From field of a message. The email address in the "From:" field is the one you tell users to place on their "safe list". It's a good idea to check your "From:" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
Deletions:
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code. See also [[http://tools.ietf.org/html/rfc2076 RFC 2076]].
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
Additions:
A **bounce** is an email message that is returned because it could not be delivered for a number of reasons: The mailbox of the recipient might be full, the email address might no longer be valid or temporarily disabled, the email address might be misspelled, etc. A bounce is not the same as an out-of-office reply. For more info, see [[http://en.wikipedia.org/wiki/Bounce_message Wikipedia]].
In the ##config.php## file you can set a special email address called the "message envelope address". The "message_envelope" address is included in the message header as the "''Return-Path''" address, and will be used to receive bounces. Make sure you create this email account.
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code. See also [[http://tools.ietf.org/html/rfc2076 RFC 2076]].
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
So, the "Return-Path" email address is the one that mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
In the ##config.php## file you can set a special email address called the "message envelope address". The "message_envelope" address is included in the message header as the "''Return-Path''" address, and will be used to receive bounces. Make sure you create this email account.
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code. See also [[http://tools.ietf.org/html/rfc2076 RFC 2076]].
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
So, the "Return-Path" email address is the one that mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
Deletions:
In the ##config.php## file you can set a special email address called the "message envelope address". The "message_envelope" address is included in the message header as the "''Errors-To''" address, and will be used to receive bounces.
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
So, the "Errors-To" email address is the one that mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
Additions:
In the ##config.php## file you can set a special email address called the "message envelope address". The "message_envelope" address is included in the message header as the "''Errors-To''" address, and will be used to receive bounces.
%%(php)$message_envelope = "mybounces@yourdomain.com";%%
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
So, the "Errors-To" email address is the one that mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
$bounce_mailbox_user = 'mybounces@domain.com';
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host.
$message_envelope = 'listbounces@yourdomain.com';
%%(php)$message_envelope = "mybounces@yourdomain.com";%%
You can check whether this has been setup correctly by displaying the header information of one of your messages, and by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they often will.
So, the "Errors-To" email address is the one that mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
$bounce_mailbox_user = 'mybounces@domain.com';
The format of the values you need to fill in may vary depending on how the server was configured. The "$bounce_mailbox_host" setting might for instance be 'localhost', 'yourpopservername.yourdomain.com', or an IP address. The "$bounce_mailbox_user" setting could be the full email address, just the prefix, or another popusername. Usually the values you would use in your normal email client, will work here too. If you are on a shared hosting account, you can also contact your host.
$message_envelope = 'listbounces@yourdomain.com';
Deletions:
%%(php)$message_envelope = "noreply@example.com";%%
You can check has been setup correctly by displaying the header information of one of your messages by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they will.
So, the "Errors-To" email address is the one mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
$bounce_mailbox_user = 'noreply@example.com';
# $message_envelope = 'listbounces@yourdomain';
Revision [1452]
Edited on 2007-11-14 13:43:54 by BasOvink [Added setting for blacklisting email on max bounces]Additions:
== From version 2.11.4 ==
%%(php)# When only user is unconfirmed when consecutive bounces are over the threshold, 'mark all users
# confirmed' will cause a lot of useless bouncing (email that is, not pogo). It's better to blacklist
# the address so phplist will never try again. Default on.
define('BLACKLIST_EMAIL_ON_BOUNCE', 1);%%
%%(php)# When only user is unconfirmed when consecutive bounces are over the threshold, 'mark all users
# confirmed' will cause a lot of useless bouncing (email that is, not pogo). It's better to blacklist
# the address so phplist will never try again. Default on.
define('BLACKLIST_EMAIL_ON_BOUNCE', 1);%%
Revision [1129]
Edited on 2007-05-08 15:45:16 by HernoL [misspelling aclaration and change (threshold)]Additions:
%%(php)$bounce_unsubscribe_threshold = 5;%%
**Note**: in older versions of phplist (<= v2.10.2) the first "h" of THRESHOLD was misssing, so if you are using it please change it to make it work properly.
**Note**: in older versions of phplist (<= v2.10.2) the first "h" of THRESHOLD was misssing, so if you are using it please change it to make it work properly.
Deletions:
Additions:
- [[ViewBouncesInfo View bounces]]
- [[ProcessBouncesInfo Process bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]>>One of the strengths of phpList is its handling of "bounces".
A **bounce** is an email message that is returned because it could not be delivered for a number of reasons: The mailbox of the recipient might be full, the email address might no longer be valid or temporarily disabled, the email address might be misspelled, etc. A bounce is not the same as an out-of-office reply.
===Setting up bounce handling===
**Message envelope**
In the ##config.php## file you can set a special email address called the "message envelope address". The "message_envelope" address is included in the message header as the "Errors-To" address, and will be used to receive bounces.
You can check has been setup correctly by displaying the header information of one of your messages by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they will.
**Bounce mailbox**
So, the "Errors-To" email address is the one mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
**Bounce treshhold**
There is one additional setting, a "how many strikes before they're out" rule. This establishes your policy of how many __consecutive bounces (bounces in a row)__ you'll accept before flagging the user's account "unconfirmed". This is that setting:
**Note**: phpList bounce processing connects to your mail sever via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList.
**Other settings**
While the above settings are the ones you will ususally need to change, you may also need to review the defaults for the other bounce handling settings, like the protocol, mailbox port, using cron processing, etc. These settings can be found in:
- [[ViewBouncesInfo View bounces]]
- [[ProcessBouncesInfo Process bounces]]
- [[ProcessBouncesInfo Process bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]>>One of the strengths of phpList is its handling of "bounces".
A **bounce** is an email message that is returned because it could not be delivered for a number of reasons: The mailbox of the recipient might be full, the email address might no longer be valid or temporarily disabled, the email address might be misspelled, etc. A bounce is not the same as an out-of-office reply.
===Setting up bounce handling===
**Message envelope**
In the ##config.php## file you can set a special email address called the "message envelope address". The "message_envelope" address is included in the message header as the "Errors-To" address, and will be used to receive bounces.
You can check has been setup correctly by displaying the header information of one of your messages by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the From field of a message. The email address in the "From" field is the one you tell users to place on their "safe list". It's a good idea to check your "From" email account for replies from subscribers, because even if you tell them not to reply to messages-- they will.
**Bounce mailbox**
So, the "Errors-To" email address is the one mail system auto-responders (as opposed to user auto-responders such as "out-of-office" replies) will send bounces to if delivery of the message failed or was delayed. It is therefore this account's connection info you need to setup in config.php:
**Bounce treshhold**
There is one additional setting, a "how many strikes before they're out" rule. This establishes your policy of how many __consecutive bounces (bounces in a row)__ you'll accept before flagging the user's account "unconfirmed". This is that setting:
**Note**: phpList bounce processing connects to your mail sever via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList.
**Other settings**
While the above settings are the ones you will ususally need to change, you may also need to review the defaults for the other bounce handling settings, like the protocol, mailbox port, using cron processing, etc. These settings can be found in:
- [[ViewBouncesInfo View bounces]]
- [[ProcessBouncesInfo Process bounces]]
Deletions:
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]>>One of the true strengths of phpList is its handling of "bounces". A **bounce** is a email that is returned to its sender. There are many reasons for a bounce; the account might no longer be valid, it might be over some limit, it might be temporarily disabled, etc. Many people will subscribe using their work email address, when they change jogs the account will (hopefully if the sysadmins are doing their jobs) but the account is eventually disabled. A bounce is not the same as an out of office reply.
In the ##config.php## file you can set a special email account called the "message envelope address":
The "message_envelope" address is an email address included in the message header as the "Errors-To" address, and will be used to receive bounces. You can display the header information of a message by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the from field of a message, and would reply to if they click on "reply" in their mail client. The "From" email address is the one you tell them to "safe list". It's a good idea to check your "From" email address for replies from subscribers, because even if you tell them not to reply to messages-- they will.
So, the "Errors-To" email address is the one system auto-responders (as opposed to user responders such as "out of office" replies) will send an email to, if delivery of the message failed or was delayed. It's this account that captures bounces. It is therefore this account's connection info you'll setup in config.php:
There is one additional setting, a "how many strikes before they're out" rule. This establishes your policy of how many consecutive (in a row) bounces you'll accept before flagging the user's account "inactive". This is that setting:
NOTE: phpList bounce processing connects to your mail sever via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList.
- [[ViewBouncesInfo Viewing bounces]]
Additions:
==[[PhplistDocumentation Phplist Documentation]] » [[MessageFunctionsInfo Message functions]] » ==
Deletions:
Additions:
>>See also:
- [[ViewBouncesInfo Viewing bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]>>One of the true strengths of phpList is its handling of "bounces". A **bounce** is a email that is returned to its sender. There are many reasons for a bounce; the account might no longer be valid, it might be over some limit, it might be temporarily disabled, etc. Many people will subscribe using their work email address, when they change jogs the account will (hopefully if the sysadmins are doing their jobs) but the account is eventually disabled. A bounce is not the same as an out of office reply.
**Related pages**
- [[ViewBouncesInfo Viewing bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]
- [[ViewBouncesInfo Viewing bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]>>One of the true strengths of phpList is its handling of "bounces". A **bounce** is a email that is returned to its sender. There are many reasons for a bounce; the account might no longer be valid, it might be over some limit, it might be temporarily disabled, etc. Many people will subscribe using their work email address, when they change jogs the account will (hopefully if the sysadmins are doing their jobs) but the account is eventually disabled. A bounce is not the same as an out of office reply.
**Related pages**
- [[ViewBouncesInfo Viewing bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]
Deletions:
Additions:
==[[PhplistDocumentation Phplist Documentation]]» [[PhpListConfiguration Configuring]] » ==
Deletions:
==Installation » [[PhpListConfiguration Configuring]] »==
Revision [790]
Edited on 2006-10-16 19:03:55 by AlStillero [Updated to ver. 2.10.3, added breadcrumb trail and minor edits]Additions:
>>See also [[ViewBouncesInfo Viewing bounces]]>>One of the true strengths of phpList is its handling of "bounces". A **bounce** is a email that is returned to its sender. There are many reasons for a bounce; the account might no longer be valid, it might be over some limit, it might be temporarily disabled, etc. Many people will subscribe using their work email address, when they change jogs the account will (hopefully if the sysadmins are doing their jobs) but the account is eventually disabled. A bounce is not the same as an out of office reply.
In the ##config.php## file you can set a special email account called the "message envelope address":
The "message_envelope" address is an email address included in the message header as the "Errors-To" address, and will be used to receive bounces. You can display the header information of a message by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the from field of a message, and would reply to if they click on "reply" in their mail client. The "From" email address is the one you tell them to "safe list". It's a good idea to check your "From" email address for replies from subscribers, because even if you tell them not to reply to messages-- they will.
So, the "Errors-To" email address is the one system auto-responders (as opposed to user responders such as "out of office" replies) will send an email to, if delivery of the message failed or was delayed. It's this account that captures bounces. It is therefore this account's connection info you'll setup in config.php:
NOTE: phpList bounce processing connects to your mail sever via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList.
$bounce_unsubscribe_threshold = 5;%%
In the ##config.php## file you can set a special email account called the "message envelope address":
The "message_envelope" address is an email address included in the message header as the "Errors-To" address, and will be used to receive bounces. You can display the header information of a message by looking at its properties and source code.
Note that the message envelope address is different from the email address you supply when writing a message, which is the "From" address, i.e., the one recipients see in the from field of a message, and would reply to if they click on "reply" in their mail client. The "From" email address is the one you tell them to "safe list". It's a good idea to check your "From" email address for replies from subscribers, because even if you tell them not to reply to messages-- they will.
So, the "Errors-To" email address is the one system auto-responders (as opposed to user responders such as "out of office" replies) will send an email to, if delivery of the message failed or was delayed. It's this account that captures bounces. It is therefore this account's connection info you'll setup in config.php:
NOTE: phpList bounce processing connects to your mail sever via a PHP module called IMAP (which should not be confused the IMAP mail protocol). Your PHP server must have this module installed to be able to use the bounce handling features of phpList.
$bounce_unsubscribe_threshold = 5;%%
Deletions:
One of the true strengths of phpList is its handling of "bounces". A **bounce** is a email that is returned to its sender. There are many reasons for a bounce; the account might no longer be valid, it might be over some limit, it might be temporarily disabled, etc. Many people will subscribe using their work email address, when they change jogs the account will (hopefully if the sysadmins are doing their jobs) but the account is eventually disabled.
A bounce is not the same as an out of office reply.
In the ##config.php## file you're able to set a special email account:
This is different from the email address you supply when writing a Message, that's the "From" address, the one recipients see and would reply to if they just click "reply" from their mail client. The "From" email is the one you tell them to "safe list", and it's a good idea to check this for replies, even if you tell 'em not to -- they will.
No, the "message_envelope" address is another email account that's included in your outbound Messages in the message source's header as the "Errors-To" address.
"Errors-To" is the email address that system auto-responders (as opposed to user responders such as "out of office" replies) will send an email if delivery of the message is delayed or not possible. It's this account that captures bounces. It is therefore this account's connection info you'll setup in config.php:
NOTE: phpList bounce processing connects to your mail sever via IMAP. Your PHP installation must have this module available to use the automated bounce handling.
$bounce_unsubscribe_treshold = 5;%%
Revision [596]
Edited on 2006-07-17 15:51:25 by HernoLAdditions:
[[PhplistDocumentation phplist Documentation]]
Deletions:
Revision [510]
Edited on 2006-05-02 14:04:29 by ZelWintersAdditions:
One of the true strengths of phpList is its handling of "bounces". A **bounce** is a email that is returned to its sender. There are many reasons for a bounce; the account might no longer be valid, it might be over some limit, it might be temporarily disabled, etc. Many people will subscribe using their work email address, when they change jogs the account will (hopefully if the sysadmins are doing their jobs) but the account is eventually disabled.
Deletions:
Revision [509]
Edited on 2006-05-02 14:04:03 by ZelWintersAdditions:
%%(php)$message_envelope = "noreply@example.com";%%
Deletions:
Additions:
CategoryDocumentation
Additions:
>>See also [[ViewBouncesInfo Viewing bounces]]>>
In the ##config.php## file you're able to set a special email account:
In the ##config.php## file you're able to set a special email account:



