6.0.0-beta1
7/5/25

[#14931] Invalid date in an email makes imp break entirely
Summary Invalid date in an email makes imp break entirely
Queue IMP
Queue Version FRAMEWORK_5_2
Type Bug
State No Feedback
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester sami (at) tokavuh (dot) com
Created 06/25/2019 (2202 days ago)
Due
Updated 08/07/2019 (2159 days ago)
Assigned 06/30/2019 (2197 days ago)
Resolved 08/07/2019 (2159 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch Yes

History
08/07/2019 01:54:48 AM Michael Rubinsky State ⇒ No Feedback
 
06/30/2019 05:16:01 PM Michael Rubinsky Comment #2
Assigned to Michael Rubinsky
State ⇒ Feedback
Priority ⇒ 1. Low
Reply to this comment
I cannot reproduce this in FRAMEWORK_5_2 or in master.  I also tried 
importing email with various broken Date: headers into the horde demo 
server without breaking it.

Please provide an example email file that triggers this behavior.
06/25/2019 01:12:50 PM sami (at) tokavuh (dot) com Comment #1
Priority ⇒ 3. High
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Invalid date in an email makes imp break entirely
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
If you receive an email dated enough in the future, for example in the 
year 2155, imp 6.2.22's Mailbox::Ui::getDate() function returns 
invalid data, which makes the JSON contain an email with Date property 
set to false instead of a date, which makes the whole imp to break 
entirely. No folder list, no email list, nothing. The user cannot fix 
this without deleting the email through some other application.

It can easily be patched by adding a check for what strftime returns 
and if it's false then return _("Unknown Date") instead of what 
strftime says.

Saved Queries