"One-click Unsubscribe: Needs work — Ensure one-click unsubscribe is correctly implemented for your subscription messages One-click unsubscribe allows recipients to easily unsubscribe instead of marking your messages as spam"
This is a LIE. Most Mailman lists already implement the RFC 2369 header fields, which already contain the necessary "click to unsubscribe" information. What RFC 8058 provides is a shortcut for the user that burdens the list.
I'm not going to defend Google's implementations and policies here, but the RFC 2369 fields are regularly insufficient. Several times a month I have people asking to unsubscribe because they don't remember what address they are subscribed as across aliases, ignored-dots, and forwarding. (Yes, I include the subscriber address in the footer of every message.) At least as many people are going to just be marking every message as spam rather than contacting the -owner address, and that hurts deliverability.
Regardless of that, the little box that says "this message is from a mailing list; would you like to unsubscribe?" that appears on my iDevice is extremely useful and a great user affordance. The purpose of list management software is to meet the needs of list administrators and list subscribers, and this definitely qualifies. RFC 8058 is a standard; there's no reason for us to be needlessly hostile to implementing it. (That's independent from prioritizing it or finding someone with the time, of course.)
I'm pretty sure, as below, that we need to implement RFC 8058 headers in order to maintain deliverability to GMail.
That's easy enough. Just configure your MTA to DKIM sign that field (if Mailman is doing the signing you can configure it in mailman/config/schema.cfg), and insert before line 22 of mailman/handlers/rfc_2369.py [..]
Are you suggesting just adding bogus RFC 8058 headers to appease GMail? That's likely to anger them more. Section 3.1 of RFC 8058 says: The URI in the List-Unsubscribe header MUST contain enough information to identify the mail recipient and the list from which the recipient is to be removed, so that the unsubscription process can complete automatically.
The leave address is not sufficient for this, and as per up-thread cannot be applied in rfc_2369.py because it is pre-personalization.
The only tracker issue I can find related to this is https://gitlab.com/mailman/mailman/-/issues/1099 -- is that the best place to discuss implementation?
Yes. [...]
OK; great. That's what I was looking for. I may have some time at the end of the year to look at this since we have winter shutdown PTO.
I see in your later message that you haven't enabled personalization in Mailman. [...]
I don't see where I've given that impression; if I did it was in error. All of my list messages have full personalization enabled. It's necessary to add the subscription address to the footer and do proper bounce tracking.
don't think there's really any case in which personalization should be disabled in the modern internet mail world, and would argue (but not very strongly) that the options to turn this off probably ought be removed from Mailman. (At the very least, personalization ought be the default.)
Regards, --Jered