Date: Fri, 12 Apr 2024 17:58:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235136] cron email header has bogus date value Message-ID: <bug-235136-227-1ttfcEaq3Q@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235136-227@https.bugs.freebsd.org/bugzilla/> References: <bug-235136-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235136 --- Comment #2 from Mike Lempriere <ml-freebsd.org@vintners.net> --- I barely even remember this one... I worked around my issue by lowering spamassassin scores, so haven't paid it further attention. However, looking closely now at email source headers, I am still seeing DATE_IN_FUTURE_03_06 in my built-in "daily run" cron emails. The Received headers and Date all agree on the time of 03:02:03. This job (I believe) is started by /etc/crontab which shows: 1 3 * * * root periodic daily meaning it starts at 03:01. Just trying 'periodic daily' on the command li= ne it's about a min to run, and that's what we're seeing in the email header. Here's the sample I'm looking at: Date: Sat, 6 Apr 2024 03:02:03 -0700 (PDT) Looking at RFC 2822, I'm not sure that the closing "(PDT)" is compliant, so perhaps the fault could be considered to be cron. However, if this is compliant, and this is my incomplete understanding of the RFC, that would m= ean that cron is fine, and spamassassin is misunderstanding the headers. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235136-227-1ttfcEaq3Q>