Re: Strange future timestamp issue on some emails in KMail
Rodney Baker <[email protected]> Sun, 28 Jan 2024 01:38:42 +1030
| Newsgroups | gmane.linux.suse.kde |
|---|---|
| Message-ID | <MEYP282MB3323BC6B4ABC3D6C15C0BCD6BC782@MEYP282MB3323.AUSP282.PROD.OUTLOOK.COM> |
--nextPart5598216.5nej5CW1dp Content-Type: multipart/related; boundary="nextPart4424209.CKvuEEr1bH"; protected-headers="v1" Content-Transfer-Encoding: 7Bit From: Rodney Baker <[email protected]> To: [email protected] Subject: Re: Strange future timestamp issue on some emails in KMail Date: Sun, 28 Jan 2024 01:38:42 +1030 Message-ID: <[email protected]> In-Reply-To: <[email protected]> MIME-Version: 1.0 This is a multi-part message in MIME format. --nextPart4424209.CKvuEEr1bH Content-Type: multipart/alternative; boundary="nextPart2746924.slZzRPbuAg" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart2746924.slZzRPbuAg Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="iso-8859-1" On Saturday, 27 January 2024 23:56:27 ACDT Carlos E. R. wrote: > [...] > > No idea, but maybe you could post the "Date:" header you see in "view > source" and some of the received headers. > Kmail reports (with some details redacted): From: *ntop@ntop-pi.<[1]*localdomain> To: *u[2]*ser*@d*omain Date: *28 Jan 2024 10:06:20* Spam Status: *Spamassassin [3] * View Source reports: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on mail.<localdomain> X-Spam-Level: X-Spam-Status: No, score=-1.0 required=4.5 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=4.0.0 Received: from mail.<localdomain> (ntop-pi.<localdomain> [10.xxx.xxx.xxx]) by mail.<localdomain> (8.17.1.9/8.17.1.9/Debian-2) with ESMTP id 40RD6KgZ023092 for <user>@<localdomain>; Sat, 27 Jan 2024 23:36:21 +1030 Subject: ntopng @ <snipped> Date: Sat, 27 Jan 2024 23:36:20 It is currently 28/01/2024 01:40 here - according to KMail this message was received in the future (but the date header on the message is correct). It appears that KMail is for some reason adding the timezone offset to the date header. Regards, -- ============================================================================== ============================ Rodney Baker [email protected] ============================================================================== ============================ -------- [1] mailto:ntop%40ntop-pi.vk5ztv.ampr.org [2] mailto:bakerr%40iinet.net.au [3] data:image/ PNG;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAABCAMAAADpTH4XAAAASFBMVEUA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAD/// +qqqoAAAD2cKDYAAAAGHRSTlMAAAAAAAAAAAAAAAAAAAAAAAAAAAD// wCysdQaAAAACXBIWXMAAA3XAAAN1wFCKJt4AAAAC0lEQVQImWMQxQIAEU8BpQ0ofWgAA AAASUVORK5CYII= --nextPart2746924.slZzRPbuAg Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" <html> <head> <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8"> </head> <body><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0= ;"><span style=3D"font-size:0.67em;">On Saturday, 27 January 2024 23:56:27 = ACDT Carlos E. R. wrote:</span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">>= ; [...] </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">>= ; </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">>= ; No idea, but maybe you could post the "Date:" header you see in= "view </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">>= ; source" and some of the received headers.</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">>= ; </p> <br /><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0= ;">Kmail reports (with some details redacted): </p> <br /><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0= ;"><span style=3D"font-size:-0.083em;"><span style=3D"color:#c8c8c8;"><span= style=3D"font-family:FreeSans;">From:</span></span></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><st= rong><a href=3D"mailto:ntop%40ntop-pi.vk5ztv.ampr.org">ntop@ntop-pi.<</a= ></strong><span style=3D"font-size:0.67em;">localdomain></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"font-size:-0.083em;"><span style=3D"color:#c8c8c8;">To:</span><= /span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><st= rong><a href=3D"mailto:bakerr%40iinet.net.au">u</a></strong><span style=3D"= font-size:0.67em;">ser</span><span style=3D"font-size:-0.083em;"><span styl= e=3D"color:#80b5ff;"><strong>@d</strong></span></span><span style=3D"font-s= ize:0.67em;">omain</span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"font-size:-0.083em;"><span style=3D"color:#c8c8c8;">Date:</span= ></span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><st= rong><span style=3D"color:#aaafb3;">28 Jan 2024 10:06:20</span></strong></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><sp= an style=3D"color:#c8c8c8;">Spam Status:</span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><st= rong><span style=3D"color:#c8c8c8;">Spamassassin=A0<img src=3D"cid:38509328= 41578173328@KDE" width=3D"20" height=3D"5" />=A0</span></strong></p> <br /><br /><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-r= ight:0;"><span style=3D"font-size:0.67em;">View Source reports: </span></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">X-S= pam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on mail.<localdomai= n></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">X-S= pam-Level: </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">X-S= pam-Status: No, score=3D-1.0 required=3D4.5 tests=3DALL_TRUSTED,SHORTCIRCUI= T</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&nb= sp; shortcircuit=3Dham autolearn=3Ddisabled version=3D4.0.0</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Rec= eived: from mail.<localdomain> (ntop-pi.<localdomain> [10.xxx.x= xx.xxx])</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&nb= sp; by mail.<localdomain> (8.17.1.9/8.17.1.9/Debian-2) wi= th ESMTP id 40RD6KgZ023092</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&nb= sp; for <user>@<localdomain>; Sat, 27 Jan 2024 23:3= 6:21 +1030</p> <br /><br /><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-r= ight:0;">Subject: ntopng @ <snipped></p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Dat= e: Sat, 27 Jan 2024 23:36:20</p> <br /><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0= ;">It is currently 28/01/2024 01:40 here - according to KMail this message = was received in the future (but the date header on the message is correct).= It appears that KMail is for some reason adding the timezone offset to the= date header. </p> <br /><p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0= ;">Regards,</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">-- = </p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Rod= ney Baker</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">rod= [email protected]</p> <p style=3D"margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D</p> </body> </html> --nextPart2746924.slZzRPbuAg-- --nextPart4424209.CKvuEEr1bH Content-ID: <3850932841578173328@KDE> Content-Transfer-Encoding: base64 Content-Type: image/png; name="data:image/PNG;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAABCAMAAADpTH4XAAAASFBMVEUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///+qqqoAAAD2cKDYAAAAGHRSTlMAAAAAAAAAAAAAAAAAAAAAAAAAAAD//wCysdQaAAAACXBIWXMAAA3XAAAN1wFCKJt4AAAAC0lEQVQImWMQxQIAEU8BpQ0ofWgAAAAASUVORK5CYII=" iVBORw0KGgoAAAANSUhEUgAAABQAAAABCAYAAADeko4lAAAACXBIWXMAAA3XAAAN1wFCKJt4AAAA EElEQVQImWP8////fwYqAgA5dwP+2o01iwAAAABJRU5ErkJggg== --nextPart4424209.CKvuEEr1bH-- --nextPart5598216.5nej5CW1dp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEGamQyr3/FaVdR3B49C+FcqxB9twFAmW1HHoACgkQ9C+FcqxB 9txebAgAnfbrh70oCYwIb42ZqZy7inNa+aRi4qRE27+bZ/KmgxP/baoitmhbqWu/ AD1lvBMlt+mdpcXocWNYJGpJAD8tFNPg19lolhD7VcbSqUCHPPidL2WjOrPxjHeI fLw7MBC26lKNxTEj6b74rtGLzHKKBE1nsT2c6V4bodq+GF5dbP38q/tK9Qmi/iFe 5dkZc0EbWuLWYKEpFZEvXuU6F+pe4Bcsqj064XKME86sqUxbqvrPGZVF8BgD5wa5 Zwm8Fsz0jcZ8Vg01dOKhqWrOaRfNusJ+pZAstCC3Rt7NBuE6h4b6sO41mlC1whny jpJ0AyueM1C0C8LCQWO2RBAflUkWoA== =c8KL -----END PGP SIGNATURE----- --nextPart5598216.5nej5CW1dp--