Commit 89c7c751 89c7c751144959bca61dd43250348b68599613cc by Alain Magloire

Typos in Changelog.

1 parent d3fc411b
...@@ -5,12 +5,19 @@ ...@@ -5,12 +5,19 @@
5 i.e POP3, IMAP4, the entire message may not have been dowloaded yet. 5 i.e POP3, IMAP4, the entire message may not have been dowloaded yet.
6 IMAP is very susceptible on the size, example: 6 IMAP is very susceptible on the size, example:
7 A003 APPEND saved-messages (\Seen) {310} 7 A003 APPEND saved-messages (\Seen) {310}
8 Date: Mon, 7 Feb 1994 21:52:25 -0800 (PST)
9 From: Fred Foobar <foobar@Blurdybloop.COM>
10 Subject: afternoon meeting
11 To: mooch@owatagu.siam.edu
12 Message-Id: <B27397-0100000@Blurdybloop.COM>
13 MIME-Version: 1.0
14 ......
8 (1) If the IMAP4 server does not get the right size advertise in the 15 (1) If the IMAP4 server does not get the right size advertise in the
9 string literal, it will misbehave. 16 string literal, it will misbehave.
10 (2) Since we are assuming that the message will be in (unix)native 17 (2) Since we are assuming that the message will be in (unix)native
11 file system format meaning ending with NEWLINE, we will have 18 file system format meaning ending with NEWLINE, we will have
12 to do some calculations about the RFC822.SIZE of the message. 19 to do some calculations about the RFC822.SIZE of the message.
13 (3) As pointed about, it is not possible to rely on message_size() 20 (3) As pointed above, it is not possible to rely on message_size()
14 nor message_lines() to return the right count and even missing by 21 nor message_lines() to return the right count and even missing by
15 one can be deadly. 22 one can be deadly.
16 So we download the message to a floating message to guaranty that 23 So we download the message to a floating message to guaranty that
......