Just when I thought I maybe had a working setup, suddenly decides that it is “unable to parse INTERNALDATE format” in some message in some folder :-(

It seems that some component (?) considers *all* lines starting with “Date:” as message dates, but of course with all the TOFU, there are tons of matching lines—but the rest isn’t conformant. I’ve already fixed those that follow some pattern, but there are tons that are completely off (like “Date: 3 f=C3=A9vrier 2022 =C3=A0 11:23:21 UTC+1”).

Of course, all of this could have been avoided by not migrating to hell and its oh-so-modern authentication.

Since I’ve just gotten another reminder that will be required to access UNIL’s server, I decided to give it another try.

This time I let sync to a new, empty directory. It ran into the same problem as last time:

IMAP error: unable to parse INTERNALDATE format

Apparently something is different with that makes mbsync think that lines in the body that start with “Date:” are headers… The solution seems to be to turn off the “CopyArrivalDate” option in the mbsync configuration (which is actually the default value).

The first run is not finished, but so far, things are looking good… Phew!

Show thread
Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.