From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Problems with new imap-fetch-safe in XEmacs 21.4.21
Date: Tue, 06 Jan 2009 11:48:55 -0500 [thread overview]
Message-ID: <84k598fki0.fsf@incoming.verizon.net> (raw)
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
next reply other threads:[~2009-01-06 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 16:48 Dave Goldberg [this message]
2009-01-07 9:03 ` Katsumi Yamaoka
2009-01-07 15:15 ` Dave Goldberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84k598fki0.fsf@incoming.verizon.net \
--to=david.goldberg6@verizon.net \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).