Re: *ping*

[Russ Allbery <rra@stanford.edu>]

Joseph S D Yao <jsdy@tux.org> writes:

> Elm 2.4*something with MIME/PGP patches shows the year as "100".  2.5.2
> doesn't have this bug.  Nor can I find the MIME/PGP patches for it.  But
> the fixes are retroportable and obvious.

We've had a report that INN is accepting and propagating messages with a
Date header showing a year of 1900.  Whether or not this is a Y2K bug is
somewhat arguable; my personal inclination is that the chances are high
enough that such a message was actually sent in 2000 by a broken
newsreader that accepting it may just be being generous in what one
accepts.  But it does potentially do slightly weird things in newsreaders
sorting by date.

Other than that and elm, the only other problems we've run into are failed
timestamps in a very old version of UMich slapd (LDAP server) that we plan
on retiring soon anyway and some problems with replication on our current
Netscape LDAP servers due to root certs expiring (not a Y2K bug, but a Y2K
related issue).

Note for people who set expiration dates:  January 1st is really not a
good time to set the expiration for, even if it appeals to someone's sense
of aesthetics, since it's right after a very long holiday and therefore
advance warning has to be considerably more advanced than normal.  Please
consider March or May or September or some other date instead.

-- 
Russ Allbery (rra@stanford.edu)         <URL:http://www.eyrie.org/~eagle/>