notes from mail meeting

ChaoLam, HeikkiToivonen, MimiYin, MorgenSagen, AparnaKadakia, BrianKirsch, DonnDenman

• Creating a new communications item from a menu needs to select the "all" collection (the new item needs to be in the selected collection)
• An "out" mail may actually be in several different states
  • Draft: not yet sent
  • Queued: trying to send
  • Sent: successfully sent
  • Failed: some error happened trying to send (may be a separate flag, may go back to draft state)
• Morgen pointed out there are 3 classes of errors
  • Errors recognized immediately (no email address in the to: field)
  • Errors recognized in a few minutes (email address doesn't exist at the server)
  • Errors recognized days later (the server never responds)
• Content model needs to capture errors
  • Perhaps multiple errors per item
  • Do we create a notification for the error? No: the item itself (status, or error added to a list of errors, or however the content model handles it) is flagged such that it shows up in the dashboard view.
• How to model me?
• A bit complicated handling sending an item to yourself
• Use case: you send several items to someone
  • interacting with vanilla imap client, would be odd to get 7 different emails
  • perhaps you need to create a collection and mail/share that collection
• Aparna will come up with 4 test cases to represent .4 goals for sending
  • 3 error cases + one success case
• Morgen will help Brian with the content model (enough for .4 goals)
• Use case: sort by "explicit" order (not necessarily the date shown in the "date" column in the summary view)

-- KatieCappsParlante - 05 Aug 2004