Re: GCC to Yahoo groups fails

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Hello,
>
> A while back (months), GCC stopped working when sending email using my
> yahoo account.  GCC works with other IMAP servers, even Exchange acting
> as IMAP, but not with Yahoo.  Below is the stack trace on error:
>
> ,----
> | Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> |   string-match("^[^:]+:" nil)
> |   nnimap-retrieve-group-data-early("yahoo" (nil))
> |   nnimap-request-group("INBOX" "yahoo" t nil)
> |   gnus-request-group("nnimap+yahoo:INBOX" t (nnimap "yahoo" (nnimap-address "imap.mail.yahoo.com") (nnimap-server-port 993) (nnimap-stream ssl)))
> |   gnus-inews-do-gcc()
> |   gnus-agent-possibly-do-gcc()
> |   run-hooks(message-sent-hook)
> |   message-send(nil)
> |   message-send-and-exit(nil)
> |   funcall-interactively(message-send-and-exit nil)
> |   call-interactively(message-send-and-exit nil nil)
> |   command-execute(message-send-and-exit)
> `----

This looks like an error we were discussing a bit earlier, related
nnmairix. The basic problem (as far as I can tell) is that after the
whole retrieve-group-data-early thing was added to Gnus,
`nnimap-request-group' fails if the optional "info" argument is nil.

At the time I wasn't sure what the best solution was: it seemed like
maybe the right solution was to always make sure new groups were
registered with Gnus. But your case demonstrates that nil "info"
arguments get passed in from other places in the codebase. And more
fundamentally, I'm realizing, if an argument is noted as &optional, we
should definitely treat it as optional!

If there are no objections, I'll push that change in the morning.

Eric