From: Harry Putnam <reader@newsguy.com>
Subject: Re: Server loses `agent' status
Date: Fri, 19 Dec 2003 08:17:32 -0600 [thread overview]
Message-ID: <m3llp8c2o3.fsf@newsguy.com> (raw)
In-Reply-To: <plop871xr2txo7.fsf@gnu-rox.org>
Xavier Maillard <zedek@gnu-rox.org> writes:
> I am using a yesterday copy of Gnus cvs and all is working quite well
> here. What's more nntp are *by default* agentized so I don't really
> understand why for you it doesn't react that way.
>
> Can you post your configuration or report a bug using the dedicated
> function so we probably could see what is wrong ?
I will post a recap but currently one of the developers is working on
this and I'm trying to assist.
One point though. Although the `agent' flag does not stay thru a
restart, agent behavior does continue. That is. If I press `g', the
groups on that server that are in my `true' category are downloaded
in agent fashion.
next prev parent reply other threads:[~2003-12-19 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 12:09 Harry Putnam
2003-12-16 14:32 ` Kevin Greiner
2003-12-17 2:52 ` Harry Putnam
2003-12-17 16:32 ` Harry Putnam
2003-12-18 7:03 ` Xavier Maillard
2003-12-19 14:17 ` Harry Putnam [this message]
2003-12-22 21:10 ` FIXED: " Kevin Greiner
2003-12-24 0:02 ` Harry Putnam
2003-12-18 7:00 ` Xavier Maillard
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=m3llp8c2o3.fsf@newsguy.com \
--to=reader@newsguy.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).