Bug: import-mbox.py should not default invalid dates to 'now'
Open
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
It makes sense for archiver.py to default invalid or missing dates to now, because the archiver deals with live messages.
However it does not make sense for the importer to do so.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in import-mbox.py and compare its handling of invalid or missing dates with archiver.py, which the issue identifies as having different behavior. Confirm the intended importer behavior for those dates and verify that imported messages no longer receive the current time by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100