On Thu, 28 Sep 2006, Morgen Sagen wrote:
2) Change the filter for "In" and "Out" to also examine the email headers
and only include those messages that are actually to or from the user. I
have a feeling this will be inefficient, but maybe someone can suggest a
good way to implement it.
Without regards to efficiency, if In and Out are mine and contain mail that
is not mine (ie, not send by or to me) then there is a contracdiction with
their perceived, conventional role. If In and Out end up with mail I've had
nothing to do with, I'd be confused.
That's exactly the problem we've got now. In and Out contain all email
messages, regardless of sender/recipient. If it's too inefficient to actually
examine the sender/recipient headers to see if they match *any* of the user's
email accounts, perhaps we could...
3) Add a new boolean attribute to mail message items that indicates whether
they entered the repository via the mail framework or the sharing framework
(and change the In and Out filters to only match messages that were created
by the mail framework)
4) Change In and Out so that they aren't based on a filter, but instead have
the mail framework explicitly add mail messages to those collections. Thus
messages brought in via sharing won't accidentally appear in them.
Agreed. I think any of these could be made to work. My earlier replies were
about the "let's make In and Out not mine anymore" approach which I find
confusing.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
