You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I imported over 100K old emails via an EML ZIP import. The result was that only approx. 1/3 of them were successfully imported based on the UI's job display. This would be a pain in the rear to hand-validate which were failures. I wish I could give more specific numbers, but a few minutes ago I upgraded to the latest version, and now there are no listed completed Background Jobs listed, so I can't open the import results and give you specifics. Doesn't seem to be available anymore as a report!
Anyway, first, I grepped the logs, but the output was unusable for my purposes: import failures are output as "warn" rather than "error," but "warn" seems to also be used when a duplicate is skipped, so I don't know if an EML import failed because it was a dupe or because it couldn't be parsed. At minimum, my huge import could be helpful to finding if any EML parsing bugs exist in the codebase.
I checked my source EML files, and only 8 of them are missing an Message-Id header. I have a sqlite DB containing info about every email, including this Message-Id. It would be great to be able to check the archive via API for each Message-Id to find out which ones failed, and then manually investigate these EML files to see if they're malformed or if there's another reason they weren't imported by Mail-Archiver.
Describe the solution you'd like
Be able to query by any email header field makes the most sense to me, as it would be the same level of effort, I think. There's no reason implementing search for one header would be more complex than search over any header.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem?
I imported over 100K old emails via an EML ZIP import. The result was that only approx. 1/3 of them were successfully imported based on the UI's job display. This would be a pain in the rear to hand-validate which were failures. I wish I could give more specific numbers, but a few minutes ago I upgraded to the latest version, and now there are no listed completed Background Jobs listed, so I can't open the import results and give you specifics. Doesn't seem to be available anymore as a report!
Anyway, first, I grepped the logs, but the output was unusable for my purposes: import failures are output as "warn" rather than "error," but "warn" seems to also be used when a duplicate is skipped, so I don't know if an EML import failed because it was a dupe or because it couldn't be parsed. At minimum, my huge import could be helpful to finding if any EML parsing bugs exist in the codebase.
I checked my source EML files, and only 8 of them are missing an
Message-Idheader. I have a sqlite DB containing info about every email, including this Message-Id. It would be great to be able to check the archive via API for each Message-Id to find out which ones failed, and then manually investigate these EML files to see if they're malformed or if there's another reason they weren't imported by Mail-Archiver.Describe the solution you'd like
Be able to query by any email header field makes the most sense to me, as it would be the same level of effort, I think. There's no reason implementing search for one header would be more complex than search over any header.
Additional context
No response
All reactions