workaround/ugly hack for IMAP4 capability reporting



One-n-all, 
please try this for a workaround (aka very ugly 2am hack) if you have
an "older" imap4 only server:


--- imap.c	Tue Feb 26 02:42:45 2002
+++ imap.c.new	Tue Mar  5 02:16:04 2002
@@ -318,8 +318,9 @@
     return -1;
   }
 
-  if (!(mutt_bit_isset(idata->capabilities,IMAP4)
-      ||mutt_bit_isset(idata->capabilities,IMAP4REV1)))
+  if (! ( /*       mutt_bit_isset(idata->capabilities,IMAP4)  */
+       (idata->capabilities[0] > 1) /* if bit 0 is set then we are > 1 by definition */
+       ||mutt_bit_isset(idata->capabilities,IMAP4REV1)))
   {
     mutt_error _("This IMAP server is ancient. Mutt does not work with it.");
     mutt_sleep (2);	/* pause a moment to let the user see the error */



--- message.c	Tue Feb 26 02:42:45 2002
+++ message.c.new	Tue Mar  5 02:05:44 2002
@@ -69,7 +69,8 @@
     snprintf (hdrreq, sizeof (hdrreq), "BODY.PEEK[HEADER.FIELDS (%s)]", 
       want_headers); 
   } 
-  else if (mutt_bit_isset (idata->capabilities,IMAP4))
+  else if /*(mutt_bit_isset (idata->capabilities,IMAP4))*/
+    (idata->capabilities[0] > 1)
   {
     snprintf (hdrreq, sizeof (hdrreq), "RFC822.HEADER.LINES (%s)", 
       want_headers);


Carlos has just pointed out a fix in mutt's cvs tree at
http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvs/gnome&subdir=balsa/libmutt/imap&command=DIFF_FRAMESET&root=/cvs/gnome&file=command.c&rev1=1.14&rev2=1.15

but this might help you if you cannot wait for it to propagate ;|

cheers all,
James
(now I can sleep.....)



-- 
TSG Engineer (Kernel/Storage)           828 Pacific Highway
APAC Customer Care Centre               Gordon NSW 
Sun Microsystems Australia              2072

Failfast panic: those controlling voices in my head have 
stopped telling me what to do.....

Read about the VOS Initiative at http://www.vosinitiative.com




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