I worked on a year long project to rebuild our payments system only to learn the company had been undergoing talks and was acquired by a different payment system competitor. Even though the pending acquisition was going on for the last 6 months of the project nobody told us to stop working on this thing that the top level people knew would never be used.
“You need a link not list-unsubscribe” is not fully accurate according to my reading. They are asking senders to support the one click unsubscribe rfc, which uses list-unsubscribe.
There is an app called grog knots which I think is made by the same people. Best few bucks I’ve ever spent for an app. Love having a bunch of knot diagrams handy when I’m out trying to do something.
The 100 requests per minute fee oauth tier is how you would want to handle this right? The requests should be authenticated as if it was the current logged in user anyways.