This looks like a known issue where we incorrectly constructed some message
metadata. As you can see, it affected messages during a certain timeframe
in the past, and the raw message data itself is not affected. We're hoping
to clean this up, but don't have an ETA for that.
On Sat, May 4, 2013 at 6:40 AM, Davide Gullo <gullo@m4ss.net> wrote:
> Hi,
> nobody knows an issue like this:
>
> ------
> * 22136 FETCH (X-GM-MSGID 1384367682512034576 UID 77480 RFC822.SIZE 0
> RFC822 {11012}
>
> Delivered-To: jazzo72@gmail.com
> ....
> ....
> ....
> )
>
> TAG21 OK Success
> ------
>
> Look at the *RFC822.SIZE, it?s 0 (zero)!*
> But it isn?t really zero as you can see by the RFC822 size, it?s correct
> (11012 bytes).
>
> I got it always at the same time: all the emails after Nov 2011 until Feb
> 2012 have this issue.
> Maybe Gmail had problems in this period?
> Anybody knows it?
> Could it be an IMAP bug?
>
> Thanks,
>
> --
> Davide Gullo
>
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130528/258912e1/attachment.html>