38 lines
1.6 KiB
Plaintext
38 lines
1.6 KiB
Plaintext
MBOX-Line: From arnt at gulbrandsen.priv.no Fri Dec 6 02:01:29 2013
|
|
To: imap-protocol@u.washington.edu
|
|
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
|
|
Date: Fri Jun 8 12:34:51 2018
|
|
Subject: [Imap-protocol] Size wrong
|
|
In-Reply-To: <CANVPb6s8LbY7FxT5HG+ASs08i1_emf62-5ppgufHCtZMh5DRiA@mail.gmail.com>
|
|
References: <CANVPb6s8LbY7FxT5HG+ASs08i1_emf62-5ppgufHCtZMh5DRiA@mail.gmail.com>
|
|
Message-ID: <20131206100129.GE12843@gulbrandsen.priv.no>
|
|
|
|
On Thu, Dec 05, 2013 at 11:18:32PM +0100, Davide Gullo wrote:
|
|
> Look at the RFC822.SIZE (14787), it is different from the size in
|
|
> RFC822 {14985}.
|
|
> Do you see something like that before?
|
|
|
|
I've seen it. It doesn't happen often and most servers avoid it
|
|
completely, but I've seen it.
|
|
|
|
> It could be a bug or I miss something from the IMAP protocol?
|
|
|
|
You can call it either a server bug or an unrealistic demand from the
|
|
RFC.
|
|
|
|
Supplying an exact number can be extremely expensive for the server,
|
|
since the data stored is often not exactly the same as on the wire,
|
|
e.g. with LF instead of CRLF line endings, or with attachments stored
|
|
in binary format instead of as base64. So some servers compute the
|
|
RFC822.SIZE at message arrival time. If the code is then changed (say,
|
|
the base64 encoder makes 74-character lines instead of 75) RFC822.SIZE
|
|
can be off by a little. It's regrettable.
|
|
|
|
IMO, the wise client author does not expect that size to be exact,
|
|
even though the RFC says it has to be. You can use RFC822.SIZE to
|
|
display the message size (ie. "14k" or "1.2M" or what have you), but
|
|
when you count bytes you should use the literal size.
|
|
|
|
Arnt
|
|
|