On Wed, Sep 29 2010, Dave Goldberg wrote:

> Well it certainly does do the GCC, but I get this backtrace after the message is written:
>
> Debugger entered--Lisp error: (wrong-type-argument number-char-or-marker-p nil)
>   gnus-add-to-range(((1 . 96703)) (nil))
>   gnus-compute-read-articles("nnimap+cyrus:INBOX.in-box" (nil))
>   gnus-group-make-articles-read("nnimap+cyrus:INBOX.in-box" (nil))
>   gnus-group-mark-article-read("nnimap+cyrus:INBOX.in-box" nil)
>   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)
>
> I guess this is triggered by my having gnus-gcc-mark-as-read set to t?

Same backtrace here, but I use Dovecot. ;)

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info