From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 606629373C for ; Tue, 20 Feb 2024 11:08:10 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F1334429A for ; Tue, 20 Feb 2024 11:07:27 +0100 (CET) Received: from nena.proxmox.com (unknown [94.136.29.99]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Tue, 20 Feb 2024 11:07:24 +0100 (CET) Received: by nena.proxmox.com (Postfix, from userid 1000) id 69747CC68A; Tue, 20 Feb 2024 11:07:24 +0100 (CET) From: Mira Limbeck To: pmg-devel@lists.proxmox.com Date: Tue, 20 Feb 2024 11:06:49 +0100 Message-Id: <20240220100648.44119-6-m.limbeck@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20240220100648.44119-1-m.limbeck@proxmox.com> References: <20240220100648.44119-1-m.limbeck@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.604 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pmg-devel] [PATCH v3 pmg-api] MailTracker: remove timezone offset X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Feb 2024 10:08:10 -0000 The timezone offset is moved to `pmg-log-tracker` in the compatibility code path. This way the new rfc3339 timestamp, which is already in UTC, can be used as is. Signed-off-by: Mira Limbeck --- v3: - no changes v2: - no changes src/PMG/API2/MailTracker.pm | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/PMG/API2/MailTracker.pm b/src/PMG/API2/MailTracker.pm index b8b25ad..ffda4b5 100644 --- a/src/PMG/API2/MailTracker.pm +++ b/src/PMG/API2/MailTracker.pm @@ -43,8 +43,6 @@ my $run_pmg_log_tracker = sub { my $logids = {}; - my $timezone = tz_local_offset();; - if (defined(my $id = $includelog)) { if ($id =~ m/^Q([a-f0-9]+)R([a-f0-9]+)$/i) { $logids->{$1} = 1; @@ -128,7 +126,7 @@ my $run_pmg_log_tracker = sub { } elsif ($line =~ m/^TO:([0-9A-F]+):([0-9A-F]+):([0-9A-Z]):\s+from <([^>]*)>\s+to\s+<([^>]+)>\s+\((\S+)\)$/) { my $new = { size => $entry->{size} // 0, - time => hex($1) - $timezone, + time => hex($1), qid => $2, dstatus => $3, from => $4, @@ -174,7 +172,7 @@ my $run_pmg_log_tracker = sub { } elsif ($line =~ m/^TO:([0-9A-F]+):(T[0-9A-F]+L[0-9A-F]+):([0-9A-Z]):\s+from <([^>]*)>\s+to\s+<([^>]*)>$/) { my $e = {}; $e->{client} = $entry->{client} if defined($entry->{client}); - $e->{time} = hex($1) - $timezone; + $e->{time} = hex($1); $e->{id} = $2; $e->{dstatus} = $3; $e->{from} = $4; -- 2.39.2