OK. So, `date` is extracted from the email's `Date` header, which is set by the sender and so could be anything (a lot of spammers set this way in the future so that if your client orders on this, their spam will sit at the top of your inbox forever). However, `date_received` (or our `received_at` method) is pulled out of the email's `Received` headers, which are inserted at each node in the message's travel across the internet. So the most recent one should be the one inserted by the receiving server as the message came in. So it's a lot more trust-worthy.

I'm not sure how much explanation of email concepts vs Context.io API concepts vs. gem-specific concepts we want to do in cases like this. Ideally, I'd like to avoid duplicating stuff covered in the main API docs and point people to them. But this one is almost even a layer one more deep than that. What do you think on this topic?