Currently its 10.50am 28th of January here, my emails are stamped with local time, i have had trouble with servers saying thing are dated in the future, never had one tell me my emails have been posted after the actual date tho. So your email date stamp should have been the 22 of jan not the 24th, if it stamped your server time. Im sure you can find a logical explanation for it tho.
I know young people take things for granted these days, but having an email sit in a sendmail queue for a day or two isn't unheard of, nor the end of the world. Sure, it might have been sent on the 22nd, and your upstream MTA might have even accepted it then... but there's no guarentee that ALL the MTA's between you and Samson will all be connected and functional. Considering just how many of them are Microsoft exchange servers, I'm amazed email works at all.
However, even assuming the mail really did arrive at its destination on the 22nd, why would a mere 3 days be so troubling to you? Was the codebase going to crumble away in 72 hours unless someone touched it? Did someone go announce it on slashdot and you worried about a huge inrush of downloaders? Was Vinny the loanshark going to stop by and break kneecaps if that codebase wasn't in your hands by Friday afternoon?
In the real world, I can talk to people on the phone and they'll assure me something will get done right away, and that it should be resolved before the close of the business day. In reality, this means an internal memo or email will get sent to someone and it will be plunked onto someone's desk before the close of the business day -- and if that someone already has a big pile of papers, or is out sick, or is in a bad mood... you can bet it won't get touched until tomorrow at the earliest.
In short, unless it's going to cost me money or threaten my health, I don't get upset until a week goes by and I hear nothing. Anything else would just lead to a constant state of exasperation.
In any case, the point is now moot. Moving along...