Re: nnml suddenly not activating groups on startup

["Adam Sjøgren" <asjo@koldfront.dk>]

Russ writes:

> I noticed that a few nnml groups were activated by default but most
> weren't, so I inspected the group data with G E. The nnml groups that
> were activated have (nnml "") as the last element of their data. The
> ones that aren't activated have "nnml:" as the last element of their
> data. Presumably I can fix this by editing all of the group metadata
> accordingly, but I think new groups are created using the "nnml:"
> syntax.

All¹ of my mail groups have "nnml:" as the last element in
gnus-newsrc-alist.

I have a feeling that Gnus sometimes gets confused about servers that
are the same but mentioned by different definitions. Maybe going all
"nnml:" or all (nnml "") will unconfuse things?

Does your server buffer show multiple nnml-servers?


  Best regards,

    Adam


¹ Not my archive groups, though, they seem to all carry a copy of the full
server definition:
   (nnml "archive" (nnml-directory "~/Mail/archive")
         (nnml-active-file "~/Mail/archive/active")
         (nnml-get-new-mail nil)
         (nnml-inhibit-expiry t))
as the last element. That seems a little much.

-- 
 "Your father traded the tools for M&Ms again"              Adam Sjøgren
                                                       asjo@koldfront.dk