This is slightly different, for once it applies only to mailinglists and
2nd is that its HOW TO opt out if mailing list you're already on and not
a system indicating global opt-in/out choice.
But I guess I might need to separate into the section of how to indicate
that you want to be opt-out for new senders of commercial email and
section on how to actually opt-out when you're already receiving email.
Or possibly sections should be for global opt-out and specific opt-out to
particular maillist or particular domain.
P.S. Yes, there is an RFC 2369 on mailing list headers.
On Tue, 25 Mar 2003, Kee Hinckley wrote:
At 3:22 PM -0800 3/24/03, william(_at_)elan(_dot_)net wrote:
Any other distribution means I missed?
There are psuedo standards (Maybe there's an RFC? I haven't checked.
Probably.) such as the one followed by this list:
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
<mailto:asrg-request(_at_)ietf(_dot_)org?subject=unsubscribe>
I should note that there seems to be some variation in the format of
that field (I had to write a parser for it last month).
I'm not sure where mail-based opt-out systems fall in what you are
putting together.
The other two semi-standards are the listname-request(_at_)example(_dot_)com
(with subject unsubscribe) and listname-off(_at_)example(_dot_)com(_dot_)
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg