Please don't take this list as the literal truth. See StandardDisclaimer for more details.
feature | osaf release | Notes |
_Organizing Messages_ |
Summary view displaying key email attributes. Attributes can customized and edited (as with other capplets) | Canoga | |
How do we show messages threads and "thrasks"? | Canoga | Design Issue |
How do we group messages into virtual "folders"? | Canoga | Design Issue |
How do we search for messages? | Canoga | General Design Issue |
How do we filter/categorize messages? | Canoga | General Design Issue |
How do we archive messages? | Canoga 1.x | Debatable Feature, General Design Issue |
_Receiving Messages_ |
POP protocol support | Canoga | |
IMAP protocol support | Canoga | |
How do we deal with IntrinsicIMAPIssues? | Canoga | Design issue |
Support for SSL/TLS | Canoga | |
Support for SASL authentication | Canoga | |
Multiple account support | Canoga | Tier-2 Design issue |
Manual and automatic message retrieval | Canoga | |
Low-bandwidth user support (e.g. download partial message or header only) | Canoga 1.X | Debatable Feature, Tier-2 issue |
Support for audio and system notifications | Canoga | |
Auto re-wrap long-lines | Canoga 1.x | Debatable feature, Tier-2 Design Issue |
Do we want to (and how?) support intelligent notification (e.g. no notification of junk email)? | Canoga 1.x | Debatable Feature, Tier-2 issue |
_Reading Messages_ |
Form-based view showing message body and key email attributes | Canoga | |
Show quoted message body appropriately | Canoga | Debatable, Tier-2 |
Chracter encodings: what character encoding do we support? | Canoga 1.X | General Design Issue (I18N plan) |
Recognizer support: "live" URLs | Canoga | |
Switch message to plain text | Canoga | Debatable Feature |
Print message | Canoga | |
Attachments: inline support for HTML, plain text, images | Canoga | |
Attachments: open with helper application for other MIME types | Canoga | |
Attachments: allow saving and deletion | Canoga | |
Do we support other recognizers? | Canoga 1.x | Design Issue, Debatable Feature |
_Addressing messages_ |
To, CC, BCC addressing | Canoga | |
Switch persons/accounts on-the-fly | Canoga | Tier-2 issue |
Auto-completion of addresses | Canoga | Design-issue (tier-2?) |
Well-integrated to contacts capplet | Canoga | Design issue (tier-2?) |
_Authoring_ |
Support for plain text and HTML subset | Canoga | |
What exact subset do we include (e.g. tables?)? | Canoga | Tier-2 issue |
Switch between HTML and plain-text on-the-fly | Canoga | |
Allow user to add/substract quote level | Canoga | Debatable feature |
Inline spell-checking | Canoga | |
Auto-categorize as draft and auto-save unsent messages | Canoga | |
Support for templates and stationery | Canoga 1.x | Debatable feature |
Support for signatures | Canoga 1.x | Debatable feature |
_Replying_ |
Support for reply-to-sender and reply-to-all | Canoga | |
Support for reply-to-list | Canoga 1.x | Debatable feature, Tier-2 issue |
Quote original message with auto-citing | Canoga | Tier-2 issue |
_Sending Messages_ |
Support for SMTP servers including authentication & SSL | Canoga | |
Support for multiple accounts | Canoga | |
Support sending standard MIME attachments | Canoga | |
Support for forwarding and resending of message | Canoga | |
How do we support sending Chandler "items" and views as attachments? | Canoga | Design Issue |
_Attachments_ |
How do we support attachments as first-class items? | Canoga | Design issue |
_Import/Export_ |
Support for mbox format | Canoga | |
? What else? | Canoga | Ecosystem issue |
_Security_ |
What email and HTML features do we allow to be turned off for security reasons? | Canoga | Security issue |
_Offline support_ |
Allow caching of IMAP messages locally | Canoga | Tier-2 issue |
Automatically sync with IMAP when online (see IntrinsicIMAPIssues) | Canoga | Design Issue |
Queue outgoing messages and automatically send when online | Canoga | |
Track deletes and other transactions offline | Canoga | |
Give appropriate but not overwhelming warning when network unavailable | Canoga | |
_Interactions w/other capplets & rest of Chandler_ |
Will email be used as a transport for non-end-user communication (e.g. web services and other RPC mechanisms)? If so what are the end-user design issues? | Canoga 1.x | Debatable Feature, Architecture & Design issue |
TBD |
Multiple account support is listed as Tier-2 for receiving and addressing but it's listed as a Canoga feature for sending - my worry is that without storing the original account during the receive the user will have to remember what account was used so the composition using the proper outgoing account.