>
> >> > > I think I am starting to see this more often. Today I was checking
> >> > > again every server to see if the ntp time is syncing properly. But
> >> > > don't notice anything weird, can't really believe this sending had
> a
> >> > > bad clock. Can anyone suggest what/where to look for?
> >> > >
> >> > >
> >> > > DATE_IN_FUTURE_24_48 Date: is 24 to 48 hours after
> >> >
> >> > When you looked at the Date: header, what did it say? The part of
> >> > your question where you gave an example didn't make it through the
> >> > mailinglist!
> >>
> >> I was wondering if I am the only one seeing this. Could also be
> related
> >> to my transitioning to el9. I can remember having to change some
> scripts
> >> for time/timezone. Logged times seem ok:
> >>
> >> mta logging was on this date: Jul 4 08:51:37
> >> message header Date: Thu, 4 Jul 2024 08:51:35 +0200
> >> message header Received: xxxx Thu, 4 Jul 2024 08:51:37 +0200
>
> >This does not look like something out of the ordinary not? Even if it is
> a timezone/summertime issue it is still not 'is 24 to 48 hours after'
>
> This looks correctly.
> I remember seeing this issue when users put incorrect date or incorrect
> timezone.
Incorrect date on the Windows / MacOS will trigger this?
> Do those still appear?
Looks like it is still a low %, except this T_DATE_IN_FUTURE_96_Q
DATE_IN_FUTURE_03_06
0.1% DATE_IN_FUTURE_12_24
0.1% DATE_IN_FUTURE_06_12
31% T_DATE_IN_FUTURE_96_Q
