Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Also process bounced unidentified message #1022

Open
lwcorp opened this issue Feb 18, 2024 · 2 comments
Open

Also process bounced unidentified message #1022

lwcorp opened this issue Feb 18, 2024 · 2 comments

Comments

@lwcorp
Copy link
Contributor

lwcorp commented Feb 18, 2024

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 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.

@michield
Copy link
Member

You mean the transactional emails, as opposed to a campaign? Is there any reason why the bounce is not identified? Maybe it's better to fix that instead.

@lwcorp
Copy link
Contributor Author

lwcorp commented Feb 18, 2024

No, I mean standard campaigns. I don't know why so many bounces are like this, but it's out of my control as it comes from various ISPs. All I know is phpList does know the user should it chooses to address it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants