From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Agent problems with nnimap
Date: Sun, 06 Oct 2002 02:51:04 +0200 [thread overview]
Message-ID: <ilu8z1c1jbb.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87ptuoijjn.fsf@crybaby.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sun, 06 Oct 2002 00:54:04 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Somebody said, and I think he's right, that it doesn't work right to
> have nnimap groups in the "default" Agent category. So I created an
> "imap" category and put my nnimap groups there. That seems to work.
Why doesn't nnimap work in the default agent category? Was it that J
u doesn't work? If so, I can't reproduce it. I only have the default
agent category set to `true' and J u works for me.
next prev parent reply other threads:[~2002-10-06 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 22:54 Kai Großjohann
2002-10-06 0:51 ` Simon Josefsson [this message]
2002-10-06 8:24 ` Kai Großjohann
2002-10-20 20:00 ` Kai Großjohann
2002-10-07 16:16 ` Wes Hardaker
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=ilu8z1c1jbb.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).