[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-mailutils] [imap4d] Upper/lower case

From: Linus Nordberg
Subject: Re: [bug-mailutils] [imap4d] Upper/lower case
Date: Sat, 27 Sep 2003 16:53:51 +0200
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386--freebsd)

Linus Nordberg <address@hidden> wrote
Fri, 26 Sep 2003 22:21:18 +0200:

|  What's "correct" here?  Would it be reasonable for the server to
|  accept lower case args (or "status data items") in this case.  Example
|  below.

Based on Simon Josefssons reply on another list, see below, I suggest
the attached patch.

BTW, is it ok to use strcasecmp(3) just like that?

--8<---------------cut here---------------start------------->8---
From: Simon Josefsson <address@hidden>
Subject: Re: [gnus.gnus-bug] nnimap: STATUS arguments in lowercase
I believe this is a bug in those servers, see RFC 3501 and in
particular the last sentence of quoted text below.  [...]

9.      Formal Syntax

   The following syntax specification uses the Augmented Backus-Naur
   Form (ABNF) notation as specified in [ABNF].

   In the case of alternative or optional rules in which a later rule
   overlaps an earlier rule, the rule which is listed earlier MUST take
   priority.  For example, "\Seen" when parsed as a flag is the \Seen
   flag name and not a flag-extension, even though "\Seen" can be parsed
   as a flag-extension.  Some, but not all, instances of this rule are
   noted below.

        Note: [ABNF] rules MUST be followed strictly; in

        (1) Except as noted otherwise, all alphabetic characters
        are case-insensitive.  The use of upper or lower case
        characters to define token strings is for editorial clarity
        only.  Implementations MUST accept these strings in a
        case-insensitive fashion.
--8<---------------cut here---------------end--------------->8---


Attachment: patch.status.1
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]