3 Feb
2000
3 Feb
'00
4:30 a.m.
Marvin <marvin(a)rain.org> writes:
I tolerate, but do not even slightly like, the fact
that the dates that come
in are dependent on the senders time/date stamp. Putting a realistic time
stamp on a message is certainly not forging anything. Currently, messages
come in all over the place (with regard to time/date order). Is this good? I
think not!
It's the principle of least munging of headers again; it's considered bad
form to modify the Date: header supplied by the sender. If possible, set
your software to display and sort on the timestamp in the received header as
seen here (from your posting):
Received: (from majordom@localhost)
by opal.tseinc.com (8.9.3/8.9.3) id LAA30204
for classiccmp-classiccmp-org-outgoing; Thu, 3 Feb 2000 11:23:20 -0600 (CST)
(envelope-from owner-classiccmp(a)classiccmp.org)
It's a bit tricky since there's more than one Received: header, but if
you use the one that says "for classiccmp-classiccmp-org-outgoing", that's
the most likely to get you accurate ordering (since everyone else's clocks
don't necessarily match) and a consistent time zone.