en 1.6 Messaging and collaboration 1.0

Generic criteria from QSOS version 1.6 Intrinsic durability Maturity less than 3 months if between 3 months and 3 years after 3 years Unstable software with numerous releases or patches generating side effects Stabilized production release existing but old. Difficulties to stabilize development releases Stabilized software. Releases provide bug fixes corrections but mainly new functionalities Software knows several problems which can be prohibitive No know major problem or crisis History of good management of crisis situations Software is very likely to be forked in the future Software comes from a fork but has very few chances of being forked in the future Software has very little chance of being forked. It does not come from a fork either Adoption by community and industry Very few users identified Detectable use on Internet Numerous users, numerous references None Few refences, non critical usages Often implemented for critical applications No community or without real activity (forum, mailing list, ...) Existing community with a notable activity Strong community: big activity on forums, numerous contributors and advocates No book about the software Less than 5 books about the software are available More than 5 books about software are available, in several languages Organisation and leadership of developments 1 to 2 individuals involved, not clearly identified Between 2 and 5 independent people More than 5 people Complete dictatorship Enlightened despotism Council of architects with identified leader (e.g: KDE) Activity of the project and around the software Less than 3 developers, not clearly identified Between 4 and 7 developers, or more unidentified developers with important turnover More than 7 developers, very stable team Slow reactivity in forum or on mailing list, or nothing regarding bug fixes in releases note Detectable activity but without process clearly exposed, long reaction/resolution time Strong reactivity based on roles and tasks assignment No or few new functionalities Evolution of the product driven by the core team or by user's request without any clearly explained process Tool(s) to manage feature requests, strong interaction with roadmap Very weak activity on both production and development releases Activity on production and development releases. Frequent minor releases (bug fixes) Important activity with frequent minor releases (bugs fixes) and planned major releases relating to the roadmap forcast Industrialization level of the project Developments realized at 100% by employees of a single company 60% maximum 20% maximum Services offering No offer of training identified Offer exists but is restricted geographically and to one language or is provided by a single contractor Rich offers provided by several contractors, in several languages and split into modules of gradual levels No offer of support except via public forums and mailing lists Offer exists but is provided by a single contractor without strong commitment quality of services Multiple service providers with strong commitment (e.g: guaranteed resolution time) No offer of consulting service Offer exists but is restricted geographically and to one language or is provided by a single contractor Consulting services provided by different contractors in several languages No user documentation Documentation exists but shifted in time, is restricted to one language or is poorly detailed Documentation always up to date, translated and possibly adapted to different target readers (end user, sysadmin, manager, ...) Quality assurance process No QA process Identifies QA process but not much formalized and with no tool Automatic testing process included in code's life-cycle with publication of results No bug or feature request management tool Standard tools provided (for instance by a hosting forge) but poorly used Very active use of tools for roles/tasks allocation and progress monitoring Packaging for various operating systems Software can't be installed from source without lot of work Installation from source is limited and depends on very strict conditions (OS, arch, lib, ...) Installation from source is easy The software is not packaged for Debian A Debian package exists but it has important issues or it doesn't have official support The software is packaged in the distribution The software is not packaged for FreeBSD A port exists but it has important issues or it doesn't have official support A official port exists in FreeBSD The software is not packaged for HP-UX A package exists but it has important issues or it doesn't have official support A stable package is provided for HP-UX The software is not packaged for MacOSX A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution The software is not packaged for Mandriva A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution The software is not packaged for NetBSD A port exists but it has important issues or it doesn't have official support A official port exists in NetBSD The software is not packaged for OpenBSD A port exists but it has important issues or it doesn't have official support A official port exists in OpenBSD The software is not packaged for RedHat/Fedora A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution The software is not packaged for Solaris A package exists but it has important issues or it doesn't have official support (e.g: SunFreeware.com ) The software is supported by Sun for Solaris The software is not packaged for SuSE A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution The project can't be installed on Windows A package exists but it is limited or has important issues or just cover some specific Windows release (e.g: Windows2000 and WindowsXP) Windows is full supported and a package is provided Exploitability level Difficult to use, requires an in depth knowledge of the software functionality Austere and very technical ergonomics GUI including help functions and elaborated ergonomics No administrative or monitoring functionalities Existing, functionalities but incomplete and or need improvement Complete and easy-to-use administration and monitoring functionalities. Possible integration with external tools (e.g: SNMP, syslog, ...) Technical adaptability Monolithic software Presence of hight level modules allowing a first level of software adaptation Modular conception, allowing easy adaptation of the software by selecting or creating modules Everything by hand Recompilation possible but complex without any tools or documentation Recompilation with tools (e.g: make, ANT, ...) and documentation provided Any modification requires code recompilation Architecture designed for static extension but requires recompilation Principle of plugin, architecture designed for dynamic extension without recompilation Project's strategy License Very strict license, like GPL Moderate permissive license located between both extremes (GPL and BSD) dual-licensing depending on the type of user (person, company, ...) or their activities Very permissive like BSD or Apache licenses Very permissive like BSD or Apache licenses Moderate permissive license located between both extremes (GPL and BSD), dual-licensing depending on the type of user (person, company, ...) or their activies Very strict license, like GPL Rights held by a few individuals or entities, making it easier to change the license Rights held by numerous individuals owning the code in a homogeneous way, making relicense very difficult Rights held by a legal entity in whom the community trusts (e.g: FSF or ASF) No practical way to propose code modification Tools provided to access and modify code (like CVS or SVN) but not really used to develop the software The code modification process is well defined, exposed and respected, based on roles assignment No published roadmap Existing roadmap without planning Versionned roadmap, with planning and measure of delays Software has no sponsor, the core team is not paid Software has an unique sponsor who might determine its strategy Software is sponsored by industry No detectable strategy or strong dependency on one unique actor(person, company,sponsor) Strategic vision shared with several other free and open source projects but without strong commitment from copyrights owners Strong independence of the code team, legal entity holding rights, strong involvement in the standardization process

Supported web browsers for the webmail Does Internet Explorer support the webmail client ? Not covered Partially covered Fully covered Majoritairement Does Firefox support the webmail client ? Not covered Partially covered Fully covered Majoritairement Does Safari support the webmail client ? Not covered Partially covered Fully covered Non prioritaire Does Opera support the webmail client ? Not covered Partially covered Fully covered Non prioritaire List of necessary plung ins into the webmail Flash plug in is required/supported Flash plug in is not required/supported Flash plug in is optionnaly required/supported Flash plug in is required/supported Java plug in is required/supported Java plug in is not required/supported Java plug in is optionnaly required/supported Java plug in is required/supported ActiveX plug in is required/supported ActiveX plug in is not required/supported ActiveX plug in is optionnaly required/supported ActiveX plug in is required/supported Silverlight plug in is required/supported Silverlight plug in is not required/supported Silverlight plug in is optionnaly required/supported Silverlight plug in is required/supported Flex plug in is required/supported Flex plug in is not required/supported Flex plug in is optionnaly required/supported Flex plug in is required/supported Please annotate all other required/supported plug-ins for webmail/rich client compatibility For each mail client, please indicate if the solution provides native or emulated interface. Doest the server software provide a MAPI interface ? No MAPI interface provided Emulated MAPI interface, partial support of functionnalities Full MAPI support Doest the server software provide a Novell Evolution interface ? No Novell Evolution interface provided Emulated Novell Evolution interface, partial support of functionnalities Full Novell Evolution support Doest the server software provide a Mozilla Thunderbird/Sunbird interface ? No Thunderbird/Sunbird specific interface provided Emulated Thunderbird/Sunbird interface, partial support of functionnalities Full Thunderbird/Sunbird support Doest the server software provide a Apple Mail App. interface ? No Apple Mail App. interface provided Emulated Apple Mail App. interface, partial support of functionnalities Full Apple Mail App. support Please annotate all other rich client interface provided for messaging and collaboration (exluding regular protocols tools, such as POP/IMAP client) Supported mobile clients for the server software Does the server software provide Palm OS compatible interface ? Not covered Partially covered Fully covered Does the server software provide Windows Mobile/Pocket PC compatible interface ? Not covered Partially covered Fully covered Does the server software provide Symbian compatible interface ? Not covered Partially covered Fully covered Does the server software provide Blackberry BES compatible interface ? Not covered BES Comptaible interface Native BES interface Extra protocols that are supported on the server side ? Does the server software support Web – XHTML protocol ? Not covered Partially covered Fully support of Web – XHTML protocol Does the server software provide Web - CSS protocol ? Not covered Partially covered Fully compatible with CSS Does the server software provide a secure SMTP protocol support ? Not covered Partially covered Full Secure SMTP support Does the server software provide POP support ? Not covered Partially covered Full POP support Does the server software provide Secure POP support ? Not covered Partially covered Secure POP3 Fully covered Does the server software support IMAP protocol ? Not covered Partially covered IMAP4 fully covered Does the server software support Secure IMAP protocol ? Not covered Partially covered Secure IMAP4 fully covered Does the server software support iCal exchange protocol ? Not covered Partially covered iCalendar fully supported Does the server software support CalDAV interface ? Not covered Partially covered CalDAV Fully supported Does the server software support WebDAV interface ? Not covered Partially covered Webdav fully covered Does the server software provide a Samba like compatible interface ? Not covered Partially covered Samba fully covered Does the server software support an FTP interface ? Not covered Partially covered FTP fully covered Does the server software provide vCard interface (import/export/transfer) ? Not covered Partially covered Fully covered Does the server software support synchronization with external LDAP directories ? Not covered Partially covered Fully covered Does the server software support synchronization with external Active Directory directories ? Not covered Partially covered Fully covered SyncML - Synchronization of contacts, Calendar and (optional) email (push-email) ? Not covered Partially covered Fully covered

Installation is difficult, poorly documented or requires many patches Installation is tough but fair Installation is easy, well documented High granularity architecture (as many servers as there are sites) Adaptable Architecture (Centralization is an option) Monolithic architecture (all servers are located on the same site) No replication Partial replication or no duplication System of data replication No IMAP Migration Possible IMAP Migration Possible through specific development Migration tools are provided with software No possible migration from an IMAP solution conceivable Migration via third tools or specific development Migration and cover tools are provided, good functional cover Not covered Partially covered Fully covered Not present Cluster (load balancing or fail over) with weighing but without automatic return Resumption of service function when the principal node becomes available Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered

Pour un trafic email en pointe de 166 Mb/s pour 120.000 utilisateurs (hors protocole web), nous avons une bande passante consommée de 1,41 Kb/s More than 2 Kb/s Between 2 Kb/s and 5 Kb/s Less than 2 Kb/s Memory required on a per connected user basis, on the server side. 5 Mo and more Less than 5 Mo Less than 2 Mo On a Quadcore 32 bits server, 4Gb RAM Less than 5.000 users More than 5.000 users More than 10.000 users For a quadcore 32 bits, 4Go RAM, server - memory usage per server (if possible). Estimated User response time More than 100 ms between 50ms & 100 ms Less than 50 ms Not covered Partially covered Fully covered

Not covered Partially covered Fully covered Management of several languages and localization in server side Not covered Partially covered Fully covered The software entirely translated into French No available option Integration of the standard options of the Operating System Wide accessibility functions for blind peoples Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Possibility to extend managed objects with the solution Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered From the SOA point of view Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered

Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Pluggable Authentication Module (Sun) Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Client side and protocol encryption Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered La poste uses Open Trust. Additional details required (might require custom development) Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Fonction Disclaimer

Not covered Partially covered Fully covered Archives, Deletion,... Not covered Partially covered Fully covered Reroutage personnel, par groupe ou global. Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered mailbox folder of a mailbox Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered For example alert report

Not covered Partially covered Fully covered Storage methods and servers are supported Not covered Partially covered Fully covered Not covered Partially if architecture requirements Fully covered Not covered Partially covered Fully covered Storage methods and servers are supported Not covered Partially covered Fully covered Not covered Partially if architecture requirements Fully covered Not covered Partially covered Fully covered

Not covered Partially covered Fully covered Not covered Partially if architecture requirements Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Free time search (visual indicator of availibilities) Availibility proposal Not covered Partially covered Fully covered

Not covered Partially covered Fully covered Coherence of different tools or web browser components from the ergonomics point of view. Not covered Partially covered Fully covered General ergonomics of the web browser when viewing different functional objects Not covered Partially covered Fully covered Not covered Partially covered Fully covered Possibility to attach many documents (in one action) to a functional object ( message, calendar, meeting...) Not covered Partially covered Fully covered General ergonomics of the web browser when viewing different functional objects Not covered Partially covered Fully covered Possibility to store some URL related to objects in the favourite (of web browser of the client) Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Management of several languages and localization in client side Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered With filter dedinition Not covered Management of multiple signatures Fully covered Not covered Feeding virtual folders is done according to simple criteria Uses of regular expression to feed virtual folders on rules basis Not covered Partially covered Fully covered Not covered Complementary development to plan Available on the Web Not covered Export is limited on the perimeter Export of a message or message selection into file, including the attachments and the formatting Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered

Account creation is not possible from the client Account creation is possible for only part of the supported protocols Account creation is possivle for all supported protcols No accounts management interface provided by the client Link to a page dedicated to accounts managment for all or some of the supported protocals Native interface for editing/managing accounts It is not possible to delate accoubts from the client Link to a page from where you can delete accounts Native interface to delete accounts (without using a browser) no plug-in plug-in with limted functionnalities plug-in with adavanced functionalities 512 ko/s 128 ko/s 64 ko/s Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered none basic presence indicator presence indicator that can be customized None Basic Advanced (message can be customized ) Not covered Partially covered Fully covered When inmulti-account environment, possibility of using different presence indicators = 2 Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered telephone quality (8khz) FM quality (16 khz) HIFI quality (24 khz) Codecs formats are compatible with low bandwith and mobile networks Codecs formats are compatible with large bandwith network Codecs formats are compatible with broadband connection networks Not covered Partially covered Fully covered If the solution is only compatible with proprietary codes = 0 Support only point-to-point conference Possibility to make multipoint conferences using ad hoc infrastructure The dedicated infrastructure allows to make multipoint conferences Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered

The solution proposes differentiated access between participants and organizers Not covered Partially covered Fully covered Not covered Partially covered Fully covered The planned meetings are integrated in the participants electronic calendar Not covered Partially covered Fully covered The planned meetings are sent to participants as an invitation NO proprietary format Mpeg, avi etc.. Not covered Partially covered Fully covered Possibility to make open meetings without the necessity to log in form the participants Not covered Partially covered Fully covered Not covered Partially covered Fully covered Standard Formats (PPT, DOC, XLS, PDF, Images) Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered The solution supports automatic reconnection in case of lose connection Not covered Partially covered Fully covered Possibility to have a view on current meetings with their participants

Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Mailing lists management tools. The static mailing lists are enumerated Not covered Partially covered Fully covered Directory research made basis subscription or in the data bases Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered Not covered Partially covered Fully covered