Re: Wrong Sent-date shown in Outlook Express

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I think it's a bug on the server, not in Outlook Express. Might post asking the question in an Exchange newsgroup.
--
Jim Pickering, MVP, Outlook Express
https://mvp.support.microsoft.com/profile=F9F51EF1-4AE3-4D23-B2D8-1171988A62D6

Please deliver feedback to the newsgroup, so that others can be helped. No one gets paid to help here, and the response rate from those that are helped is less than 4-5%. If that were how medical advancements were made we would all have died years ago. Thanks.


"Martin Knafve" <knafve@xxxxxxxxxx> wrote in message news:%23mC4x5bSFHA.164@xxxxxxxxxxxxxxxxxxxxxxx
In Outlook Express, the date in the message list, "Sent"-column is sometimes shown incorrectly when using IMAP.

The error occurs when the date given by the IMAP server in the Envelope-response is Base64-encoded. Since the date is normally unencoded, this only happens if the Date: header contains special characters.

Outlook says:
v3e9 UID FETCH 1:* (BODY.PEEK[HEADER.FIELDS (References X-Ref X-Priority X-MSMail-Priority X-MSOESRec Newsgroups)] ENVELOPE RFC822.SIZE UID FLAGS INTERNALDATE)

The server then responds:
* 1 FETCH (UID 11 RFC822.SIZE 672 FLAGS (\Seen) INTERNALDATE "25-Apr-2005 18:54:07 +0200" ENVELOPE ("=?iso-8859-1?B?VGh1LCAyMCBKYW4gMjAwNSAxMDo1ODo1NSAtMDIwMCAoSG9y4XJpbyBicmFzaWxlaXJvIGRlIHZlcuNvKQ==?=" "subject" (("address@xxxxxxxxxxxxx" NIL "address" "domain.com.br")) (("address@xxxxxxxxxxxxx" NIL "address" "domain.com.br")) (("address@xxxxxxxxxxxxx" NIL "address" "domain.com.br")) (("address@xxxxxxxxxxxxx" NIL "address" "domain.com.br")) NIL NIL NIL "<.123.123.123.123.1106225935.squirrel@xxxxxxxxxxxxxxx>") BODY[HEADER.FIELDS (References X-Ref X-Priority X-MSMail-Priority X-MSOESRec Newsgroups)] {24}[nl]

The first parameter in the ENVELOPE response is the date. In this case, it's encoded usigng base 64 (since it contains non-ascii characters in the time-zone specification). Instead of de-coding the date, Outlook shows 8859-01-01 as year for this email message. It looks like it just removes the characters from the string =?iso-8859-1?B?VG.. and displays them to the client.

If the date is sent to OE as literal data instead, the date is shown properly. I took a quick view in the IMAP RFC and could not find anything telling that the date given by the server is never encoded. Also, Outlook Express decodes all other ENVELOPE components properly (such as subject and email address) so it's hard to understand why the date isn't decoded properly.

Anyone has any comments on this? Is this an Outlook Express bug?

Kind regards,
Martin Knafve


.

Relevant Pages

  • Re: Fetchmail + Sendmail for local users ??
    ... While checking IMAP folder through OE at server, it ask for the u/n and ... I can't help, I'm afraid, as I don't use Outlook. ... OK Dovecot ready. ... Unable to authenticate to IMAP server ...
    (Fedora)
  • Re: Fetchmail + Sendmail for local users ??
    ... While checking IMAP folder through OE at server, it ask for the u/n and ... I can't help, I'm afraid, as I don't use Outlook. ... OK Dovecot ready. ... Unable to authenticate to IMAP server ...
    (Fedora)
  • Re: Single user issue; best troubleshooting
    ... COULD be cause by that intermediate 'network access' server ... you do know there is significant logging in Outlook ... form of Integrated Authentication and so all of the OUTLOOK ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to allow POP3 SSL connections w ISA 2004
    ... the Outlook group as well. ... Firewall Client configuration for ISA Server 2004. ...
    (microsoft.public.windows.server.sbs)
  • RE: login and email problems
    ... To the Outlook issue, ... Run "ipconfig /registerdns" command to register the DNS server. ... Ensure that you have an Outlook profile configured for the server ... profile is not associated with a Microsoft Exchange Server e-mail account. ...
    (microsoft.public.windows.server.sbs)