Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Chris Shenton]

Two problems I've noticed with 5.8.7 since a CVS pull of the
pre-release, or maybe with 5.8.6. Seen on both FreeBSD and Solaris.

1. New nnml groups are displayed with status "*" and I can't enter
   them.

   I use procmail to file incoming mail into groups, then gnus picks
   them up. It (usually) shows the new group and I create a new
   procmail recipe and get mail in a new file/folder. But with status
   "*" when I try to enter the group it says something to the effect
   of "no such group". A look at the gnus store, which I keep under
   ~/Mail/newgroupname/", show the mail files getting populated
   properly.

   I can get into the group eventually by `K'illing the group, then
   `j'umping to the group name that I type in (e.g., nnml:list.gnus)
   which causes it to show as status "K"illed. I can `U'nkill the
   group and finally enter.  Ick.

   Is it a bug or do I need to set something to create the new groups
   as "S"ubscribed or something?


        
2. Leaves tmp files like ~/Mail/Incoming#####xyz

   Gnus since 5.8.6 or 5.8.7 CVS and now Release have been leaving
   what appears to be temporary files in the mail store area, which I
   have as ~/Mail/. The files are named "Incoming" + some number,
   (pid?) plus a few extra chars.

   These don't seem harmful, but become numerous quite quickly with a
   large amount of mail coming in. Seems like vestigial debugging
   code. It's seems to be happening in:

   nnmail.el:1633:     (concat (file-name-as-directory temp) "Incoming")))
   nnmail.el:1634: (concat (file-name-as-directory temp) "Incoming")))))

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Kevin Falcone]

>>>>> "CS" == Chris Shenton <cshenton@uucom.com> writes:

  CS>    I can get into the group eventually by `K'illing the group,
  CS>    then `j'umping to the group name that I type in (e.g.,
  CS>    nnml:list.gnus) which causes it to show as status "K"illed. I
  CS>    can `U'nkill the group and finally enter.  Ick.

What happens if you run M-g on the group? I usually have to do that on
new groups the first time.  

You might also want to look at gnus-subscribe-newsgroup-method
        
  CS>    Gnus since 5.8.6 or 5.8.7 CVS and now Release have been
  CS>    leaving what appears to be temporary files in the mail store
  CS>    area, which I have as ~/Mail/.

Yes, this is to back up your mail in case Gnus decides to have an
early lunch.  You can stop this with

(setq mail-source-delete-incoming t)

-kevin

-- 
Lasciate ogni speranza, voi ch'entrate!
			--Dante

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Cyrille Lefevre]

Chris Shenton <cshenton@uucom.com> writes:

> Two problems I've noticed with 5.8.7 since a CVS pull of the
> pre-release, or maybe with 5.8.6. Seen on both FreeBSD and Solaris.
> 
> 1. New nnml groups are displayed with status "*" and I can't enter
>    them.
> 
>    I use procmail to file incoming mail into groups, then gnus picks
>    them up. It (usually) shows the new group and I create a new
>    procmail recipe and get mail in a new file/folder. But with status
>    "*" when I try to enter the group it says something to the effect
>    of "no such group". A look at the gnus store, which I keep under
>    ~/Mail/newgroupname/", show the mail files getting populated
>    properly.
> 
>    I can get into the group eventually by `K'illing the group, then
>    `j'umping to the group name that I type in (e.g., nnml:list.gnus)
>    which causes it to show as status "K"illed. I can `U'nkill the
>    group and finally enter.  Ick.
> 
>    Is it a bug or do I need to set something to create the new groups
>    as "S"ubscribed or something?

try just g after you have created your new folder, or C-u space or return,
don't remember. I work this way, too, but w/ nnfolder :)

> 2. Leaves tmp files like ~/Mail/Incoming#####xyz

I have these, too.

Cyrille.
--
home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Chris Shenton]

On 01 Aug 2000 01:17:53 +0200, Cyrille Lefevre <clefevre@citeweb.net> said:

Cyrille> try just g after you have created your new folder, or C-u
Cyrille> space or return, don't remember. I work this way, too, but w/
Cyrille> nnfolder :)

Bummer, no luck. I did "g" like I always to to injest mail, then tried
both C-u SPACE then C-u RETURN. No joy. From the *Messages* buffer:

    Retrieving newsgroup: nnml:list.fw1-wizards@phoneboy.com...
    Opening nnml server on +nnml:list.fw1-wizards@phoneboy.com...
    Invalid group (no such directory)
    Couldn't request group nnml:list.fw1-wizards@phoneboy.com: Invalid group (no such directory)
    Retrieving newsgroup: nnml:list.fw1-wizards@phoneboy.com...
    Invalid group (no such directory)
    Couldn't request group nnml:list.fw1-wizards@phoneboy.com: Invalid group (no such directory)


But it lies:

  /export/home/cshenton/Mail/list:
  drwxr-sr-x   3 cshenton staff        512 Jul 24 09:30 fw1-wizards@phoneboy


>> 2. Leaves tmp files like ~/Mail/Incoming#####xyz

Cyrille> I have these, too.

Yikes, I have 6000 since the beginning of the July. (No wonder WAIS is
taking so long...)

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Cyrille Lefevre]

Chris Shenton <cshenton@uucom.com> writes:

> On 01 Aug 2000 01:17:53 +0200, Cyrille Lefevre <clefevre@citeweb.net> said:
> 
> Cyrille> try just g after you have created your new folder, or C-u
> Cyrille> space or return, don't remember. I work this way, too, but w/
> Cyrille> nnfolder :)
> 
> Bummer, no luck. I did "g" like I always to to injest mail, then tried
> both C-u SPACE then C-u RETURN. No joy. From the *Messages* buffer:

well, you are right, C-u something didn't work. but g works for me (I've
just made the test), at least w/ nnfolder. I don't use nnml to stay
compatible w/ other mail readers.

>     Retrieving newsgroup: nnml:list.fw1-wizards@phoneboy.com...
>     Opening nnml server on +nnml:list.fw1-wizards@phoneboy.com...
>     Invalid group (no such directory)
>     Couldn't request group nnml:list.fw1-wizards@phoneboy.com: Invalid group (no such directory)
>     Retrieving newsgroup: nnml:list.fw1-wizards@phoneboy.com...
>     Invalid group (no such directory)
>     Couldn't request group nnml:list.fw1-wizards@phoneboy.com: Invalid group (no such directory)

what says G e (group->edit->info) ?

Cyrille.
--
home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Chris Shenton]

On 01 Aug 2000 04:06:33 +0200, Cyrille Lefevre <clefevre@citeweb.net> said:

Cyrille> what says G e (group->edit->info) ?

Ah ha... I think you may have hit it here.

Why does it think the nnml-directory and active-file are under
Mail/out/ instead of just Mail?

    ;;; Editing the select method for `nnml:list.fw1-wizards@phoneboy.com'.
    ;; Type `C-c C-c' after you've finished editing.

    (nnml ""
          (nnml-get-new-mail nil)
          (nnml-inhibit-expiry t)
          (nnml-directory "~/Mail/out/")
          (nnml-active-file "~/Mail/out/active"))

Uh huh: the only place "~/Mail/out/" appears in .gnus.el is where I to
tell it what to do with archived outbound mail, per the *Info* on
Archived Messages:

  ; How does the dir implied by gnus-message-archive-group
  ; interact with the nnml-directory used by gnus-message-archive-method?
  ; if I use (nnml "FOO) I get a virtual folder nnml+FOO which makes it
  ; annoying to Bm move sent articles to normal nnml folders.

  (setq gnus-message-archive-group
        (format-time-string "out.%Y-%m" (current-time))) ; put in "out" subdir

  (setq gnus-message-archive-method
        '(nnml ""			; no "out" prefix to prevent nnml+out:
               (nnml-get-new-mail nil)	; what's it do??
               (nnml-inhibit-expiry t)
               (nnml-directory	 "~/Mail/out/") ;LC to avoid OUT and out?
               (nnml-active-file "~/Mail/out/active")
               ))

I'm guessing the assignments are NOT local to this setq. Ahhhh...
[sound of banging head, without heavy metal music]

So I can nuke the nnml-directory and nnml-active-file lines, but I'd
like to fix it: what's the right way to tell it to put archived
outbound mail in ~/Mail/out/ or ~/Mail/out.%Y-%m?

Thanks.

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Cyrille Lefevre]

Chris Shenton <cshenton@uucom.com> writes:

> On 01 Aug 2000 04:06:33 +0200, Cyrille Lefevre <clefevre@citeweb.net> said:
> 
> Cyrille> what says G e (group->edit->info) ?
> 
> Ah ha... I think you may have hit it here.

you're dead :) LOL

[snip]

>   (setq gnus-message-archive-group
>         (format-time-string "out.%Y-%m" (current-time))) ; put in "out" subdir
> 
>   (setq gnus-message-archive-method
>         '(nnml ""			; no "out" prefix to prevent nnml+out:
>                (nnml-get-new-mail nil)	; what's it do??
>                (nnml-inhibit-expiry t)
>                (nnml-directory	 "~/Mail/out/") ;LC to avoid OUT and out?
>                (nnml-active-file "~/Mail/out/active")
>                ))

I guess you *must* have the "out" prefix you get rid off.
try the original rule, such as :

   (setq gnus-message-archive-method
         '(nnml "out"			; arg! out seems to be needed ;^)
                (nnml-get-new-mail nil)	; what's it do??
                (nnml-inhibit-expiry t)
                (nnml-directory	 "~/Mail/out/") ;LC to avoid OUT and out?
                (nnml-active-file "~/Mail/out/active")
                ))

also, check all your mailbox properties if that works.

Cyrille.
--
home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Kai Großjohann]

On Mon, 31 Jul 2000, Chris Shenton wrote:

>   (setq gnus-message-archive-method
>         '(nnml ""			; no "out" prefix to prevent nnml+out:
>                (nnml-get-new-mail nil)	; what's it do??
>                (nnml-inhibit-expiry t)
>                (nnml-directory	 "~/Mail/out/") ;LC to avoid OUT and out?
>                (nnml-active-file "~/Mail/out/active")
>                ))

Careful, now.  The string foo in (nnml "foo" ...params...) is an
identifier.  You can't have two servers with the same name, ie you
can't have (nnml "foo" ...params...) twice with different parameters.

I think your gnus-secondary-select-methods entry looks like (nnml ""
...params...), and your gnus-message-archive-method entry looks like
(nnml "" ...params...), so there's a problem, here.

kai
-- 
I like BOTH kinds of music.

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[David S. Goldberg]

He also needs to ensure nnml-get-new-mail is set to nil in the archive
message.  If that's not explicitly done, I can see why that server
thinks it owns the new mail groups.
-- 
Dave Goldberg
Post: The Mitre Corporation\MS K207\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[David S. Goldberg]

>>>>> David S Goldberg (me) foolishly writes:

> He also needs to ensure nnml-get-new-mail is set to nil in the archive
> message.  If that's not explicitly done, I can see why that server
> thinks it owns the new mail groups.

Never mind.  I hadn't had my coffee yet and his explicit setting of
nnml-get-new-mail to nil completely missed me.  Sorry.
-- 
Dave Goldberg
Associate Department Head
G06A
dsg@mitre.org

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Chris Shenton]

On Tue, 01 Aug 2000 08:23:07 -0400, dsg@mitre.org (David S. Goldberg) said:

David> He also needs to ensure nnml-get-new-mail is set to nil in the
David> archive message.  If that's not explicitly done, I can see why
David> that server thinks it owns the new mail groups.  

But the problem seems to be that setting these vars even within the
definition of the archive behavior actually sets the variables that
all new groups get, as per the output from "Ge".

That's the thing that seems odd, and has caused the "can't find file"
problem: setting the active file to Mail/out/ in the archive
definition "leaked" out to affect how the attributes of newly found
mail groups and made them unreadable.

The same appeared true with the nnml-get-new-mail: the newly
found/created group had that attribute set as well. Obviously not what
I want for normal mail groups.

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Kai Großjohann]

On Tue, 01 Aug 2000, Chris Shenton wrote:

> But the problem seems to be that setting these vars even within the
> definition of the archive behavior actually sets the variables that
> all new groups get, as per the output from "Ge".

Note the name clash that I've already mentioned.

Rename one of the select methods.

kai
-- 
I like BOTH kinds of music.

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Paul Jarc]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) writes:
> Careful, now.  The string foo in (nnml "foo" ...params...) is an
> identifier.  You can't have two servers with the same name, ie you
> can't have (nnml "foo" ...params...) twice with different parameters.

Unrelated to the original problem, what about two select methods on
different backends?  Can I have (nnfoo "blah" ...) and
(nnbar "blah" ...)?


paul

Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files

[Kai Großjohann]

On Wed, 02 Aug 2000, Paul Jarc wrote:

> [...]  Can I have (nnfoo "blah" ...) and (nnbar "blah" ...)?

Yes.  I have (nnml "") and (nnimap "" ...).

kai
-- 
I like BOTH kinds of music.