SEEMail - Vendors
You are viewing an ARCHIVED page.
Introduction
Vendors and their products, go through a formal process, to ensure interoperability with existing SEEMail systems. This vendor/product accreditation process is described in detail in the SEEMail Product/Supplier Accreditation Process. The basic steps are:
- Vendor Accreditation: Vendor proves they are reputable, by
providing information about capability and experience.
- Interim Product Accreditation. Vendor configures a test
environment, then proves it meets the SEEMail Business Requirements, by
performing a set of send/receive tests against the SEEMail Automated
Reference Test Server (SMARTS).
- Full Product Accreditation / Interim Site Certification.
Vendor configures 1st customer environment, then proves it meets
SEEMail Business Requirements, by repeating a sub-set of the
previous send/receive tests against SMARTS.
- Full Site Certification. Vendor/Customer successfully
establishes links / exchanges messages with other SEEMail Participating
agencies, to the satisfaction of the SEEMail Manager.
Key Documents
- SEEMail: Definitions Version 1.1: This document contains the definitions for terms used in SEEMail.
- SEEMail Business Requirements Version 2.2: This document describes the business requirements that a gateway must meet, to be able to exchange, block and report upon messages sent between SEEMail Participating Agencies.
- SEEMail: Accreditation Process Version 2.1: This document describes the process for Accreditation of Vendors and Software, for SEEMail.
- SEEMail: Site Certification Process for Eligible / Participating Agencies Version 1.1: This document describes the process for SEEMail Site Certification, required to demonstrate a gateway is able to exchange, block and report upon messages sent between SEEMail Participating Agencies.
- SEEMail: Tests Version 2.3
This document describes the SEEMail tests necessary for site certification and party/product accreditation. It is available in rich text (RTF) and PDF formats only.
Accredited vendors
SEEMail has recently undergone transition to Version 2, therefore the list below shows vendors in several categories. New vendors/products are welcomed.
For further information, contact the SEEMail Manager.
Version 2 fully accredited vendors:
- Gen-i, using Marshal Software's MailMarshal Secure v5.5.5.6 with Gen-i SEEMail Extensions 1.0
- Liverton Software, using Marshal Software's MailMarshal Secure v5.5.6.6.
- Scientific Software and Systems Ltd, using Clearswift's MAILsweeper and SSS's SecureIT v1.0.
- In addition, the following agencies offer SEEMail Version 2 to
their customers through arrangements to use the Liverton accredited
configuration:
- Datacom Systems Ltd offers a bureau SEEMail service, for agencies that do not wish or are not in a position to manage their own email services in-house.
- Network Pro
Version 2 interimly accredited vendors:
- Telecom Advanced Solutions, using MailMarshal Secure 5.5.4.16 with Safecom Extension.
- Optimation Ltd, using Open Source based "SSI SEEMail Server Version 2.1".
Frequently Asked Questions
Why does SEEMail have to accredit vendors ?
The E-government Unit of the State Services Commission accredits secure e-mail gateway products and suppliers of those products, to ensure interoperability with the existing SEEMail system.
What does accreditation mean ?
Accreditation means the product has completed acceptance testing in an operational site, and has successfully passed interoperability testing for secure e-mail gateway products for the Secure Electronic Environment (S.E.E.).
Accreditation does not in any way whatsoever warrant the suitability or performance of the Accredited Software for any purpose and neither the Crown, nor the State Services Commissioner or his representative accept any liability from any Supplier, Participating Agency, Eligible Agency or any other party whatsoever for any cost, damage or loss arising from purchase or use of this software.
Can a non-accredited vendor sell Accredited Software ?
No. The vendor must be accredited. It is possible for an accredited vendor to sub-contract some aspect of their role, but the customer/vendor contract and hence the accountability/liability will remain with the accredited vendor. (14 June 2001).
Can a government agency do their own thing?
Yes. Various government agencies have developed an open source version. These agencies have to undergo a similar product accreditation process as the vendors, to ensure interoperability.

