Evolution fails to properly parse Date: header

[Ken Pratt]

I received an email with a date header of:

Date: Thu, 31 Jan 2019 19:15:39 +0000 (UTC)

It is incorrectly show as

Thu 14:15

In the Date column of the message display. The month abbreviation and day number are not present. The email shows up sorted incorrectly by the Thu 14:15 date (as if it were within the last week) instead of the actual Thu, 31 Jan 2019 19:15:39 +0000 (UTC) date.

Perhaps it is the redundant timezone indicator?

Thank you for the great work!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evolution 3.28.5-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 7 15:07:28 2019
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2018-05-12 (271 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

[Andre Klapper (a9016009)]

Can you please share/attach a public testcase? "File > Save as mbox...", then edit that text file with a text editor to remove/alter any confidential information. Thanks!

[Ken Pratt (kenpratt)]

My apologies - I no longer have the example email.

[Ken Pratt (kenpratt)]

It seems that the parser in evolution fails to parse:

Date: Thu, 31 Jan 2019 19:15:39 +0000 (UTC)

The above is the actual header from the SMTP conversation.

[Sebastien Bacher (seb128)]

Could you perhaps report it upstream as well on https://gitlab.gnome.org/GNOME/evolution/issues/ ?

[Andre Klapper (a9016009)]

No problem here parsing and displaying the line

Date: Thu, 31 Jan 2019 19:15:39 +0000 (UTC)

in Evolution 3.32.3.

This should not be reported upstream until there is a testcase (exported email message) and until successfully re-tested in a version supported by upstream developers (currently: 3.32).