Bug: importer should not store mails that don't have a Date: header
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
Related to #436, at present the importer uses the current timestamp if the mail has no Date: header.
Any such mail will be filed incorrectly.
The importer should report such mails and ignore them instead (as is done for some other mails that cannot be stored).
Maybe there should be an option to abort the import instead.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the importer path that handles messages without a Date: header, and compare it with the existing handling for mails that cannot be stored. Verify how import errors are reported and confirm that a mail lacking Date is reported and ignored rather than assigned the current timestamp; the optional abort behavior is left unresolved by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100