From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)
Description of problem:
/usr/sbin/imapd creates bad unix mailbox From line due to bad timezone
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Send self mail from a foreign account.
2. Collect mail using pop on an Outlook or Outlook Express client.
3. Move message to a folder on an imap server.
Actual Results: Message will appear to be received at the current time in GMT,
which is then converted to an equivalent local time.
Expected Results: Message should appear to be received at the current time in
the current local timezone.
The following line in mailbox files on the imap server is responsible for the
From email@example.com Wed Feb 13 17:07:51 2002 -0000
in my case this should be:
From firstname.lastname@example.org Wed Feb 13 17:07:51 2002 +1000
This bug is documented in /usr/share/doc/imap-2000c/bugs.txt dated
Jan 10, 2001 from imap RPM is: imap-2000c-15.i386.rpm
"In some versions of Redhat Linux, SVR4-style timezone name lookup
doesn't work properly due to a bug in glibc. The workaround is to
edit os_lnx.c to include tz_bsd.c instead of tz_sv4.c. Note that
other versions of Linux don't support BSD-style timezone name
lookup, so don't make this change unless it's needed on your system."
The problem appears on both Outlook 2000 SR-1 (220.127.116.1114) and
Outlook Express 5.50.4807.1700 clients.
The problem appears on both imap and imaps implementations.
Following instructions in /usr/share/doc/imap-2000c/bugs.txt as documented:
Application of /usr/src/redhat/SOURCES/imap-2000c-redhat-timezone.patch
-rw-r--r-- 1 root root 297 Feb 16 05:08 imap-2000c-redhat-timezone.patch
--- imap-2000c/src/osdep/unix/os_lnx.c.redhat-timezone Wed Oct 25 09:41:08 2000
+++ imap-2000c/src/osdep/unix/os_lnx.c Sat Feb 16 05:08:30 2002
@@ -42,4 +42,5 @@
#define fork vfork
+/* #include "tz_sv4.c" */
... does NOT result in any noticable change in behaviour as far as correct
timezone stamping of unix mailbox From lines is concerned. :(
If this is indeed a bug in glibc, then it is probably something that
should be fixed in glibc I think. I have no idea either way, but
patching imap to fix a glibc bug doesn't seem right to me.
Reassigning to glibc component.
Should be fixed in glibc-2.2.4-24.