On Jan 6, 2017, at 2:00 PM, Mary Ann Kelley maryann@thehomeschoolmom com [Dada Mail Developers] dadadev@PROTECTED wrote:

I understand the whole thing about stopping automated processes, but I don’t think this has to be automated to that degree Just inserting the same link that is at the bottom (the one that takes them to the unsubscribe page) would work fine

I'm a little confused, as the article you linked just says that iOS sends an email using the email embedded in the List-Unsubscribe header, and does nothing with the unsubscribe link So, removing the email would do I guess remove the unsub button?

It seems inefficient for each list manager to have to handle this in code and keep up with manually making the change after each update, when this is a trend that isn’t going to go away

Well, there is no feature to manipulate the List-Unsubscribe header, that's true It's probably not going to be a priority for me to add this feature I'm faced many times with the problem that adding features means adding complexity, and complexity itself causes confusion I'm not sure if it seems worth it, in this scenario, but rather use the best practices as spec'd in the RFC It's true that many times my decisions are not always something that users agree with, but the source is there to allow that sort of customization

As it is, Dada is forcing them to use the option that doesn’t do what it is supposed to (unsubscribe the email) and makes work for the list manager (by generating a reply that has to be manually dealt with) I can’t see how this is an advantage to anyone

I mean, I sort of disagree, it's doing what it's supposed to do: it's alerting the list owner that someone wants to unsubscribe It does require manual intervention by the list owner, but the list owner should, I think know how to remove someone from their list manually, as the scenario will still happen: people do just reply directly to the mailing list, asking to be removed The List Owner will never be able to remove themselves from this responsibility