Certified email

Description

A certified email can only be sent using a special Certified Email Account provided by a registered provider. When a certified email is sent, the sender's provider will release a receipt of the successful (or failed) transaction. This receipt has legal value and it includes precise information about the time the certified email was sent. Similarly, the receiver's provider will deliver the message in the appropriate certified email account and will then release to the sender a receipt of successful (or failed) delivery, indicating on this receipt the exact time of delivery. If either of these two receipts are lost by the sender, providers are required to issue a proof of transaction with equal legal validity, if this proof is requested within 30 months of delivery.

In terms of user experience, a certified email account is very similar to a normal email account. The only additional features are the receipts, received as attachments, providing details and timestamps for all transactions. A certified email account can only handle certified email and cannot be used to send regular email.

Technical process

The development of this email service has conceptual variations that are dominated by two-party scenarios with only one sender and one receiver as well as a trusted third party (TTP) serving as a mediator. As in traditional registered mail, many certified email technologies call for the parties involved to trust the TTP, or the "postman", because it has the capacity to reveal the identity of the sender to the recipient once the protocol is initiated. There are, however, some applications based on multi-party email protocols; these include the technology originally proposed by Markowitch and Kremer, that involves an online or offline TTP in addition to the sender and receiver. There is also a multi-party version, wherein a user can send the same email to multiple recipients. In this system, those who acknowledge the receipt are able to view the data. Some applications also offer add-in features, such as the integration of the concept of timeliness, wherein a participant to the process can terminate a session in finite time in order to avoid waiting for a reply forever.

The mediation of a trusted third party (TTP) requires both parties, the sender and the recipient, to come to terms in approving who will be the mediator. In compliance scenarios, where a regulation may simply require a party to deliver a notice to a given recipient and be able to prove having done so (i.e. GDPR), the role of a TTP can be trusted to an electronic registered delivery service capable to secure timestamped evidence of the contents and delivery of the electronic message, without the recipient's intervention.

Certified email in Italy

The Italian certified email (Posta elettronica certificata, PEC) was established in 2005 and it uses protocols described in the RFC 6109 (Request for Comments 6109), which was drafted in order to make the protocols public to the Internet community.

Since July 1 of 2013, all communications between enterprises and the Italian public administration are required to be sent through PEC and paper documents are no longer accepted.

All matters concerning PEC in Italy are supervised and regulated by a special government agency called AgID ("Agenzia per l'Italia digitale") which determines the authorized certified email providers, the legal framework of PEC and the rules and terms of use.

Anyone may register a PEC address through a certified provider or reseller.

Starting from 2022, Italy is migrating from PEC to an EIDAS-compliant protocol, called Registered Electronic Mail. The switch over to the new protocol is being led by Roberto Reale and Alessandra Antolini on behalf of AgID.

Certified email in UE

It's called REM (registered email) and has different provider here listed in the table.

References

References

1. "Posta elettronica certificata – PEC". Italian government.
2. "IncaMail".
3. "GovHK: Electronic Authentication & Digital Certificates".
4. "De-Mail – einfach verschlüsselt und nachweisbar".
5. (9 March 2018). "Il futuro della PEC: Armonizzazione e riconoscimento in Europa - Diritto informatico: Notizie e guide".
6. (24 May 2017). "La Posta Elettronica Certificata verso le regole europee".
7. (2005). "Applied Public Key Infrastructure: 4th International Workshop: IWAP 2005". IOS Press.
8. (2004). "Information and Communications Security: 6th International Conference, ICICS 2004, Malaga, Spain, October 27-29, 2004. Proceedings". Springer.
9. (2005). "Information and Communications Security: 7th International Conference, ICICS 2005, Beijing, China, December 10-13, 2005, Proceedings". Springer Science & Business Media.
10. Carlos Tico (2012). ''Method, a system and a computer program product for certifying that a destination email server has received an email message sent from a sender to at least one destination address.'' [https://patents.google.com/patent/US9742722B2/en?oq=9%2c742%2c722 US Patent 9,742,722 B2] (2017) and [https://patents.google.com/patent/EP2805455B1/en?oq=EP2805455B1 EP2805455B1] (2018).
11. (2005-02-11). "Decreto del Presidente della Repubblica 11 febbraio 2005, n. 68".
12. "Posta elettronica certificata". Italian government.
13. "REM SERVICES - Criteri di adozione standard ETSI - Policy IT".
14. https://eidas.ec.europa.eu/efda/trust-services/browse/eidas/tls/search/type?step=3&searchCriteria=eyJzZXJ2aWNlU2NvcGUiOiJFWENMVURFX0lOQUNUSVZFIiwiY291bnRyeUNvZGVzIjpbIkFUIiwiQkUiLCJCRyIsIkhSIiwiQ1kiLCJDWiIsIkRLIiwiRUUiLCJGSSIsIkZSIiwiREUiLCJFTCIsIkhVIiwiSVMiLCJJRSIsIklUIiwiTFYiLCJMSSIsIkxUIiwiTFUiLCJNVCIsIk5MIiwiTk8iLCJQTCIsIlBUIiwiUk8iLCJTSyIsIlNJIiwiRVMiLCJTRSIsIlVLIl0sInNlcnZpY2VMZWdhbFR5cGVzIjpbIlFfRVJEUyJdfQ%3D%3D