We have entirely renewed the eEvidence’s registration process for a more straightforward sign-up. Take a look at https://secure.eevid.com/register. With the previous approach, new users couldn’t directly sign up for an eEvidence+ premium license; it was required to sign up first for a free eEvidence Basic license and, once confirmed, to upgrade to an eEvidence+ license […]

At 13:34h GMT +1, December 23rd, the FNMT communication problem, which prevented us from retrieving the TSA timestamps for digitally signing some eEvid.Certs, has ben corrected. Immediately after, we have resumed the signing process, sealing and delivering users all pending eEvid.Certs. Around 13:57h GMT +1, December 23rd, we have finished this process and closed the […]

We are sorry to inform you that we have an open case with the Time Stamp Authority (TSA), which is preventing us from applying the timestamp on the eEvid.Cert signature. This problem only affects the signature of the eEvid.Certs for the free eEvidence Basic and eEvidence+ Unlimited licenses. The eEvid.Certs for eEvidence+ Archive and eEvidence+ […]

Some new users have reported problems when sending eEvids from Gmail and Yahoo. When trying to do so, they receive a postmaster error message. This error is caused by eEvidence, not Gmail nor Yahoo. We are aware of it and working to sort it out as soon as possible. Thank you for your patience. If […]

For a few hours, the link to archived files was missing from eEvid History. due to a wrong path to the file system. The error has been fixed. If you are interested in starting to to communicate with greater guarantees and you are a professional, particular and/or small company, do not hesitate to consult the […]

We have detected that, in certain circumstances, the eEvid limit for the eEvidence Basic and Archive licenses was ignored. Those of you who have gone above the limit, don’t worry: all eEvids are perfectly valid. If you are interested in starting to to communicate with greater guarantees and you are a professional, particular and/or small […]

When you send a eEvid from Yahoo! by manually typing the address with the “.eevid.com” wildcard, Yahoo! will include the recipient’s address as the recipient’s name on the email header. Something like this: To john@example.com.eevid.com <john@example.com.eevid.com> This causes a strange effect: although eEvidence removes the wildcard for every RCPT (recipient), recipients will see their address […]