On 03/23/05(04:16) you "Jayme Cox" <jayme.cox@kabira..> wrote
in <_A2865@delegate-en.ML_>
 |I'm getting the following error when I try to fetch the body of a message using
 |IMAP and Thunderbird:
 |
 |03/22 00:36:42.15 C: 30 UID fetch 2301 (UID RFC822.SIZE RFC822.peek)
 |03/22 00:36:42.15 S: 30 BAD Bogus attribute list in UID FETCH
 |
 |However, if I connect to the IMAP server directly, it works ok.
 |
 |I know RFC822.PEEK has been obsoleted, but it only fails when going thru
 |delegated... Is there a workaround?

I tested Thunderbird with an IMAP server on my Linux machine, but
could not encounter an error.  I invoked my DeleGate like this:

  % delegated -P9999 SERVER=imap

then connected to this DeleGate from Thunderbird with account name
"y.sato@localhost".  The relevant lines in logfile is like this:

  03/24 07:10:15.15 [6039] 1+0: D: * OK localhost Proxy IMAP4 server DeleGate/8.11.2^M
  03/24 07:10:15.16 [6039] 1+0: C: 1 login "y.sato@localhost.." ****
  03/24 07:10:15.16 [6039] 1+0: IMAP LOGIN  "y.sato" @ localhost.localdomain:143
  03/24 07:10:15.18 [6039] 1+0: ConnectToServer connected [8] {192.168.1.111:143 <- 192.168.1.111:55341} [0.022s]
  03/24 07:10:15.18 [6039] 1+0: >>>> * OK [CAPABILITY IMAP4 IMAP4REV1 STARTTLS LOGIN-REFERRALS AUTH=LOGIN] localhost IMAP4rev1 2000.283rh at Thu, 24 Mar 2005 07:10:15 +0900 (JST)^M
  03/24 07:10:15.18 [6039] 1+0: >>>> 1 login "y.sato" ****
  03/24 07:10:15.18 [6039] 1+0: willSTLS_SV: ServerFlags=10
  03/24 07:10:15.20 [6039] 1+0: S: 1 OK LOGIN completed^M
  03/24 07:10:15.20 [6039] 1+0: OK IMAP-LOGIN FROM -@ysimac..:49464 TO y.sato@localhost..
  03/24 07:10:15.20 [6039] 1+0: C: 2 select "INBOX"^M
  03/24 07:10:15.23 [6039] 1+0: S: 2 OK [READ-WRITE] SELECT completed^M
  03/24 07:10:15.23 [6039] 1+0: C: 3 UID fetch 1:* (FLAGS)^M
  03/24 07:10:15.23 [6039] 1+0: S: 3 OK UID FETCH completed^M
  03/24 07:10:15.24 [6039] 1+0: C: 4 UID fetch 779 (UID RFC822.SIZE BODY[])^M
  03/24 07:10:15.24 [6039] 1+0: S: 4 OK UID FETCH completed^M

Like above , my Thunderbird uses BODY[] instead of RFC822.peek.
So I think the problem depends on the negotiation phase in IMAP protocol.
If it is the problem of "CAPABILITY" command, then it might be fixed
with a patch like enclosed.

Cheers,
Yutaka
--
  D G   Yutaka Sato <pfqcabdyi-mxhgu464633w.ml@delegate.org> http://delegate.org/y.sato/
 ( - )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller


*** dist/delegate8.11.1/src/imap.c	Tue Mar  1 08:37:02 2005
--- src/imap.c	Thu Mar 24 07:03:12 2005
***************
*** 190,196 ****
--- 190,201 ----
  /*
  				fprintf(tc,"* CAPABILITY IMAP4 AUTH-LOGIN\r\n");
  */
+ /*
  				fprintf(tc,"* CAPABILITY IMAP4 AUTH-LOGIN");
+ */
+ 				fprintf(tc,"* CAPABILITY IMAP4");
+ 				fprintf(tc," IMAP4rev1");
+ 				fprintf(tc," AUTH-LOGIN");
  				if( willSTLS_CL(Conn) ){
  					fprintf(tc," STARTTLS");
  				}