Re: Strange future timestamp issue on some emails in Kmail [SOLVED]
Rodney Baker <[email protected]> Mon, 29 Jan 2024 19:52:41 +1030
| Newsgroups | gmane.linux.suse.kde |
|---|---|
| Message-ID | <MEYP282MB3323D00B39A88A80D2083F59BC7E2@MEYP282MB3323.AUSP282.PROD.OUTLOOK.COM> |
--nextPart4357918.zNYaBHVF5K Content-Type: multipart/alternative; boundary="nextPart1797114.PhDGmT1pYT"; protected-headers="v1" Content-Transfer-Encoding: 7Bit From: Rodney Baker <[email protected]> To: [email protected] Date: Mon, 29 Jan 2024 19:52:41 +1030 Message-ID: <[email protected]> MIME-Version: 1.0 This is a multi-part message in MIME format. --nextPart1797114.PhDGmT1pYT Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Sunday, 28 January 2024 18:36:06 ACDT Rodney Baker wrote: [...] > > You have to make the sender software add time zone info to the "Date:" > > header. > > Right, got it, thanks. So it is an ntop-ng issue - I'll have to raise a > ticket with them then. > > Thanks for the tip. > > Regards, > Rodney. Just a followup - found the problem with ntop-ng, reported it to the devs and they've ack'd it and pushed a fix already. Just waiting on the update to be published and available. Regards, Rodney. -- ============================================================================== ============================ Rodney Baker [email protected] ============================================================================== ============================ --nextPart1797114.PhDGmT1pYT Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii" <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">On Sunday, 28 January 2024 18:36:06 ACDT Rodney Baker wrote:</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">[...]</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > You have to make the sender software add time zone info to the "Date:"</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > header.</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> Right, got it, thanks. So it is an ntop-ng issue - I'll have to raise a</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> ticket with them then.</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> Thanks for the tip.</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> Regards,</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> Rodney.</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Just a followup - found the problem with ntop-ng, reported it to the devs and they've ack'd it and pushed a fix already. Just waiting on the update to be published and available. </p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Regards,</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Rodney.</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">-- </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">==========================================================================================================</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Rodney Baker</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">[email protected]</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">==========================================================================================================</p> </body> </html> --nextPart1797114.PhDGmT1pYT-- --nextPart4357918.zNYaBHVF5K 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+FcqxB9twFAmW3bmEACgkQ9C+FcqxB 9tzabgf9HQcrY8QotfptEJvemBOMDeJEwsJ50MWrMoGQboksxMZt6J3NgLwSmTZ5 NqP/AmkmCjSAoYKGddUJ6ux2KMZEhIJWUI1Rl16p+OFmpX3EMYA/XrxGqai//Zmt RwC/9UVH6HU0ZgaFIOGeFoiRxaurbdMXgOqNCaGeMK4+4xDHOTfI99sYO5Y7ATiM 1j6JFsCTQ9NGQupkAF5gxOo5cWRDwj6m1SlR4F0HYnbtcNXWE0OFyzEHHZfyBRFb /snAH+7zh7Gm8poiZ5qE+OWDKZzVq5SaWu1WANfJBJJaeRuMCh9X3I3ttpXzKic9 QqmtGjQ1mCVOHdhaRQBGECWwGA1Fdw== =/8jR -----END PGP SIGNATURE----- --nextPart4357918.zNYaBHVF5K--