Fix double timestamp in logfiles

Regression in 6.5.X vs. earlier releases.

Spencer Collyer reported through the mailing list that on Arch Linux, fetchmail 6.5.2 now has undesired timestamps in the output, on 2025-04-14:

After a recent update of my Arch Linux system my fetchmail is now at release 6.5.2+TLS+NLS.

Since updating to this release, I'm seeing timestamps appearing in the fetchmail output, where they didn't appear before.

For instance, sample output used to be:

-----------------------------------------------
2 messages for X at Y (89359 octets).
reading message X@Y:1 of 2 (47364 octets) flushed
reading message X@Y:2 of 2 (41995 octets) flushed
-----------------------------------------------

But now I'm getting:
-----------------------------------------------
Apr 04 09:00:00 fetchmail: 3 messages for X at Y (82284 octets).
Apr 04 09:00:00 fetchmail: reading message X@Y:1 of 3Apr 04 09:00:00 fetchmail:  (31026 octets) flushed
Apr 04 09:00:00 fetchmail: reading message X@Y:2 of 3Apr 04 09:00:00 fetchmail:  (31715 octets) flushed
Apr 04 09:00:01 fetchmail: reading message X@Y:3 of 3Apr 04 09:00:01 fetchmail:  (19543 octets) flushed
-----------------------------------------------

I'd like to go back to the old style format, as I don't really need the timestamp - I always call fetchmail in a cron job so don't need the timestamp as the mail from cron tells me when it was run.

Failing that, is it possible to at least get rid of the second timestamp on each line? That is just noise which makes the message harder to read.