Closed albrechtd closed 4 years ago
Thanks, I had a feeling there was a case I missed.
I can confirm that the latest git version fixes the issue for my test set of semi-broken messages collected in the wild. Thanks a lot for you quick fix! Best, Albrecht.
I noticed that for some broken messages I picked up in the wild, the new header parser introduced as fix for #78 does not emit an error message. This seems to happen if the very first header of a message part is broken. E.g. for the following minimal example message
the application
examples/msgcheck
as of version 3.2.5 detectswhilst the latest git (or release 3.2.6) says
Apparently, all broken top-level (message) headers as well as all other broken part headers (i.e. except for the first one) are detected properly.