Re: nnmairix problem after nnmaildir -> nnimap switch

[David Engster <deng@randomsample.de>]

Dan Davison <davison@stats.ox.ac.uk> writes:
> David Engster <deng@randomsample.de> writes:
>> To get rid of an existing nnmairix server, you just have to delete *all*
>> existing nnmairix groups and restart Gnus. 
>
> Thanks David. That worked, and I was making progress, but I've now hit a
> similar problem. For reasons I won't attempt to justify I now have two
> nnmairix servers configured

Actually, I'm pretty happy that someone is using more than one
server. That feature required quite some coding...

>  and I want to get rid of them and make a clean start. So my server
> buffer looks like
>
>      {nnfolder:archive} (opened)
>      {nnmairix:general} (opened)
>      {nnmairix:gen} (opened)
>      {nnimap:dc} (opened)
>
> No mairix groups appear in the group buffer as they are empty.  What
> exactly do I have to do to make these nnmairix servers go away? I can
> force mairix groups to appear by subscribing to them with
> gnus-server-read-server followed by
> gnus-browse-unsubscribe-current-group, and then I can kill them. But
> the two nnmairix servers persist after restarting gnus (whether or not
> I use gnus-server-close-server to close the servers before restarting
> gnus).

Well, there must still be nnmairix groups lying around. You can see the
name of the groups of the nnmairix server in the minibuffer be
evaluating

(nnmairix-get-groups-from-server "general")

and

(nnmairix-get-groups-from-server "gen")

Remember to hit "L" in the group buffer to see all groups. If you really
don't see those groups, try evaluating

(progn
 (switch-to-buffer gnus-group-buffer)
 (gnus-group-jump-to-group "nnmairix+general:GROUPNAME"))

and it should jump to the group GROUPNAME, so that you can kill it.

Regards,
David