[gnus.gnus-bug] nnimap: STATUS arguments in lowercase

[gnus.gnus-bug] nnimap: STATUS arguments in lowercase

[Linus Nordberg]

[-- Attachment #1: Type: text/plain, Size: 134 bytes --]

Hi,

Attached message was sent to bugs@gnus.org a couple of days ago.
Maybe someone on this list knows more about nnimap?

-- 
Linus


[-- Attachment #2: Type: message/rfc822, Size: 6853 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 609 bytes --]

Oort Gnus v0.24
GNU Emacs 21.3.1 (i386--freebsd, X toolkit, Xaw3d scroll bars)
 of 2003-06-15 on fluff

Hi,

The second argument to the STATUS command, the "status data items", is
sent in lower case.  GNU Mailutils imap4d (and at least one other IMAP
server) is unhappy with this and returns "BAD STATUS Too few args
(empty list)".

Example of failure:
  191 STATUS "INBOX" (uidvalidity uidnext unseen)
  191 BAD STATUS Too few args (empty list)

Example of success:
  191 STATUS "INBOX" (UIDVALIDITY UIDNEXT UNSEEN)
  * STATUS INBOX (UIDVALIDITY 1064340696 UIDNEXT 2 UNSEEN 0 )
  191 OK STATUS Completed





[-- Attachment #2.1.2: User settings --]
[-- Type: application/emacs-lisp, Size: 4576 bytes --]

Re: [gnus.gnus-bug] nnimap: STATUS arguments in lowercase

[Simon Josefsson]

Linus Nordberg <linus@nordberg.se> writes:

> Hi,
>
> Attached message was sent to bugs@gnus.org a couple of days ago.
> Maybe someone on this list knows more about nnimap?
...
> The second argument to the STATUS command, the "status data items", is
> sent in lower case.  GNU Mailutils imap4d (and at least one other IMAP
> server) is unhappy with this and returns "BAD STATUS Too few args
> (empty list)".
>
> Example of failure:
>   191 STATUS "INBOX" (uidvalidity uidnext unseen)
>   191 BAD STATUS Too few args (empty list)
>
> Example of success:
>   191 STATUS "INBOX" (UIDVALIDITY UIDNEXT UNSEEN)
>   * STATUS INBOX (UIDVALIDITY 1064340696 UIDNEXT 2 UNSEEN 0 )
>   191 OK STATUS Completed

I believe this is a bug in those servers, see RFC 3501 and in
particular the last sentence of quoted text below.  What version of
imap4d?  What was the other server?

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
        particular:

        (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.

Re: [gnus.gnus-bug] nnimap: STATUS arguments in lowercase

[Linus Nordberg]

Simon Josefsson <jas@extundo.com> wrote
Sat, 27 Sep 2003 00:31:00 +0200:

|  I believe this is a bug in those servers, see RFC 3501 and in
|  particular the last sentence of quoted text below.  What version of
|  imap4d?  What was the other server?

Thanks.

It's current imap4d from CVS.

When I looked into it closer, "the other server" was actually two
other servers and none of them did suffer from this particular
problem.  I will report them separately.

-- 
Linus