From: Stefan Kamphausen <skampi@gmx.de>
Subject: One more authinfo file posting
Date: Wed, 09 Feb 2005 09:57:24 +0100 [thread overview]
Message-ID: <85hdkmi00b.fsf@mail.bn-software.de> (raw)
Hi,
I really think that this should be in the FAQ _and_ that Gnus should
be a little bit more verbose on its decision making process.
The problem is -once again- that the authinfo file defined in my
nnimap settings won't be read. I've tried (probably) all combinations
of:
- the name of the IMAP server (IP, FQDN, short name)
- the port (143, imap, 993, none at all)
and the matching settings in my .authinfo file ([1]).
I would really like to see some messages in the *nnimap-debug* buffer,
telling me for what it was looking in which file and what it found and
why it chose not to use such a line.
Could you give me any pointers on what I could try next or how to be
more verbose in the nnimap-debug-buffer? I tried to read the code in
nnimap.el but I think I'd need to dive much deeper into the gnus
mechanisms to really understand it.
For my system and setup see [2].
Thanks and Regards
Stefan Kamphausen
Footnotes:
[1]
Actually, I use a different file because I am accessing a different
mailbox on an ms exchange server; this could be a big improvement to
the docs or the FAQs because I've hunted it for some 3 weeks until I
found that I could log in to the server with a combination of
"domain/username/short name of the mailbox". Most important was the
short name, because the long name as displayed in outlook didn't work.
Maybe because of the spaces or the '[' or the '&' or the ']' in it's
name, I don't know. But then, that's another story :-)
[2]
I am using Gnus v5.10.6 on "21.4 (patch 15) \"Security Through
Obscurity\" XEmacs Lucid" with the following
gnus-secondary-select-method:
(setq gnus-secondary-select-methods
'((nnml "")
(nnimap ""
(nnimap-address "mailserver")
(nnimap-authinfo-file "~/.imap-othermailbox")
(nnimap-list-pattern ("*"))
(nnimap-expunge-on-close never)
)
))
--
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.
next reply other threads:[~2005-02-09 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 8:57 Stefan Kamphausen [this message]
2005-02-09 14:21 ` Reiner Steib
2005-02-09 14:37 ` Stefan Kamphausen
2005-02-09 15:27 ` Stefan Kamphausen
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=85hdkmi00b.fsf@mail.bn-software.de \
--to=skampi@gmx.de \
/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).