> > 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
On 22.07.24 09:58, Marc wrote:
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.
Do those still appear?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -- Benjamin Franklin, 1759
