Filed of mail

The solution of filed of mail doblenet allows him to strictly fulfill all the directives of retention of data, as much European (LSSI, LOPD level very high, normative CNMV) as international Americans/(Sarbanes-Oxley [SOX], DMCA, FOIA, etc)

 

General description

Our service offers so much in modality “payment by use” (SaaS) as in the form of appliances lodged in his own datacenters and they are interconnected with his systems of mail. In combination with our own technology of mail, virtualmbox, we can offer the most complete range of services of integrated and optimized form.

The solution is designed to appear as a mail servant, but is designed and optimized for the storage of long term mail: we were not satisfied only to storing great volumes of mail, but making practitioner the use of the filed information of daily form against the associated complexity have to reclaim the filed mail offline.

Search and categorisation

The e-mail keeps in a format strictly standardized so that the recovery is simple, at the same time as the storage of duplicated content is avoided. This way it is even made possible the search and categorisation of enormous amounts of mail in forms that could not be anticipated when the file was created for the first time. The following functionalities are possible:

  • Retention: to specify what messages will be due to eliminate or to retain, and when; specifying criteria even search/classification.
  • Views of mail: to create a mailbox that contains the messages that fulfill a certain consultation (criterion search) persistent.
  • Recovery (undelete): search of erased messages accidentally and to recover them.
  • Export of messages that some comply with certain criteria search/classification.

Filed stable and in the long term

In addition to being designed to manage enormous amounts of accumulated mail after years, filed of mail doblenet is oriented towards the future: since the canonical form only keeps from each mail in the base of messages --correcting any possible syntax error during the filed one--, the future programs of e-mail will be able to accede without problems to the stored messages. For example, a reader of mail in the 2020 will not need to be compatible bug-a-bug with a at the moment existing version of Outlook… nor will either be necessary to worry so that present designed messages to attack bugs can suppose threat some for future programs.

 

Our solution does not have predefined limits as far as the size or the use that occurs the filed one, and is only restricted by the capacity of the infrastructure that supports it. Still more, the configuration in cluster allows to bear to majors burdens transparently and without needing no of the “apaños” common to surpass limitations common such as the number or the size of the mailboxes to keep.

Interoperability and fulfillment of standards

Unlike other propietary and incompatible solutions, we put all the emphasis in the interoperability with other existing solutions; we strictly fulfill the standards of Internet mail, and --by means of a complete game of tests against implementations of clients and servers of mail of third parties-- we try to even operate correctly when there is bugs and other breaches of the standard in the other systems.

Our solution implements all the protocols excellent for the e-mail management, including IMAP4, POP3, smtp and Sieve (all of them with support TLS/SSL), along with a selection of extensions commonly used (such as “Lemonade” for the access to the mail in mobility)

 

Each and every one of the connected servers at the moment to Internet operate in hostile surroundings, and must count on protections in each level. Our filed solution of was designed from the first moment with security criteria, as much in terms of confidentiality of the filed mail as the capacity to resist diverse forms of attack.

In the version “payment by use”, the service is lent on our platform on watch superfluous and monitored constantly.

In the version “appliance”/“on premises”, the solution runs on a platform hardware and software of proven reliability and with an operating system especially protégé against intrusions.

 

 

We try that the work of the administrator/responsible for audits is easiest possible: the transparency and the diagnoses and messages of S-state concise and useful and the ample documentation and the variety of administration tools are complemented with. In addition, to procure itself that it is necessary a minimum intervention maintaining an appropriate behavior, consistent and predictable before a great variety of circumstances.

Example

We form a policy of reasonably complex retention: we wish to file all the mail during at least 6 months; The messages in the folder “file” will have to be kept during 5 years. The mail without reading in the shared folder /Usuarios will be preserved during 9 months.

  1. First, the general rules: to retain everything during 180 days (6 months); But all the kept mail will not erase after 9 months.
    > retain mail 180 > delete mail 270

    Therefore, the mail could be erased after 180 days. The erased messages (and not marked to file) past 9 months will not be erased in the next operation of purge.

  2. Now, the specific rules for “/Archivo”:
    > retain mail 1827 /Archivo

    (1827 days are 5 years, without worrying to us about leap years)

  3. The most complex rule is for /Usuarios:
    > retain mail 270 /users (not flag seen) and (not flag junk)

    (270 days nine months are, assuming that all were 30). Some clients of mail will use a “flag” different from junk, reason why it would be necessary to fit it.