From: jerome.marant@free.fr (Jérôme Marant)
Subject: Re: Using nnimap
Date: 21 Aug 2001 11:57:46 +0200 [thread overview]
Message-ID: <7zn14t3fc5.fsf@amboise.ird.idealx.com> (raw)
In-Reply-To: <vafk7zxep69.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Do you really get INBOX, or is it nnimap:INBOX, or nnimap+Free:INBOX?
> Please be precise.
I'm sorry to bother you with this.
I do connect to the server (typing login and password) and then
when I type A A, I get:
*:INBOX
*:INBOX/sent-mail
*:nndraft.nndraft
>
> > From the Group buffer, type ^. Do you see more than one nnimap server
> there?
>
> Ah, oh. I now remember that nnimap is your primary select method.
> Then, of course, you will see INBOX.
Are primary and secondary select method conceptually different?
What's the difference?
> Please say precisely in extremely long-winded boring detail what
> happens. I don't know what you mean by "nothing". I'm sure that
> Emacs will react in _some_ way when you use C-u RET.
After typing "A A", I do subscribe to INBOX with "u".
Then, I do "L" and I can see INBOX in the susbribed groups list.
0:INBOX
When I type "g" or "M-g" on INBOX, gnus tells me that there are no
news.
When I use C-u RET on INBOX, gnus tells me that it cannot enter
the Group.
> It's supposed to be simple. It looks as if you did everything right.
> I don't know what might be wrong.
I tried:
(setq gnus-message-archive-method
'(nnimap "Free"))
but I don't know if this is mandatory and it did not change anything
anyway.
>
> Normally, adding (nnimap "" ...) to gnus-secondary-select-methods
> should be enough.
>
> The only unusual thing I see is that you put (nnimap ...) in
> gnus-select-method, so nnimap is your native server. Maybe not many
> people have tested this. It has happened before that some things
> don't work so well when nnml or nnimap are used as native server.
I will try to use it as a secondary method.
BTW, what was problematic in nnimap as a primary method?
Thanks.
--
Jérôme MARANT
next prev parent reply other threads:[~2001-08-21 9:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 18:02 Jérôme Marant
2001-08-19 16:25 ` Kai Großjohann
2001-08-19 16:42 ` Jérôme Marant
2001-08-19 22:59 ` Kai Großjohann
2001-08-21 8:01 ` Jérôme Marant
2001-08-21 9:29 ` Kai Großjohann
2001-08-21 9:57 ` Jérôme Marant [this message]
2001-08-21 12:12 ` Kai Großjohann
2001-08-21 12:32 ` Jérôme Marant
2001-08-21 13:11 ` Kai Großjohann
2001-08-22 7:44 ` Jérôme Marant
2001-08-22 8:51 ` Simon Josefsson
2001-08-23 7:52 ` Jérôme Marant
2001-08-22 19:22 ` Kai Großjohann
2001-08-23 7:58 ` Jérôme Marant
2001-08-23 15:52 ` Kai Großjohann
2001-08-24 7:21 ` Jérôme Marant
2001-08-24 17:34 ` Jim Davidson
2001-08-24 23:35 ` Jérôme Marant
2001-08-24 21:48 ` Simon Josefsson
2001-08-25 17:32 ` Roland Mas
2001-08-25 17:47 ` Simon Josefsson
2001-08-27 17:37 ` Jim Davidson
2001-08-21 15:08 ` Jody Klymak
2001-08-21 15:52 ` Kai Großjohann
-- strict thread matches above, loose matches on Subject: below --
2000-03-07 18:06 using nnimap Arcady Genkin
2000-03-07 19:41 ` Simon Josefsson
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=7zn14t3fc5.fsf@amboise.ird.idealx.com \
--to=jerome.marant@free.fr \
/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).