Charles Lindsey wrote:
The "less technically oriented" user, and especially a newbie who has just
joined the list, will do whatever his MUA defaults to. Agreed, an MUA that
understands MFT should keep a database of lists that the user has had
occasion to use, and should ask whether that user is subscribed when a new
list is encountered for the first time. It can then generate an
appropriate MFT header. That AIUI is how MFT is intended to operate.
Some people use multiple UAs, possibly at multiple locations. Anything
that requires extensive configuration is a problem. Also, some people
read lists via a web archive; an MUA has no way to determine that.
And people change mailing list subscriptions (e.g. when they go on