On Mon, 11 Sep 2023, at 21:24, Support 3Hound via mailop wrote:
> During years the FBL became a kind of "safe feature" for users that prefer to
> click "junk" or "spam" and be sure they will not receive anymore.
> […]
> FBL generates also a good data flow for the mailbox provider that may filter
> the "next e-mail" from a sender that don't honor the FBL (or can't act
> realtime the unsubcribe) generating a better service for the end user and a
> way to identify good player and bad ones.
That's a … different perspective on this behaviour. Treating an FBL report as
"unsubscribe" (or rather *proscribe* at the ESP level) is terrible for user
experience and not at all what the feedback loop should be used for IMO. Users
click Report Spam by mistake one time (this happens *a lot)* and suddenly they
don't get emails they want. Even worse, as the proscription is often at the
ESP-level, the original sender ban be unaware of the block and thinks they are
still sending correctly. These are a nightmare for our customer support team to
deal with — the sender's support are saying they are sending the message, our
support are telling the customer there's no logs of it ever reaching our
servers. The customer is stuck in the middle
This has already caused us to drastically reduce the times we send FBL reports
at Fastmail — not every Report Spam will do so, only if the user repeatedly
does so for a specific sender — and I am still 🤏 this close to stopping sending
anything.
Feedback loops should be used by ESPs to identify bad *senders*, by looking at
aggregate reports. Never for unsubscribing specific recipients.
Neil.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
