mailing list archives

meli community discussions

⚠️ if something does not work as intended when interracting with the mailing lists,
reach out Github mirror Gitea repo @epilys:matrix.org

[Imap-protocol] RFC4551 text issues

E-mail headers
From: Greg Banks <gnb@fastmail.fm>
To: imap-protocol@u.washington.edu
Date: Fri, 08 Jun 2018 12:34:45 -0000
Message-ID: 4DC7ADAE.3050807@fastmail.fm permalink / raw / eml / mbox 
G'day,

I've been reading RFC4551 and noticed the following issues.

1.  The modifier UNCHANGEDSINCE is misspelt UNCHANGESINCE (note the 
missing 'D') four times in section 3.2.

2.  The abnf says

    resp-text-code      =/ "HIGHESTMODSEQ" SP mod-sequence-value /
                           "NOMODSEQ" /
                           "MODIFIED" SP set

There is no abnf rule for "set" in either RFC3501 or RFC4551.  However 
the rule "sequence-set" in RFC3501 seems to match the examples given 
earlier in RFC4551 and the apparent intent.

-- 
Greg.
Reply
E-mail headers
From: alexey.melnikov@isode.com
To: imap-protocol@localhost
Date: Fri, 08 Jun 2018 12:34:46 -0000
Message-ID: 4DDE9002.1010800@isode.com permalink / raw / eml / mbox 
Greg Banks wrote:

> G'day,

Hi Greg,
Thanks for reporting this.

> I've been reading RFC4551 and noticed the following issues.
>
> 1.  The modifier UNCHANGEDSINCE is misspelt UNCHANGESINCE (note the 
> missing 'D') four times in section 3.2.

Good point.

> 2.  The abnf says
>
>    resp-text-code      =/ "HIGHESTMODSEQ" SP mod-sequence-value /
>                           "NOMODSEQ" /
>                           "MODIFIED" SP set
>
> There is no abnf rule for "set" in either RFC3501 or RFC4551.  However 
> the rule "sequence-set" in RFC3501 seems to match the examples given 
> earlier in RFC4551 and the apparent intent.

Indeed.

Can you submit both of this using the Errata submission 
<http://www.rfc-editor.org/errata.php>? (Using the "Report New Errata" 
button)

Thanks,
Alexey
Reply