So, dumping from the database: umask 022 && unset LC_ALL && LANG=en_US.UTF-8 export LANG && db=/var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db && sqlite3 "$db" 'select * from hyperkitty_email where mailinglist_id = 6 and ( id = 2046 or id = 2047 );' 2046|E1sgLGY-0004Xq-I8@balug-sf-lug-v2.balug.org|FHYXBZALJW2OGKRF6Z6H5K4AQKWDDRHM|[BALUG-Test] test - ignore Check database timezone behavior|Check database timezone behavior 2024-08-20T09:35:01+00:00 Tue, 20 Aug 2024 09:35:01 +0000 Tue Aug 20 09:35:01 2024 2024-08-20T02:35:01-07:00 Tue, 20 Aug 2024 02:35:01 -0700 Tue Aug 20 02:35:01 2024|2024-08-20 09:35:02|0||2024-08-20 09:36:25.979261|0||mpaoli@balug.org|1197|Michael Paoli|6| 2047|E1sgLGX-0004Xd-Vw@balug-sf-lug-v2.balug.org|YOB5QE7J2T6IKPCCA4OGHNHWDMMZ2OVN|[BALUG-Test] test - ignore Check database timezone behavior|Check database timezone behavior 2024-08-20T09:35:01+00:00 Tue, 20 Aug 2024 09:35:01 +0000 Tue Aug 20 09:35:01 2024 2024-08-20T02:35:01-07:00 Tue, 20 Aug 2024 02:35:01 -0700 Tue Aug 20 02:35:01 2024|2024-08-20 09:35:02|0||2024-08-20 09:36:28.873014|0||mpaoli@balug.org|1198|Michael Paoli|6|
Well ... not quite what I was hoping to be able to test. Looks like despite different TZ settings, mailx used same Date: header in each.
Michael Paoli wrote:
Check database timezone behavior 2024-08-20T09:35:01+00:00 Tue, 20 Aug 2024 09:35:01 +0000 Tue Aug 20 09:35:01 2024 2024-08-20T02:35:01-07:00 Tue, 20 Aug 2024 02:35:01 -0700 Tue Aug 20 02:35:01 2024