The Challenge

Q. Would it be possible to devise a method to supply unquestionable evidence of the contents and delivery of an email, without calling the recipient for action?

A. You bet.

We're proud about the milestone achieved by eEvidence in providing the Internet Community with a simple, yet effective, way to award global probative value to emails and digital files.

How we do it

Our role is pretty simple. We get your email, we register its contents and delivery and we issue the evidence receipt that proves who sent what, to whom and when.

The 3 pieces of the eEvidence Method

Proof of content

Delivery acceptance

Immutable evidence

We use cryptographic hash functions to obtain digital footprints from the original email and from each attachment.

Since it is infeasible to find two different files with the same hash, registering a hash equals registering the file from which the hash has been obtained.

When delivering the email to the recipient's mail server, we record all relevant data from the transmission.

This includes the standard response code returned by the recipient's mail server acknowledging that the email has been accepted for delivery.

Finally, we issue an evidence receipt that binds together a full copy of the original email, the associated hashes and the transmission details.

By electronically signing the evidence receipt, the immutability of the data it contains is sealed forever.

We register emails, so send us emails

We secure unquestionable evidence of what has been sent and accepted by other party

As long as you ask us to register emails, we can do the magic.

Back in the 70s, 20th Century, the smart guys that worked out the Internet wanted a simple way to exchange messages electronically. They defined the so-called Simple Mail Transfer Protocol, setting the most universal means of electronic communication of all times. Since then trillions of emails have been exchanged all over the world by means of devices that talk SMTP. So do we.

Internet standards offer you several ways to forward your emails through us, no matter what email system or program you use. Once you get it to us, we do what any mail server does when delivering emails to the intended recipients: we reach the recipient's mail server by following DNS standards and we deliver the email through a regular SMTP transmission.

The recipient will receive just that, a regular email from you, with no indication whatsoever about the registration proces.

Mail servers usually keep logs of the emails they process. Meant for system administration, however, such logs do not include information about what the email contains and become useless when in need to provide details on what was actually transmitted.

This leaves the available evidence to what the sender and the recipient may have kept. At this point, questioning the email authenticity, or even denying the transmission, becomes a case of your word against mine.

This is where the eEvidence method comes into play, by building an immutable digital record of the email contents and delivery through a unique combination of Internet and cryptography standards.

No need for the recipient to intervene or know about it

It is not possible to prove that an email has been read by the recipient —for the same reason you cannot prove that someone has read a certified regular letter. What the SMTP protocol provides, however, is an indisputable way to confirm whether the email has been accepted by the recipient's mail server. If accepted, it is his responsibility to forward the email to the recipient.

With no control over how will the recipient's mail server handle it, pretending to prove more than just having delivered the email is pointless. This is why we don't require the recipient to intervene; and if you don' tell him about it, neither will we.

Don't miss the FAQs section for more details about our email registration approach, tips on how to better use the product and resources for troubleshooting common issues.