That one email? Honestly, never saw it!

When you send an email, you trust that it will be delivered properly. If the message unexpectedly fails to reach the intended recipient, how do you find out? Whether or not (important) business emails were received can sometimes lead to disputes. What can you do in such a case?
Taking it on trust
Almost everyone takes it for granted that an email arrives safely almost immediately after it is sent. Yet there are many obstacles that can stop emails from arriving. Not every sender knows how to check this. You can, for example, request a delivery or read receipt, but in many cases these requests are not honoured. So it is often a gamble.
Non Delivery Reports
Fortunately, there is a mechanism that notifies the sender when a delivery attempt fails. If an email cannot be delivered, a so-called Non Delivery Report (NDR) is generated. You receive this so-called bounce in your inbox, and you usually know almost immediately. Unfortunately, NDRs don’t always find their way to the intended recipient either; they get delayed or are thrown away unseen. And what do you do if the email was delivered, but the recipient then claims never to have received it?
Traceability
By making the handling of email transparent, you can prove whether or not an email was ‘lost’. Onlinespamfilter customers have this solution at their fingertips as standard when they log in to the portal and look at the mail history. When an email passes through Onlinespamfilter, a unique ID is generated for it. All the important information is then linked to this ID, including the route the email took through the data centre, and when and to whom it was delivered. So from the moment it is sent, the route an email takes can be traced precisely. We keep this important information about each individual email for two weeks.
Disputes
This can come in very handy: say you have sent an important business email, but when you ask, the receiving party says they received nothing. If you happened not to receive the NDR, and therefore assume the email arrived, this could easily lead to an awkward situation. In these cases, the information from the email’s unique ID comes in handy. You can check what went wrong within the system and whether or not the email arrived. If the other party really didn’t receive the email, you can use the unique ID and the related server information to show that you did at least send it. This is often enough to prevent any unpleasant discussions.
Conclusion
Although the email protocol has good ways to guarantee that email arrives, or at least to notify the sender of a failed delivery, not every party has implemented this mechanism correctly. A trace of the email can then often show ‘after the fact’ at least where things went wrong, and possibly give pointers to where improvements can be made!
