QUOTE(mzaleski @ Feb 25 2008, 07:59 PM)

Hrmm, ok, I pulled up RFC 2822 email spec. You are correct in that the current spec calls for +/- and 4 digit offset for timezone. Section 4.3 "Obsolete Date and Time" indicates a large number of textual timezones including "UT", "GMT", "EST" and so on (defined in RFC 822).
Digging deeper, I searched IMP bugs and found:
http://bugs.horde.org/ticket/5717 . That bug report was closed as "won't fix". After asking on IMP's mailing list, the problem is in PHP 5.x (worked fine in PHP4.x). See
http://thread.gmane.org/gmane.comp.horde.imp/23623: interestingly, someone quoted the RFC 2822 spec and it states that email clients must still be able to process the old timezone entries from RFC 822.
Searching for PHP bugs, I found
http://bugs.php.net/bug.php?id=42486, in which the PHP developers refused to fix it. This is frustrating.
It sounds like the PHP devs are telling their users that they have to do a search/replace of "UT" with "UTC" before calling strtotime().
Everyone is claiming it isn't a bug, but the net result is IMP is not a RFC 2822 compliant email package due to this problem. And yes, I realize that both PHP and IMP are open source packages with volunteers doing the coding.