RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (3)

RFC 4550, "Internet Email to Support Diverse Service Environments (Lemonade) Profile", June 2006

Note: This RFC has been obsoleted by RFC 5550

Source of RFC: lemonade (app)

Errata ID: 59

Status: Verified
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2006-08-11
Verifier Name: Alexey Melnikov
Date Verified: 2009-07-06

Section 1.1 says:

   In particular, examples assume that Lemonade
   Submit and IMAP servers support all Lemonade extensions described in
   this document, so they don't show how to deal with absence of an
   extension.

It should say:

   In particular, examples assume that Lemonade
   Submit and IMAP servers support all Lemonade extensions described in
   this document, so they don't show how to deal with the absence of an
   extension.

Notes:

missing article

Errata ID: 736

Status: Verified
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2006-08-11

Section 9.2 says:

   [IMAP-DISC] Melnikov, A., "Synchronization operations for
               disconnected IMAP4 clients", Work in Progress, October
               2004.

It should say:

   [IMAP-DISC] Melnikov, A., Ed., "Synchronization Operations for 
               Disconnected IMAP4 Clients", RFC 4549, June 2006.



Notes:

This I-D has been published -- synchronized with RFC 4550 -- as RFC 4549.

from pending

Errata ID: 1767

Status: Verified
Type: Editorial

Reported By: Tony Hansen
Date Reported: 2009-04-16
Verifier Name: Alexey Melnikov
Date Verified: 2009-07-06

Section 2.4.1, 2.4.2 says:

S: a002 OK URLFETCH completed
I: a003 LOGOUT
S: * BYE See you later
S: a003 OK Logout successful

It should say:

I: a002 OK URLFETCH completed
S: a003 LOGOUT
I: * BYE See you later
I: a003 OK Logout successful

Notes:

According to section 1.1 (Conventions Used in This Document):
In examples, "M:", "I:", and "S:" indicate lines sent by the client
messaging user agent, IMAP e-mail server, and SMTP submit server,
respectively.

The exact same error appears in both sections 2.4.1 and 2.4.2.

Report New Errata