URGENT: The timezone could not be found in the database

[lrpasquetto]

I have a client that has more than 20,000 emails, it keeps the server to control backups.
I'm riding a webmail for my clients and some messages when I read , accuses the following error:

Exception in Headers.php line 56: DateTime::__construct(): Failed to parse time string (Fri, 14 Mar 14 16:19:14 Hora oficial do Brasil) at position 24 (H): The timezone could not be found in the database

• in Headers.php line 56
• at DateTime->__construct('Fri, 14 Mar 14 16:19:14 Hora oficial do Brasil') in Headers.php line 56
• at Headers->parseHeader('date', 'Fri, 14 Mar 14 16:19:14 Hora oficial do Brasil') in Headers.php line 23
• at Headers->__construct(object(stdClass)) in Message.php line 185
• at Message->getHeaders() in Message.php line 170
• at Message->getSubject() in HomeController.php line 179

[ddeboer]

That’s a weird timezone. Which mailserver produces those dates?

What we could do, is wrap the DateTime construction in a try/catch and just leave the date header empty if it fails.

[Slamdunk]

Hi @lrpasquetto can you provide the message raw headers (with sensitive data obscured) that produced the issue?

[Slamdunk]

@lrpasquetto We have added in #199 various weird date time format found in production email:

imap/tests/MessageTest.php

Lines 302 to 315 in aac8f58

	/**
	* @see https://gist.github.com/mikesart/b33762363153e2b8c7c7
	*/
	public function provideDateCases(): array
	{
	return [
	['2017-09-28T09:24:01+0000', 'Thu, 28 Sep 2017 09:24:01 +0000 (UTC)'],
	['2014-06-13T17:18:44+0200', '=?ISO-8859-2?Q?Fri,_13_Jun_2014_17:18:44_+020?=' . "\r\n" . ' =?ISO-8859-2?Q?0_(St=F8edn=ED_Evropa_(letn=ED_=E8as))?='],
	['2008-02-13T02:15:46+0000', '13 Feb 08 02:15:46'],
	['2008-04-03T12:36:15-0700', '03 Apr 2008 12:36:15 PDT'],
	['2004-08-12T23:38:38-0700', 'Thu, 12 Aug 2004 11:38:38 PM -0700 (PDT)'],
	['2006-01-04T21:47:28+0000', 'WED 04, JAN 2006 21:47:28'],
	];
	}

If you will ever get again the mail that produces the error we'll be happy to put it in the cases tested.
Until that time, I'm closing this stalled issue.