Problems with new imap-fetch-safe in XEmacs 21.4.21

Problems with new imap-fetch-safe in XEmacs 21.4.21

[Dave Goldberg]

I get the following on GCC to an Exchange 2007 mailbox now.  The GCC
actually does succeed but the error is annoying nonetheless.  Lisp backtrace:

Debugger entered--Lisp error: (wrong-type-argument numberp "*:*")
  signal(wrong-type-argument (numberp "*:*"))
  byte-code("..." [receive props uids buffer imap-enable-exchange-bug-workaround data string-match "The specified message set is invalid" make-local-variable t imap-fetch signal nouidfetch] 5)
  imap-fetch-safe(("*" "*:*") "UID")
  imap-message-appenduid-1("Sent Items")
  imap-message-append("Sent Items" #<buffer " *acc*"> nil nil " *nnimap* imc")
  nnimap-request-accept-article("Sent Items" "imc" t)
  gnus-request-accept-article("nnimap+imc:Sent Items" "nnimap:imc" t t)
  gnus-inews-do-gcc()
  gnus-agent-possibly-do-gcc()
  run-hooks(gnus-agent-possibly-do-gcc)
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit)

Please let me know if there is anything else I can do to help debug this.

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net

Re: Problems with new imap-fetch-safe in XEmacs 21.4.21

[Katsumi Yamaoka]

>>>>> Dave Goldberg wrote:
> I get the following on GCC to an Exchange 2007 mailbox now.  The GCC
> actually does succeed but the error is annoying nonetheless.  Lisp backtrace:

> Debugger entered--Lisp error: (wrong-type-argument numberp "*:*")
>   signal(wrong-type-argument (numberp "*:*"))
>   byte-code("..." [receive props uids buffer imap-enable-exchange-bug-workaround data string-match "The specified message set is invalid" make-local-variable t imap-fetch signal nouidfetch] 5)
>   imap-fetch-safe(("*" "*:*") "UID")
>   imap-message-appenduid-1("Sent Items")

[...]

The first argument passed to `imap-fetch-safe' seems to have to
be a cons, not a list.  If that is a list, it is passed to
`number-to-string' by way of `imap-list-to-message-set' and
causes the `wrong-type-argument' error.  This is no more than a
guess since I don't use IMAP, but here is a patch:

--8<---------------cut here---------------start------------->8---
--- imap.el~	2009-01-04 21:39:51 +0000
+++ imap.el	2009-01-07 09:02:11 +0000
@@ -1870,7 +1870,7 @@
 	  (imap-message-data (make-vector 2 0)))
       (when (imap-mailbox-examine-1 mailbox)
 	(prog1
-	    (and (imap-fetch-safe '("*" "*:*") "UID")
+	    (and (imap-fetch-safe '("*" . "*:*") "UID")
 		 (list (imap-mailbox-get-1 'uidvalidity mailbox)
 		       (apply 'max (imap-message-map
 				    (lambda (uid prop) uid) 'UID))))
--8<---------------cut here---------------end--------------->8---

Re: Problems with new imap-fetch-safe in XEmacs 21.4.21

[Dave Goldberg]

>>>>> On Wed, 07 Jan 2009 18:03:24 +0900, Katsumi Yamaoka <yamaoka@jpl.org> #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( said:

>>>>> Dave Goldberg wrote:
>> I get the following on GCC to an Exchange 2007 mailbox now.  The GCC
>> actually does succeed but the error is annoying nonetheless.  Lisp backtrace:

>> Debugger entered--Lisp error: (wrong-type-argument numberp "*:*")
>> signal(wrong-type-argument (numberp "*:*"))
>> byte-code("..." [receive props uids buffer imap-enable-exchange-bug-workaround data string-match "The specified message set is invalid" make-local-variable t imap-fetch signal nouidfetch] 5)
>> imap-fetch-safe(("*" "*:*") "UID")
>> imap-message-appenduid-1("Sent Items")

> [...]

> The first argument passed to `imap-fetch-safe' seems to have to
> be a cons, not a list.  If that is a list, it is passed to
> `number-to-string' by way of `imap-list-to-message-set' and
> causes the `wrong-type-argument' error.  This is no more than a
> guess since I don't use IMAP, but here is a patch:

[...]

The patch solved the problem for me.  Thanks!

-- 
Dave Goldberg
david.goldberg6@verizon.net