Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Shenton <cshenton@uucom.com>
Subject: Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files
Date: Tue, 01 Aug 2000 13:43:11 -0400	[thread overview]
Message-ID: <lfem48g9n4.fsf@Samizdat.uucom.com> (raw)
In-Reply-To: dsg@mitre.org's message of "Tue, 01 Aug 2000 08:23:07 -0400"

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.



  parent reply	other threads:[~2000-08-01 17:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-31 13:19 Chris Shenton
2000-07-31 22:53 ` Kevin Falcone
2000-07-31 23:17 ` Cyrille Lefevre
2000-07-31 23:36   ` Chris Shenton
2000-08-01  2:06     ` Cyrille Lefevre
2000-08-01  2:52       ` Chris Shenton
2000-08-01  3:15         ` Cyrille Lefevre
2000-08-01  7:37         ` Kai Großjohann
2000-08-01 12:23           ` David S. Goldberg
2000-08-01 13:33             ` David S. Goldberg
2000-08-01 17:43             ` Chris Shenton [this message]
2000-08-02  8:31               ` Kai Großjohann
2000-08-02 14:49           ` Paul Jarc
2000-08-02 19:24             ` Kai Großjohann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=lfem48g9n4.fsf@Samizdat.uucom.com \
    --to=cshenton@uucom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).