From: Jim Crossley <jim@crossleys.org>
To: info-gnus-english@gnu.org
Subject: Re: Dovecot not liking .authinfo?
Date: Sat, 03 Mar 2007 15:15:04 -0500 [thread overview]
Message-ID: <87vehiw0c7.fsf@asus.crossleys.home> (raw)
In-Reply-To: <86fy8ms1ro.fsf@blue.stonehenge.com>
Ok, I figured it out...
merlyn@stonehenge.com (Randal L. Schwartz) writes:
>>> I'm trying out a dovecot imap server, and gnus simply will not
>>> authenticate to it with what's in ~/.authinfo. It prompts me every
>>> time! The perms are correct, and it works with other imap servers.
[...]
> It's working just fine for me. The problem with dovecot is that
> it's hyper-configurable. :) This is what I have in my .authinfo:
It wasn't a dovecot problem at all. It seems that if you specify
'port' in .authinfo, you must also set nnimap-server-port in .gnus.el,
regardless of whether you're using the standard imap port.
So given this in .gnus.el:
(setq gnus-secondary-select-methods
'(
(nnimap "dovecot"
(nnimap-address "dovecot")
)
(nnimap "courier"
(nnimap-address "courier")
(nnimap-server-port 143)
)
)
)
My .authinfo:
machine courier port 143 login jim password ......
machine dovecot port 143 login jim password ......
The courier box never prompted me for un/pw, but the dovecot box
always did. I fixed the problem by simply removing "port 143" from
the dovecot line in .authinfo. I could've also fixed it by adding
(nnimap-server-port 143) in .gnus.el. They just have to agree, I
think.
Thanks for the quick replies,
Jim
prev parent reply other threads:[~2007-03-03 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 1:08 Jim Crossley
2007-03-03 16:23 ` Slackrat
2007-03-03 16:57 ` Randal L. Schwartz
2007-03-03 20:15 ` Jim Crossley [this message]
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=87vehiw0c7.fsf@asus.crossleys.home \
--to=jim@crossleys.org \
--cc=info-gnus-english@gnu.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).