Setting up Gnus with IMAP

Setting up Gnus with IMAP

[Sebastian Kaps]

Hi!

I'm trying to use Gnus with IMAP.
I've read Robin's HOWTO on my.gnus.org, but something doesn't work. When
I launch Gnus and type "^" to enter the server buffer, I see this:
,----
|      {nnimap:192.168.1.2} (denied)
`----

My setup looks like this:
,----
| (setq
|  gnus-select-method '(nntp "192.168.1.2")
|  gnus-secondary-select-methods '((nnml "")
| 				 (nnimap "192.168.1.2"
| 					 (nnimap-address "192.168.1.2")
| 					 (nnimap-server-port "143")
| 					 (nnimap-authenticator "login")
| 					 (nnimap-expunge-on-close "never")
| 					 (nnimap-authinfo-file "~/.authinfo")
| 					 (nnimap-stream "network")
| 					 )))
| (setq imap-debug "*imap-debug*")
| (setq imap-log "*imap-log*")
| (setq nnimap-debug "*nnimap-debug*")
`----

and the logs:

,----[ *nnimap-debug* ]
| ======================================================================
| 1 -> nnimap-server-opened: server="192.168.1.2"
| 1 <- nnimap-server-opened: nil
| ======================================================================
| 1 -> nnimap-open-server: server="192.168.1.2" defs=((nnimap-address "192.168.1.2") (nnimap-server-port "143") (nnimap-authenticator "login") (nnimap-expunge-on-close "never") (nnimap-authinfo-file "~/.authinfo") (nnimap-stream "network"))
| | 2 -> nnimap-server-opened: server="192.168.1.2"
| | 2 <- nnimap-server-opened: nil
| | 2 -> nnimap-open-connection: server="192.168.1.2"
| | 2 <- nnimap-open-connection: nil
| 1 <- nnimap-open-server: nil
| ======================================================================
| 1 -> nnimap-server-opened: server="192.168.1.2"
| 1 <- nnimap-server-opened: nil
| ======================================================================
| 1 -> nnimap-open-server: server="192.168.1.2" defs=((nnimap-address "192.168.1.2") (nnimap-server-port "143") (nnimap-authenticator "login") (nnimap-expunge-on-close "never") (nnimap-authinfo-file "~/.authinfo") (nnimap-stream "network"))
| | 2 -> nnimap-server-opened: server="192.168.1.2"
| | 2 <- nnimap-server-opened: nil
| | 2 -> nnimap-open-connection: server="192.168.1.2"
| | 2 <- nnimap-open-connection: nil
| 1 <- nnimap-open-server: nil
`----

,----[ *imap-debug* ]
| | 2 -> imap-opened: buffer=" *nnimap* 192.168.1.2"
| | 2 <- imap-opened: nil
| | | 3 -> imap-open: server="192.168.1.2" port="143" stream="network" auth="login" buffer=" *nnimap* 192.168.1.2"
| | | | 4 -> imap-opened: buffer=" *nnimap* 192.168.1.2"
| | | | 4 <- imap-opened: nil
| | | | 4 -> imap-open-1: buffer=" *nnimap* 192.168.1.2"
| | | | 4 <- imap-open-1: nil
| | | 3 <- imap-open: nil
| | 2 -> imap-opened: buffer=" *nnimap* 192.168.1.2"
| | 2 <- imap-opened: nil
| | | 3 -> imap-open: server="192.168.1.2" port="143" stream="network" auth="login" buffer=" *nnimap* 192.168.1.2"
| | | | 4 -> imap-opened: buffer=" *nnimap* 192.168.1.2"
| | | | 4 <- imap-opened: nil
| | | | 4 -> imap-open-1: buffer=" *nnimap* 192.168.1.2"
| | | | 4 <- imap-open-1: nil
| | | 3 <- imap-open: nil
`----

Any clues?

-- 
Ciao, Sebastian

Re: Setting up Gnus with IMAP

[Simon Josefsson]

Sebastian Kaps <seb-dated-1058345066.f5d54a@toyland.sauerland.de> writes:

> // Kai Großjohann writes:
>
>> IMHO it doesn't make sense to specify so many values which are the
>> default anyhow.  For example, should the port be "143" or 143?
>> Should the authenticator be "login" or login?  Etc pp.
>
> Yes, you're right. But shouldn't the documentation be more clearly about
> this issue?

The documentation says the following.  How can we improve it?

`nnimap-stream'
     The type of stream used to connect to your server.  By default,
     nnimap will detect and automatically use all of the below, with
     the exception of TLS/SSL.  (IMAP over TLS/SSL is being replaced by
     STARTTLS, which can be automatically detected, but it's not widely
     deployed yet.)

     Example server specification:

          (nnimap "mail.server.com"
                  (nnimap-stream ssl))

     Please note that the value of `nnimap-stream' is a symbol!
...

Re: Setting up Gnus with IMAP

[Sebastian Kaps]

// Simon Josefsson writes:

> Sebastian Kaps <seb-dated-1058345066.f5d54a@toyland.sauerland.de> writes:
>> // Kai Großjohann writes:
>> 
>>> IMHO it doesn't make sense to specify so many values which are the
>>> default anyhow.  For example, should the port be "143" or 143?
>>> Should the authenticator be "login" or login?  Etc pp.
>> 
>> Yes, you're right. But shouldn't the documentation be more clearly about
>> this issue?

> The documentation says the following.  How can we improve it?

My version of the documentation seems a bit outdated. For nnimap-stream
it says:
,----
| `nnimap-stream'
|      The type of stream used to connect to your server.  By default,
|      nnimap will detect and automatically use all of the below, with
|      the exception of SSL. (SSL is being replaced by STARTTLS, which
|      can be automatically detected, but it's not widely deployed yet).
| 
|         * "gssapi:" Connect with GSSAPI (usually kerberos 5). Require
|           the `imtest' program.
| 
|         * "kerberos4:" Connect with kerberos 4. Require the `imtest'
|           program.
| 
|         * "starttls:" Connect via the STARTTLS extension (similar to
|           SSL). Require the external library `starttls.el' and program
|           `starttls'.
| 
|         * "ssl:" Connect through SSL. Require OpenSSL (the program
|           `openssl') or SSLeay (`s_client').
| 
|         * "network:" Plain, TCP/IP network connection.
| 
|      The `imtest' program is shipped with Cyrus IMAPD, nnimap support
|      both `imtest' version 1.5.x and version 1.6.x.
| 
|      For SSL connections, the OpenSSL program is available from
|      `http://www.openssl.org/'. OpenSSL was formerly known as SSLeay,
|      and nnimap support it too - altough the most recent versions of
|      SSLeay, 0.9.x, are known to have serious bugs making it useless.
|      Earlier versions, especially 0.8.x, of SSLeay are known to work.
`----

Note that the possible values are quoted (and even contain colons). This
might be confusing.


> `nnimap-stream'
>      The type of stream used to connect to your server.  By default,
>      nnimap will detect and automatically use all of the below, with
>      the exception of TLS/SSL.  (IMAP over TLS/SSL is being replaced by
>      STARTTLS, which can be automatically detected, but it's not widely
>      deployed yet.)

>      Example server specification:

>           (nnimap "mail.server.com"
>                   (nnimap-stream ssl))

>      Please note that the value of `nnimap-stream' is a symbol!
> ...

This is much better. I think the example wipes out any possible doubt.
However - as an end user who is not very familar with lisp - the "...is
a symbol!" part doesn't help much. I'd have to look up the meaning of
'symbol' in the lisp documentation, which wouldn't be a problem but I
think it's unnecessary.

-- 
Ciao, Sebastian

Setting up gnus with IMAP

[Marvin]

I have recently set-up gnus to read my email via imap. Everything
seems to work fine, except I don't see my email.

Any suggestions

Gnus Newbie

cheers
m

Re: Setting up gnus with IMAP

[Marvin]

On May 12, 9:19 pm, Marvin <marvin...@gmail.com> wrote:
> I have recently set-up gnus to read my email via imap. Everything
> seems to work fine, except I don't see my email.
>
> Any suggestions
>
> Gnus Newbie
>
> cheers
> m

I see gnus-help, but nothing else

Re: Setting up gnus with IMAP

[Gijs Hillenius]

I could be very wrong: BUT

In the gnus buffer, type ^ and get a list of servers.
Select your imap server and check if your mail boxes are
there.
Subscribe to the ones you want to see (toggle) u U).

Regards

Gijs


-- 
Hey man, cool crash!  Way to cheat death.
		-- Bart visits Martin in the hospital,
		   "Saturdays of Thunder"

Re: Setting up gnus with IMAP

[Marvin]

On May 13, 3:46 am, Gijs Hillenius <gijs_no_sp...@hillenius.net>
wrote:
> I could be very wrong: BUT
>
> In the gnus buffer, type ^ and get a list of servers.
> Select your imap server and check if your mail boxes are
> there.
> Subscribe to the ones you want to see (toggle) u U).
>
> Regards
>
> Gijs
>
> --
> Hey man, cool crash!  Way to cheat death.
>                 -- Bart visits Martin in the hospital,
>                    "Saturdays of Thunder"

Gijs,

This worked, thanks.

One other question, is there a way to get gnus to show the subscribed
mailboxes at the start ?

cheers
MMD

Re: Setting up gnus with IMAP

[Richard Riley]

Marvin <marvinpas@gmail.com> writes:

> On May 13, 3:46 am, Gijs Hillenius <gijs_no_sp...@hillenius.net>
> wrote:
>> I could be very wrong: BUT
>>
>> In the gnus buffer, type ^ and get a list of servers.
>> Select your imap server and check if your mail boxes are
>> there.
>> Subscribe to the ones you want to see (toggle) u U).
>>
>> Regards
>>
>> Gijs
>>
>> --
>> Hey man, cool crash!  Way to cheat death.
>>                 -- Bart visits Martin in the hospital,
>>                    "Saturdays of Thunder"
>
> Gijs,
>
> This worked, thanks.
>
> One other question, is there a way to get gnus to show the subscribed
> mailboxes at the start ?
>
> cheers
> MMD

Maybe its not showing them because they are empty? You can customise
that using the customise group option or do it in your .emacs/.gnus
using something like:

(setq  gnus-permanently-visible-groups (rx(or "root" "INBOX" "FastSearch" "DevelopmentEmail.mail" )))

Re: Setting up gnus with IMAP

[Rob Weir]

On 13 May 2009, Marvin wrote:
> One other question, is there a way to get gnus to show the subscribed
> mailboxes at the start ?

It should show the subscribed ones at startup, provided they have new
mail in them.  You can customise each group (with G c) to make them
"Permanently visible".

-- 
-rob

Re: Setting up gnus with IMAP

[Tassilo Horn]

"Rob Weir" <rweir@ertius.org> writes:

Hi!

>> One other question, is there a way to get gnus to show the subscribed
>> mailboxes at the start ?
>
> It should show the subscribed ones at startup, provided they have new
> mail in them.  You can customise each group (with G c) to make them
> "Permanently visible".

Or simply hit `L' in *Group* (and `l' again to hide groups with no
unread/ticked messages).  I think it's very convenient to have only the
groups displayed which contain unread or ticked messages, especially if
you have lots of groups, although that might feel a bit strange in the
beginning.

Bye,
Tassilo
-- 
There are only two things that can cut diamonds: other diamonds, and
Chuck Norris.