We were just discussing this on IRC, and bkirsch's suggestion is in
line with what I proposed in #chandler today:
11:16am Morgen > "I still say we just have In and Out be explicit
collections that only the mail framework adds things to, have In
and Out still be Mine collections, and then if the user subscribes
to a collection that happens to have emails, those emails will only
get into the Dashboard if the user marks the collection as "mine".
Those emails won't show up in In/Out, but that's okay, right?"
On Sep 29, 2006, at 11:30 AM, Brian Kirsch wrote:
Hello,
According to the design team specs the desired functionality for
In and Out is as follows:
If the "me" email address is in the To or Cc of a message it
appears in the "In" collection.
If the "me" email address is in the From or Reply-To it appears in
the "Out" collection.
As mentioned in other posts on this thread there are certainly
performance issues to consider.
When creating Mail Message items the Mail Service could based on
the headers manually add the messages to the appropriate collections.
This would actually be better than a filter for a variety of
reasons including the fact that the "me" email address may change
over time (i.e. I switch from Earthlink to Comcast). You would
still want your old mail from the Earthlink to appear in the In
and Out even though the account is no longer active.
Thoughts?
-Brian
Morgen Sagen wrote:
Bug 6857 is a request to take the In and Out collections out of
the "Mine" collection. This is a trivial fix (removing a couple
lines from osaf/pim/__init__.py), but I wonder if there was a
reason these were part of Mine to begin with. Anyone see a
problem with taking them out of Mine?
~morgen
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
--
Brian Kirsch Internationalization Architect / Mail Service Engineer
Open Source Applications Foundation
543 Howard Street 5th Floor
San Francisco, CA 94105
http://www.osafoundation.org
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
