[LEAPSECS] Greetings from an intercalary second

[Tom Van Baak]

Line 55 of my raw headers has your leap second:

00001 Return-Path: <leapsecs-bounces at leapsecond.com>
00002 Delivered-To: tvb-leapsecond:com-tvb at leapsecond.com
00003 X-Envelope-To: tvb at leapsecond.com
00004 Received: (qmail 73506 invoked from network); 1 Jan 2017 00:00:09 -0000
...
00049  for <leapsecs at leapsecond.com>; Sat, 31 Dec 2016 19:00:05 -0500 (EST)
00050 Received: from shellx.eskimo.com (shellx.eskimo.com [204.122.16.2])
00051  by mail.eskimo.com (Postfix) with ESMTP id BF13B22D3;
00052  Sat, 31 Dec 2016 16:00:03 -0800 (PST)
00053 Received: by shellx.eskimo.com (Postfix, from userid 10926)
00054  id B432739F7; Sat, 31 Dec 2016 16:00:03 -0800 (PST)
00055 Date: Sat, 31 Dec 2016 18:59:60 -0500
00056 From: scs+ls at eskimo.com (Steve Summit)
00057 To: leapsecs at leapsecond.com
00058 Message-Id: <20170101000003.B432739F7 at shellx.eskimo.com>
00059 X-Virus-Scanned: clamav-milter 0.99.2 at mail.eskimo.com
00060 X-Virus-Status: Clean
00061 Subject: [LEAPSECS] Greetings from an intercalary second
...
00078 Sender: "LEAPSECS" <leapsecs-bounces at leapsecond.com>
00079 
00080 Some readers may be interested in the Date: line on this message.
00081 It is not faked: it was added by a lightly-modified sendmail
00082 program running under a Linux kernel keeping true UTC, with the
00083 timestamp fetched via clock_gettime(CLOCK_UTC) and formatted
00084 using a timespec-aware version of localtime().
00085 
00086 I don't claim that the code behind this demonstration solves every
00087 leapsecond-related difficulty (far from it!), but it's a start.
00088 _______________________________________________
00089 LEAPSECS mailing list
00090 LEAPSECS at leapsecond.com
00091 https://pairlist6.pair.net/mailman/listinfo/leapsecs

/tvb

----- Original Message ----- 
From: "Steve Summit" <scs+ls at eskimo.com>
To: <leapsecs at leapsecond.com>
Sent: Saturday, December 31, 2016 3:59 PM
Subject: [LEAPSECS] Greetings from an intercalary second


> Some readers may be interested in the Date: line on this message.
> It is not faked: it was added by a lightly-modified sendmail
> program running under a Linux kernel keeping true UTC, with the
> timestamp fetched via clock_gettime(CLOCK_UTC) and formatted
> using a timespec-aware version of localtime().
> 
> I don't claim that the code behind this demonstration solves every
> leapsecond-related difficulty (far from it!), but it's a start.
> _______________________________________________
> LEAPSECS mailing list
> LEAPSECS at leapsecond.com
> https://pairlist6.pair.net/mailman/listinfo/leapsecs