Hi Steffen! On 2022-07-28T17:15:02TAI, Steffen Nurpmeso wrote: > |when I send an email with /bin/mail at 2022-07-28T04:48:54+00:00:37, > |then s-mailx writes: > |Date: Thu, 28 Jul 2022 04:48:54 +0000 > > And what did you expect? > exim would convert the timestamp to UTC and write "Date: Thu, 28 Jul 2022 04:48:17 +0000"...
> What is it that i should fix? > I would find it cool, if s-mailx could detect that situation itself. But of course I can use my wrapper script, too... The question is, if s-mailx should mention, that it cannot produce an RFC5322-compliant timestamp in the TAI zone. > If it is that you want some standard to include CLOCK_TAI, oh yes, > that i would love to see myself. Much better than fiddling around > with the link of civil time to solar time. But CLOCK_TAI is not > that widely supported, nor are the mechanisms in the kernel > everywhere. :( > We do not need CLOCK_TAI... I think my zoneinfo file makes fiddling around with 61-second long minutes unnecessary, because: There are no such minutes in TAI zone... Bye Arne