On 10/2/20 2:58 PM, Alex Schuilenburg via Mailman-users wrote:
I ran both on the original archive, cleanarch made no changes and check_hk_import just retported the number of messages.
That's actually expected with this mbox as there are apparantly no
unescaped From lines in the message body and no other serious defects.
As it turns out, the message was imported, but with the dodgy email as sender which was fixed by the insert/update as per my comment.
Hope you have some success with the redacted mbox example.
As I mention at <https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422998204> I imported the mbox to a test list, and there were noe real issues. What issue there is is the mbox message's actual From: header is
From: Firstname Surname at example-UK <user@example.com>
Part of what's going on is some MM 2.1 archives has email addresses
obfuscated by replacing @ with at so the import process reverses
this and changes the From: to
header is
From: Firstname Surname@example-UK <user@example.com>
which now contains two email addresses albeit not separated by a comma
and picks the first. The message then gets properly archived with
sender Firstname Surname@example-UK which is a syntactically valid
email address and doesn't cause the ResponseNotReady() exception in
sync_mailman so I don't see that issue.
The difference is either the fact that my test runs with the HEAD of the GitLab branch which may not have the issue or the difference between the real From: header and the sanitized one is significant.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan