Mimi Yin wrote:I think mailing list subscription is pretty non-standard - there are a few major systems for open-source mail, but I think most are a haphazard set of different combinations of putting "Subscribe" in the subject line, in the body, signing up on a web site, etc.
- What about subscribing to and Setting up Mailing lists. If we had UI in Chandler for users to "Subscribe" to mailing lists, would this be a better "model" for helping users understand that they can "filter" mailing lists into their own collections automatically, the same way they can have separate Inboxes for each email account.
However, opera mail handles this rather well - it seems to identify common mailing list headers in your existing mail (which are also non-standard, but perhaps easier to detect) and creates virtual folders for each mailing list you're on.
There's a standard going around that puts metainformation about the mailing list in the headers... Opera Mail seems to do its indexing via it. The only other client I've seen aware of it is pine... OSAF's mailman installation does it, the headers on this email have:
List-Id: Design Discussions <design.osafoundation.org>I guess it's this rfc? http://www.ietf.org/rfc/rfc2369.txt
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/design >,
<mailto:[EMAIL PROTECTED]?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/design >
List-Post: <mailto:[email protected]>
List-Help: <mailto:[EMAIL PROTECTED]?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/design>,
<mailto:[EMAIL PROTECTED] ?subject=subscribe>
Better formalizing this to support automatic subscription and unsubscription would seem to be a logical mechanism to support smarter mailing lists in the future. (e.g. Deme! http://groupspace.org !)
-Brendan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
