32 lines
1.8 KiB
Plaintext
32 lines
1.8 KiB
Plaintext
MBOX-Line: From andris.reinman at gmail.com Wed Jul 30 01:34:31 2014
|
|
To: imap-protocol@u.washington.edu
|
|
From: Andris Reinman <andris.reinman@gmail.com>
|
|
Date: Fri Jun 8 12:34:53 2018
|
|
Subject: [Imap-protocol] Another gmail bug
|
|
Message-ID: <EB485B74-F035-44E5-BAAD-20F9A800DF24@gmail.com>
|
|
|
|
Hello,
|
|
|
|
It seems that recently everyone has been starting to use this mailing list as a GMail issue tracker, so heres my findings as well (do not know if these are known issues or not).
|
|
|
|
1. If you EXAMINE a mailbox and FETCH a message with (FLAGS BODY[HEADER.FIELDS ?]) then the returned FLAGS list *always* includes the \Seen flag even if the message does not have this flag set. If you omit the headers part and just FETCH (FLAGS) then the \Seen flag is returned as it should. Notice that I am using BODY and not BODY.PEEK to fetch the headers. The actual flags are not changed as the mailbox was EXAMINEd not SELECTed but for this call the response includes the invalid \Seen.
|
|
|
|
tag EXAMINE INBOX
|
|
tag FETCH 123 (FLAGS BODY[HEADER.FIELDS (?))
|
|
* 123 FETCH (FLAGS (\Seen))
|
|
tag FETCH 123 (FLAGS)
|
|
* 123 FETCH (FLAGS ()) <- no \Seen flag anymore
|
|
|
|
2. If you have a message with an message/rfc822 attachment and the attached message does not have In-Reply-To set in its headers, then the returned ENVELOPE for this attachment uses ?NIL? as a String instead of NIL for the In-Reply-To value.
|
|
|
|
tag FETCH 123 (BODYSTRUCTURE)
|
|
* 123 FETCH (BODYSTRUCTURE ? (?MESSAGE? ?RFC822? ? (NIL NIL ? ?NIL? <- Should be NIL, not ?NIL"
|
|
|
|
I have also set up simple test cases (as node.js scripts) to verify these bugs: https://gist.github.com/andris9/592d69a40e970ea32597
|
|
|
|
Best regards,
|
|
Andris Reinman
|
|
-------------- next part --------------
|
|
An HTML attachment was scrubbed...
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20140730/9bbf4329/attachment.html>
|