The user requests that the system process bounced unidentified messages, as currently no action is taken when bounces are signaled as such.
After noticing my bounce count is roughly the same after there were supposed to be consecutive bounces, I've realized when bounces were signaled as `bounced unidentified message` - and in those cases it seems no processing takes place at all. In other words, a subscriber's mail can bounce indefinitely and no action will be taken. The reason is [function processMessages](https://github.com/phpList/phplist3/blob/main/public_html/lists/admin/processbounces.php#L409) checks `$GLOBALS['tables']['user_message_bounce']`, but that table only lists identified bounces, so it's kind of a vicious circle. The irony is the user is known, it's just the message that is unknown. So if the user is known and we know there was a bounce, it should definitely go against that user's consecutive bounces and unconfirm if needed. Otherwise it affects being considered as a spammer.