Hello, On Sat, Aug 13, 2022 at 11:41:49AM +0200, debbug.neom...@sideload.33mail.com wrote: > Package: neomutt > Version: 20201127+dfsg.1-1.2 > Severity: normal > Tags: upstream > X-Debbugs-Cc: debbug.neom...@sideload.33mail.com > > The “Date:” field is added after the user instructs neomutt to send > their message, so there is no opportunity for the user to edit the > timestamp of the message. Perhaps rightly so, for RFC-compliance. But > the timestamp that mutt generates exposes the timezone of the > author. It’s too much information. E.g. this reveals to the recipient > and all mail servers enroute that the sender is physically in the > central Europe timezone: > > Date: Fri, 12 Aug 2022 13:21:24 +0200 > > This exposes the presence of senders in the eastern US timezone: > > Date: Fri, 12 Aug 2022 13:21:24 -0400
I suggest to unset the local_date_header configuration option.
From the manual:
3.171. local_date_header
Type: boolean
Default: yes
If set, the date in the Date header of emails that you send will be in
your
local timezone. If unset a UTC date will be used instead to avoid
leaking
information about your current location.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
signature.asc
Description: PGP signature
