From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] gmail imap
Date: Fri, 21 Nov 2008 12:21:05 -0500 [thread overview]
Message-ID: <a5c6a816f207b6f8ba6bed98ec10cad5@quanstro.net> (raw)
there definately is a bug in gmail's imap
3 uid fetch 29 (rfc822.size)<cr>
* 29 FETCH (UID 29 RFC822.SIZE 1234)<cr>
3 OK Success<cr>
3 uid fetch 29 (body[])<cr>
* 29 FETCH (UID 29 BODY[] {1246}<cr>
[...]
oops. the obvious bug, that the body of the email
is 1246 - 1234 lines long and they forgot to count
the <cr>s added by the protocol doesn't check
because the body is 7 lines long. neither is the
header 12 lines long.
- erik
next reply other threads:[~2008-11-21 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 17:21 erik quanstrom [this message]
2008-11-21 19:18 Eris Discordia
[not found] <E0DEFAC8CBB22682FEC4ACE2@192.168.1.2>
2008-11-30 6:05 ` Michaelian Ennis
2008-11-30 15:35 ` erik quanstrom
2008-12-01 15:54 ` Roman Zhukov
2008-12-01 22:44 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5c6a816f207b6f8ba6bed98ec10cad5@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).