| 1 | [[PageOutline]] |
| 2 | = Webmail Goals = |
| 3 | |
| 4 | At [wiki:support-team/2012-04-07 the recent support team meeting] we discussed our desired features and goals for webmail applications. |
| 5 | |
| 6 | This is an attempt to document them and compare them across different webapps. if a column for a webapp is empty, that means no one has verified it one way or the other. |
| 7 | |
| 8 | if a goal or desired feature isn't clear, it should be broken out into a separate subsection with an internal link for discussion. |
| 9 | |
| 10 | == feature comparison == |
| 11 | |
| 12 | ||= feature =||= squirrelmail =||= horde =||= roundcube =|| |
| 13 | || trivial login || || || || |
| 14 | || easy search || || || || |
| 15 | || faceted search || || || || |
| 16 | || HTTP→HTTPS/HSTS support || || || || |
| 17 | || cookies/js security audit || || || || |
| 18 | || trivial to add to addressbook from incoming mail || || || || |
| 19 | || address book accessibility across webmail apps || || || || |
| 20 | || displaying messages in threads || || || || |
| 21 | || generating messages with proper threading headers || || || || |
| 22 | || easy reply-to-list for mailing list messages || || || || |
| 23 | || calendar integration || || || || |
| 24 | || message tagging || || || || |
| 25 | || [#IMAPIntegration IMAP integration] || || || || |
| 26 | || [#DefaultFromAddress correct default "From" address] || || || || |
| 27 | || [#OutboundIdentityManagement outbound identity management] || || || || |
| 28 | || inbound filters/sieve || || || || |
| 29 | || anti-spam integration || || || || |
| 30 | || good user documentation || || || || |
| 31 | || good developer/plugin documentation || || || || |
| 32 | || aesthetically-pleasing || || || || |
| 33 | || if aesthetically-pleasing, themable? || || || || |
| 34 | || internationalization || || || || |
| 35 | || proper charset/MIME handling || || || || |
| 36 | |
| 37 | |
| 38 | == Goals == |
| 39 | |
| 40 | === IMAP Integration === |
| 41 | |
| 42 | Most webmail talks to an imap server on the backend. We need that since MF/PL uses IMAP to present our mail. |
| 43 | |
| 44 | If a webmail system applies tags to messages, it would also be nice to supply those message tags back to the IMAP server for integration somehow with other clients. |
| 45 | |
| 46 | === Default From Address === |
| 47 | |
| 48 | an MF/PL login should just use a simple name. But the webmail application needs to pick a legitimate "from" address for that member. (e.g. if they have their own domain name, they should use foo@example.org, instead of foo@example.mayfirst.org). |
| 49 | |
| 50 | === Outbound Identity Management === |
| 51 | |
| 52 | Members ought to be able to select from an array of outbound identities when composing a message. At a minimum, a member ought to be able to predefine a set of outbound identities they commonly use. Ideally, the set of outbound identities should be synchronized with the aliases that MF/PL knows will flow into their mailbox. |