On Tue, 23 Aug 2005 17:18:15 EDT, Tim Casten said:
> I don't disagree with you entirely Paul.  However, LSOFT is adding to the bad
> Date and time header by incorrectly replacing the time stamp sith 6 zero's
> 00:00:00  i take it because blackberry sends out the cap GMT with their
> timestamp.  However in looking at headers from a blackberry the correct time is
> also included.

And you *know* the blackberry time is correct, how, exactly? Explain in detail,
*without* saying "we can hack around it because we know it's a Blackberry..."

The software can't even get the *format* right, why should we trust its value?
Do you have a good algorithm *other* than the pseudo-code

        if (timezone_format == dain-bramaged-brack-belly)
        then fixup_blackberry_damage
        else if....

The only other option that Listserv has besides forcing a "odd enough to be
noticed" value is to set the Date: to Listserv's current concept of the time,
which is a disaster waiting to happen - if you smash in a odd time, people
will notice and allow for that.  You stick in the current time, and people
won't notice - until "When did he know and when did he reply?" becomes important,
at which point a plausible-but-wrong value can cause much harm....