You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the bug and steps to reproduce:
When a transactional email bounces, although I can see the bounce email in the POP3 account, it does not seem that the address is being added to the blocklist. The bounce handling and blocklisting does work for regular campaigns.
As I'm automatically sending a transactional Welcome email on subscribing to the mailing list, this means that any incorrect email registered will generate at least two bounces instead of one before it's blocklisted (the second bounce being the first actual campaign email sent).
As a result, instead of the list seeing a regular stream of bounces being handled on a day to day basis, there is a larger amount of bounces all at once every few weeks when the campaign is sent, which I imagine is not good for sending reputation.
Is bounce handling on transactional email supposed to work or is this as designed? I don't see any technical reason why it could not blocklist those addresses on reception of a bounce.
And thanks for your work on Listmonk, it's been very smooth and easy to use so far.
The text was updated successfully, but these errors were encountered:
Hi @jbarnoin. listmonk doesn't currently support bounce handling for transactional e-mails. This is something that can be considered for a future release.
Version:
Description of the bug and steps to reproduce:
When a transactional email bounces, although I can see the bounce email in the POP3 account, it does not seem that the address is being added to the blocklist. The bounce handling and blocklisting does work for regular campaigns.
As I'm automatically sending a transactional Welcome email on subscribing to the mailing list, this means that any incorrect email registered will generate at least two bounces instead of one before it's blocklisted (the second bounce being the first actual campaign email sent).
As a result, instead of the list seeing a regular stream of bounces being handled on a day to day basis, there is a larger amount of bounces all at once every few weeks when the campaign is sent, which I imagine is not good for sending reputation.
Is bounce handling on transactional email supposed to work or is this as designed? I don't see any technical reason why it could not blocklist those addresses on reception of a bounce.
And thanks for your work on Listmonk, it's been very smooth and easy to use so far.
The text was updated successfully, but these errors were encountered: