Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

[Chris Shenton]

I've set up courier-imap and done telnet conversations to it to verify
login.  I haven't used Gnus IMAP before but now have in gnus.el:

  (setq
   gnus-secondary-select-methods '(
                                   (nnml "") 
                                   (nnimap "pectopah.shenton.org"
                                           (nnimap-stream ssl))
                                   )
   mail-sources '((imap	:server		"pectopah.shenton.org"
                        :fetchflag	"\\Seen")
                  ...
  )


(I don't understand the difference between the secondary-select-method
and the mail-sources above, nor in the *Info* descriptions; clues?)

Anyway, Gnus prompts for password then reports an error on the
mode-line after trying to connect; it's captured in *Messages*:

  imap: Connecting to pectopah.shenton.org...
  Waiting for response from pectopah.shenton.org...done
  imap: Connecting to pectopah.shenton.org...done
  imap: Plaintext authentication...
  Imap server pectopah.shenton.org information: Fatal error: TOO MANY CONSECUTIVE PROTOCOL VIOLATIONS: 

I can watch where it fails with tcpdump; I'll just give the ASCII
here, with login omitted:

11:27:31.137415 192.168.255.185.49233 > 192.168.255.185.imap: P
1:15(14) ack 228 win 33304 <nop,nop,timestamp 5416896 5416795> (DF)

  E..B..@.@.......
  .....Q....x.Y1.u
  .....[.......R..
  .R.[1.CAPABILITY
  ..

11:27:31.138616 192.168.255.185.imap > 192.168.255.185.49233: P
228:371(143) ack 15 win 33304 <nop,nop,timestamp 5416896 5416896> (DF)

  E.....@.@..p....
  .......QY1.u..x.
  .............R..
  .R..*.CAPABILITY
  .IMAP4rev1.UIDPL
  US.CHILDREN.NAME
  SPACE.THREAD=ORD
  EREDSUBJECT.THRE
  AD=REFERENCES.SO
  RT.QUOTA.IDLE.ST
  ARTTLS..1.OK.CAP
  ABILITY.complete
  d..


11:27:31.200605 192.168.255.185.49233 > 192.168.255.185.imap: P
61:92(31) ack 602 win 33304 <nop,nop,timestamp 5416902 5416902> (DF)

  E..S..@.@.......
  .....Q....y.Y1..
  ....(........R..
  .R..4.UID.SEARCH
  .UNSEEN.UNDELETE
  D..

11:27:31.200923 192.168.255.185.imap > 192.168.255.185.49233: P
602:664(62) ack 92 win 33304 <nop,nop,timestamp 5416902 5416902> (DF)

  E..r..@.@.......
  .......QY1....y:
  .............R..
  .R..*.SEARCH.32.
  33.34.35.36.37.3
  8.39.40.41.42..4
  .OK.SEARCH.done.
  ..

11:27:31.201304 192.168.255.185.49233 > 192.168.255.185.imap: P 92:120(28) ack 664 win 33304 <nop,nop,timestamp 5416902 5416902> (DF)

  E..P..@.@.......
  .....Q....y:Y1.)
  .....p.......R..
  .R..5.UID.FETCH.
  32.RFC822.PEEK..

11:27:31.201566 192.168.255.185.imap > 192.168.255.185.49233: P 664:712(48) ack 120 win 33304 <nop,nop,timestamp 5416902 5416902> (DF)

  E..d..@.@.......
  .......QY1.)..yV
  .............R..
  .R..5.NO.Error.i
  n.IMAP.command.r
  eceived.by.serve
  r...

If I recreate this conversation over telnet, it fails likewise

  5 uid fetch 33 rfc822 peek
  5 NO Error in IMAP command received by server.

If I remove the PEEK command, it succeeds:

  6 uid fetch 33 rfc822 
  * 2 FETCH (UID 33 RFC822 {3692}
  [... shows message...]
  )
  * 2 FETCH (FLAGS (\Seen))
  6 OK FETCH completed.

I see in the CVS logs at

  http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/lisp/imap.el?hideattic=0

there's a mention to this in Revision 1.13:

  nnimap.el (nnimap-request-article): Use BODY.PEEK[] instead of
  RFC822.PEEK if server support IMAP4rev1.
  (nnimap-request-body): Use BODY.PEEK[TEXT] instead of
  RFC822.TEXT.PEEK if server support IMAP4rev1.
  (nnimap-request-head): Use BODY.PEEK[HEADER] instead of
  RFC822.HEADER if server support IMAP4rev1.

but it doesn't seem to be using this, despite the checks for
"IMAP4rev1" in the CAPABILITY command above.

Any suggestions or clues? Thanks.

Re: Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

[Matthias Andree]

Chris Shenton <chris@shenton.org> writes:

> I've set up courier-imap and done telnet conversations to it to verify
> login.  I haven't used Gnus IMAP before but now have in gnus.el:
>
>   (setq
>    gnus-secondary-select-methods '(
>                                    (nnml "") 
>                                    (nnimap "pectopah.shenton.org"
>                                            (nnimap-stream ssl))
>                                    )
>    mail-sources '((imap	:server		"pectopah.shenton.org"
>                         :fetchflag	"\\Seen")
>                   ...
>   )
>
>
> (I don't understand the difference between the secondary-select-method
> and the mail-sources above, nor in the *Info* descriptions; clues?)

mail-sources makes Gnus download all messages from the server to the
local machine (that runs Gnus)

secondary-select-method lets Gnus keep the messages on the server
(offline capable when used with the Agent, Gnus v5.10 preferred).

> Any suggestions or clues? Thanks.

Is there something that prevents you from updating Gnus?

-- 
Matthias Andree

Re: Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

[Chris Shenton]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> mail-sources makes Gnus download all messages from the server to the
> local machine (that runs Gnus)
> 
> secondary-select-method lets Gnus keep the messages on the server
> (offline capable when used with the Agent, Gnus v5.10 preferred).

OK, excellent.

> Is there something that prevents you from updating Gnus?

Nope, I'm just using what came with the Emacs-21.3 which I've recently
installed.  Any preferred version or should I get the bleeding edge
from CVS?

Re: Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

[Matthias Andree]

On Mon, 11 Aug 2003, Chris Shenton wrote:

> Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
> 
> > mail-sources makes Gnus download all messages from the server to the
> > local machine (that runs Gnus)
> > 
> > secondary-select-method lets Gnus keep the messages on the server
> > (offline capable when used with the Agent, Gnus v5.10 preferred).
> 
> OK, excellent.
> 
> > Is there something that prevents you from updating Gnus?
> 
> Nope, I'm just using what came with the Emacs-21.3 which I've recently
> installed.  Any preferred version or should I get the bleeding edge
> from CVS?

The "bleeding edge" CVS is the current 5.10.X stable tree. If you're
going to play extra safe, get the latest 5.10.X release, the CVS stuff
also works well for me.

-- 
Matthias Andree

Re: Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

[Matthias Andree]

On Mon, 11 Aug 2003, Ted Stern wrote:

> Hi, I use CVS gnus and have one imap account i keep on the server.  I use the
> gnus-secondary-select-method style.
> 
> But for some reason my password is not read from the .authinfo file.
> 
> Do you happen to know what might be going wrong?

Works for me.

What are the permissions on ~/.authinfo?

-rw-------    1 ma       users          47 2003-08-11 23:21 /home/ma/.authinfo

.gnus excerpt:

(setq gnus-secondary-select-methods 
      '(        (nnimap "localhost"
                (nnimap-address "localhost")
                (nnimap-stream ssl))))

Re: Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

[Ted Stern]

On 11 Aug 2003, Matthias Andree wrote:
> On Mon, 11 Aug 2003, Ted Stern wrote:
>
>> Hi, I use CVS gnus and have one imap account i keep on the server.  I use
>> the gnus-secondary-select-method style.
>> 
>> But for some reason my password is not read from the .authinfo file.
>> 
>> Do you happen to know what might be going wrong?
>
> Works for me.
>
> What are the permissions on ~/.authinfo?
>
> -rw------- 1 ma users 47 2003-08-11 23:21 /home/ma/.authinfo
>
> .gnus excerpt:
>
> (setq gnus-secondary-select-methods 
>       '(        (nnimap "localhost"
>                 (nnimap-address "localhost")
>                 (nnimap-stream ssl))))

My .authinfo has the same permissions.  I ended up customizing
imap-default-username to minimize the hassle.

Ted
-- 
 Ted Stern                                 Applications Group
 Cray Inc.                               office: 206-701-2182
 411 First Avenue South, Suite 600         cell: 206-383-1049
 Seattle, WA 98104-2860                     FAX: 206-701-2500

 Frango ut patefaciam -- I break that I may reveal
 (The Paleontological Society motto, equally apropos for debugging)

Re: Gnus-v5.9.0 fails with courier-imap-2.0.0: Error in command

[Simon Josefsson]

Chris Shenton <chris@shenton.org> writes:

> I've set up courier-imap and done telnet conversations to it to verify
> login.  I haven't used Gnus IMAP before but now have in gnus.el:
>
>   (setq
>    gnus-secondary-select-methods '(
>                                    (nnml "") 
>                                    (nnimap "pectopah.shenton.org"
>                                            (nnimap-stream ssl))
>                                    )
>    mail-sources '((imap	:server		"pectopah.shenton.org"
>                         :fetchflag	"\\Seen")
>                   ...
>   )
>
>
> (I don't understand the difference between the secondary-select-method
> and the mail-sources above, nor in the *Info* descriptions; clues?)

It was explained by someone else, but let me add that you probably
doesn't want both at the same time.

> 11:27:31.201304 192.168.255.185.49233 > 192.168.255.185.imap: P 92:120(28) ack 664 win 33304 <nop,nop,timestamp 5416902 5416902> (DF)
>
>   E..P..@.@.......
>   .....Q....y:Y1.)
>   .....p.......R..
>   .R..5.UID.FETCH.
>   32.RFC822.PEEK..
>
> 11:27:31.201566 192.168.255.185.imap > 192.168.255.185.49233: P 664:712(48) ack 120 win 33304 <nop,nop,timestamp 5416902 5416902> (DF)
>
>   E..d..@.@.......
>   .......QY1.)..yV
>   .............R..
>   .R..5.NO.Error.i
>   n.IMAP.command.r
>   eceived.by.serve
>   r...

The server reject valid IMAP4, but invalid IMAP4rev1, constructs.
This is fine, and was fixed in:

> I see in the CVS logs at
>
>   http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/lisp/imap.el?hideattic=0
>
> there's a mention to this in Revision 1.13:
>
>   nnimap.el (nnimap-request-article): Use BODY.PEEK[] instead of
>   RFC822.PEEK if server support IMAP4rev1.
>   (nnimap-request-body): Use BODY.PEEK[TEXT] instead of
>   RFC822.TEXT.PEEK if server support IMAP4rev1.
>   (nnimap-request-head): Use BODY.PEEK[HEADER] instead of
>   RFC822.HEADER if server support IMAP4rev1.
>
> but it doesn't seem to be using this, despite the checks for
> "IMAP4rev1" in the CAPABILITY command above.
>
> Any suggestions or clues? Thanks.

Gnus 5.9 is too old to incorporate that patch, I guess.