Additions:
~- **Delete all unidentified (> 2 months old)**: will delete all unidentified bounces older than 2 months.
Deletions:
Additions:
===View bounces===
The View bounces pages will display a listing of bounces received. In most cases they will be identified for a user and a message. If you run a live system, do not delete the bounces, because the system would not be able to identify the consecutive bounces, once more bounces come back. However, with larger lists you may need to clean up the database from time to time, and delete some of the oldest bounces to save some space.
The view bounces page provides a number of options to maintain the bounces database. Most options speak for themselves:
~- **Delete all unidentified (> 2 months old)**: will delete all unidentied bounces older than 2 months.
~- **Delete all processed (> 2 months old)**: will delete all processed bounces older than 2 months.
~- **Delete all**: this will delete all bounced messages in the database.
~- **Reset bounces**: this will reset the bounce count to zero for all users.
The View bounces pages will display a listing of bounces received. In most cases they will be identified for a user and a message. If you run a live system, do not delete the bounces, because the system would not be able to identify the consecutive bounces, once more bounces come back. However, with larger lists you may need to clean up the database from time to time, and delete some of the oldest bounces to save some space.
The view bounces page provides a number of options to maintain the bounces database. Most options speak for themselves:
~- **Delete all unidentified (> 2 months old)**: will delete all unidentied bounces older than 2 months.
~- **Delete all processed (> 2 months old)**: will delete all processed bounces older than 2 months.
~- **Delete all**: this will delete all bounced messages in the database.
~- **Reset bounces**: this will reset the bounce count to zero for all users.
Revision [1491]
Edited on 2008-01-12 01:06:16 by JonathanMandelAdditions:
Before you can View Bounces, you must Process Bounces.
Revision [1453]
Edited on 2007-11-14 13:46:54 by BasOvink [Added info on blacklisting email on max bounces]Additions:
== From version 2.11.4 ==
When user is only unconfirmed, the reconcile function 'mark all users confirmed' will cause a lot of useless bouncing. It's better to blacklist the address as well so phplist will never try again. Default on.
When user is only unconfirmed, the reconcile function 'mark all users confirmed' will cause a lot of useless bouncing. It's better to blacklist the address as well so phplist will never try again. Default on.
Additions:
- **mailbox full**: the user needs to clear their email inbox. You may be able to deliver messages in a later stage.
- **user/alias doesn't exist/not found**: probably misspelled name in the email address, or deleted user
- **domain/tld unresolved / doesn't exist**: probably misspelled domain name in the email address.
When any of these events occur, an email is usually sent to the email address defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config.php file. All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist cannot tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user's address. When the number of __consecutive counts__ for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
If you need more granularity, and want to distinguish between different types of bounces and determine what to do with them, you can enable "[[AdvancedBounceHandlingInfo advanced bounce handling]]".
- [[ViewBouncesInfo View bounces]]
- [[ProcessBouncesInfo Process bounces]]
- **user/alias doesn't exist/not found**: probably misspelled name in the email address, or deleted user
- **domain/tld unresolved / doesn't exist**: probably misspelled domain name in the email address.
When any of these events occur, an email is usually sent to the email address defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config.php file. All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist cannot tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user's address. When the number of __consecutive counts__ for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
If you need more granularity, and want to distinguish between different types of bounces and determine what to do with them, you can enable "[[AdvancedBounceHandlingInfo advanced bounce handling]]".
- [[ViewBouncesInfo View bounces]]
- [[ProcessBouncesInfo Process bounces]]
Deletions:
- **user/alias doesn't exist/not found**: probably misspelled, or deleted user
- **domain/tld unresolved / doesn't exist**: probably misspelled address
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config.php file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user's address. When the number of counts for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
- [[ViewBouncesInfo Viewing bounces]]
Additions:
==[[PhplistDocumentation Phplist Documentation]] » [[MessageFunctionsInfo Message functions]] » [[PhpListConfigBounces Settings for handling bounces]] »==
**Related pages**
- [[ViewBouncesInfo Viewing bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]
**Related pages**
- [[ViewBouncesInfo Viewing bounces]]
- [[AdvancedBounceHandlingInfo Advanced bounce handling]]
Deletions:
Additions:
==[[PhplistDocumentation Phplist Documentation]]» [[PhpListConfiguration Configuring]] » [[PhpListConfigBounces Settings for handling bounces]] »==
Deletions:
==Installation » [[PhpListConfiguration Configuring]] » [[PhpListConfigBounces Settings for handling bounces]] » ==
Additions:
==Installation » [[PhpListConfiguration Configuring]] » [[PhpListConfigBounces Settings for handling bounces]] » ==
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config.php file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config.php file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
Deletions:
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
Additions:
==Installation » [[PhpListConfiguration Configuring]] » [[PhpListConfigBounces Settings for setting up bounces]] » ==
Email messages can bounce for several reasons:
Email messages can bounce for several reasons:
Deletions:
Email messages can bounce for several reasons;
Additions:
==Installation » [[PhpListConfiguration Configuring]] » [[ViewBouncesInfo View Bounces]]==
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
**bounce threshhold** (##''$bounce_unsubscribe_treshold = 5;''##) in the config.php file.
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user's address. When the number of counts for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##''$message_envelope = "noreplay@example.com";''## in the config file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart, i.e., it can't distinguish a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
**bounce threshhold** (##''$bounce_unsubscribe_treshold = 5;''##) in the config.php file.
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user's address. When the number of counts for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
Deletions:
**bounce threshhold** (##$bounce_unsubscribe_treshold = 5;## in the config file)
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user/address. When the number of counts for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete, or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
Additions:
[[PhplistDocumentation Phplist Documentation]]
----
=====View Bounces=====
- **mailbox full**: the user needs to clear their email inbox
- **user/alias doesn't exist/not found**: probably misspelled, or deleted user
- **mail server temporarily not available**: server probably down
- **mail server permanently not available**: server down for a long time, or not communicating with YOUR server
- **domain/tld unresolved / doesn't exist**: probably misspelled address
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##$message_envelope = "noreplay@example.com";## in the config file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart. ie. it can't tell a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
**bounce threshhold** (##$bounce_unsubscribe_treshold = 5;## in the config file)
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user/address. When the number of counts for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete, or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
----
CategoryDocumentation
----
=====View Bounces=====
- **mailbox full**: the user needs to clear their email inbox
- **user/alias doesn't exist/not found**: probably misspelled, or deleted user
- **mail server temporarily not available**: server probably down
- **mail server permanently not available**: server down for a long time, or not communicating with YOUR server
- **domain/tld unresolved / doesn't exist**: probably misspelled address
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by ##$message_envelope = "noreplay@example.com";## in the config file). All these emails come from different servers, different mail programs, and in different formats and layouts: PHPlist can not tell them apart. ie. it can't tell a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a
**bounce threshhold** (##$bounce_unsubscribe_treshold = 5;## in the config file)
When an email is received at the bounce address and is processed in PHPlist, PHPlist tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user/address. When the number of counts for a given email address reaches the threshhold, PHPlist unconfirms the user. It doesn't delete, or blacklist the user. By unconfirming the user, PHPlist will refuse to send it another message (unless the email address becomes confirmed again).
----
CategoryDocumentation
Deletions:
- user/alias doesn't exist/not found; probably misspelled, or deleted user
- mail server temporarily not available; server probably down
- mail server permanently not available; server down for a long time, or not communicating with YOUR server
- domain/tld unresolved / doesn't exist; probably misspelled address
When any of these events occur, an email is usually sent to the respective address (defined in PHPlist by $message_envelope = "noreplay@example.com"; in the config file). All these emails (as you've probably seen) come from different servers, different mail programs, and in different formats and layouts. PHPlist can not tell them apart. ie. It can't tell a 'Mailbox full message' from a 'domain/tld unresolved / doesn't exist' message. That's why it uses a bounce threshhold ($bounce_unsubscribe_treshold = 5; in the config file)
When an email is received at the bounce address and is processed in PL, PL tries to find the email address that the bounce message refers to, and counts a 'bounce' for that user/address. When the number of counts for a given email address reaches the threshhold, PL unconfirms the user. It doesn't delete, or blacklist the user. By unconfirming the user, PL will refuse to send it another message (unless the email address becomes confirmed again).
