Re: gnorb can't find moved messages

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Bob Newell <bobnewell@bobnewell.net> writes:

> This problem also arose for me when I very first started to
> use Gnorb, and also surprised me as I thought the registry
> would act as a sort of invariant pointer. However, it didn't.

Thanks to both of you -- it looks to me like the problem is in
`gnorb-follow-gnus-link', not the registry. I've noticed that sometimes
if you follow Gnus message links, you get into a Summary buffer that
includes a bogus (None) message. Usually nothing happens with that, but
in this case it looks like Gnorb tries to start a reply to that bogus
message.

In my brief testing, it only happens the first time you try it. After
the first time Gnorb correctly finds the moved message, and starts a
reply to it. I have no idea why, I assume some caching is going on.
Anyway, I will try to fix `gnorb-follow-gnus-link' so it doesn't do
that.

> It came up because I use gmail as my primary service and use
> gnus to access with IMAP (with no local storage). Gmail has a
> funny sort of structure where everything appears in the "All
> Mail" folder as well as possibly in one or more individual
> folders (really tags, but it works like folders).
>
> Generally what I do is "archive" my "inbox" mail when I'm done
> with it. All that does is remove the "inbox" tag, leaving the
> "All Mail" tag in place. But if I had marked the mail for
> tracking with Gnorb while in the inbox, which seems the normal
> way to do things (act on the mail before archiving), the
> org-mode link would be set to "inbox". After archiving, the
> link would be broken.

This isn't quite the same thing -- org-mode links hard-code the group
name, so if you move the message Org won't be able to find it again.
That doesn't have anything to do with Gnorb.