Treat spam reports / complaints separately from other types of bounces.

[bamboowonder]

With an end goal of optimum deliverability and reaching people's inboxes. Email sender reputation is critical. This is measured by email service providers in a number of ways.

Two of the benchmarks commonly used is how bounces and spam/complaints are handled.

In this context, a bounce is any failed/delayed delivery that is not "successfully delivered" or "spam/complaint".

There are degrees of severity with bounces.

Spam/complaints are extremely sensitive, and resending to anyone who has marked you as spam will immediately affect your entire domain's deliverability.

Bounces are less sensitive, and open to interpretation as to how many bounces per email are acceptable. Email providers look at both the per-email bounces, and overall account bounce percentage when determining whether to put your email in spam or the inbox.

---

The current functionality for bounce threshold is great for letting the user determine what is acceptable.

However spam complaints should always be treated as an immediate hard block, since a Listmonk user may not even realize how badly it will affect their deliverability to resend. And understandably they want to treat generic bounces separately.

Thank you for your consideration.

[jackdanielux]

But is spam/complaint treated as bounce for major SMTP providers?

If yes, only then this threshold of 1 will help, otherwise it would continue to deliver it to their inboxes.

On Thu, 30 Sep, 2021, 9:00 pm David Bamboo, @.***> wrote:

With an end goal of optimum deliverability and reaching people's inboxes. Email sender reputation is critical. This is measured by email service providers in a number of ways.

Two of the benchmarks commonly used is how bounces and spam/complaints are handled.

In this context, a bounce is any failed/delayed delivery that is not "successfully delivered" or "spam/complaint".

There are degrees of severity with bounces.

Spam/complaints are extremely sensitive, and resending to anyone who has marked you as spam will immediately affect your entire domain's deliverability.

Bounces are less sensitive, and open to interpretation as to how many bounces per email are acceptable. Email providers look at both the per-email bounces, and overall account bounce percentage when determining whether to put your email in spam or the inbox.

The current functionality for bounce threshold is great for letting the user determine what is acceptable.

However spam complaints should always be treated as an immediate hard block, since a Listmonk user may not even realize how badly it will affect their deliverability to resend. And understandably they want to treat generic bounces separately.

Thank you for your consideration.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/knadh/listmonk/issues/497, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARESAVENRTZQKJITYBXG4U3UER7AFANCNFSM5FCTVQVQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[knadh]

https://github.com/knadh/listmonk/commit/5fc28a733c7d6d9e6e3a2d4cc699e009c142bf35 adds support for per-bounce-type actions.