[Design] Email in Chandler

[Oren Sreebny]

Mimi and folks:

Though most clients include filtering, if you're living in an IMAP  
world it's always seemed more reasonable to me to do your filtering  
on the IMAP server. Here at UW, we've implemented a web-based filter  
interface that allows folks to do server-side filtering. I don't know  
if that's common, but if it is, you could save yourself a lot of  
effort by not supporting filters on the client.

One thing that is really important in our environment is support for  
LOTS of imap folders - it's not uncommon for folks to have  
collections with hundreds of folders. That implies not doing things  
like scanning all of the folders for new messages, but allowing the  
user to specify which folders she wants scanned.

I'm not sure I understand what  "Chandler does NOT replace your  
existing email client for reading and writing emails" means - is that  
merely a "what can we realistically get done in a 1.0 release", or a  
statement of long-term direction? I believe that our constituencies  
are looking to specifically replace their existing email client with  
an integrated client that does all the good things mentioned in the  
first bullet point along with email.

Cheers -

- Oren

On Jan 23, 2006, at 4:47 PM, Mimi Yin wrote:

> http://wiki.osafoundation.org/bin/view/Journal/EmailDiscussion20060120
>
> Here are notes from an ad-hoc design meeting last week on *options*  
> for our high-level strategy for email in Chandler 1.0.
>
> + How will people use email in Chandler?
> + What scenarios will it be useful for?
> + What workflows will we support?
>
> Mimi
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design