Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Stefan Kamphausen <skampi@gmx.de>
Subject: Re: One more authinfo file posting
Date: Wed, 09 Feb 2005 15:37:05 +0100	[thread overview]
Message-ID: <85ll9xyf3i.fsf@mail.bn-software.de> (raw)
In-Reply-To: <v9bratizl9.fsf@marauder.physik.uni-ulm.de>

Hi,

Reiner Steib <reinersteib+from-uce@imap.cc> writes:

first: thanks for the quick reply :-)

> On Wed, Feb 09 2005, Stefan Kamphausen wrote:
>
>> 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]).
>
> It's hard to guess if you omit the most important part, the content of
> the authinfo file (~/.imap-othermailbox).  Be sure to erase any
> passwords.

well, I thought I made it clear, that I don't have /one/ file but a
plethora of combinations.

Currently I got in my ~/.authinfo:


machine news.newsserver.example login kamphausen password xxxxx force yes
machine mailserver login "windomain/skamphausen/othermailbox" password "xxxxx"


and in my ~/.imap-othermailbox I got one line for each the IP and the
FQDN of "mailserver" and one for just "mailserver" that look just like
the second line in ~/.authinfo otherwise.


 > >
>> 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.
>
> As a quick check, use the following patch:
> [snip]

OK, the patch reveiled that the file that is actually read is
~/.authinfo and not the ~/.imap-othermailbox:

Parsing authinfo file `~/.authinfo'

Nevertheless, I can't see why it doesn't accept the line in there.
Maybe I'll spent another hour doing more experiments with it ;-)

Please tell me if I'm wrong, but considering the amount of postings
dealing with this problem, shouldn't there be some messages as to what
lines are examined and why they are rejected in the message-log?  The
messages could be turned off with a nnimap-i-know-my-authinfo-dealings
variable ;-)

Thanks and Regards
Stefan
-- 
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.


  reply	other threads:[~2005-02-09 14:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09  8:57 Stefan Kamphausen
2005-02-09 14:21 ` Reiner Steib
2005-02-09 14:37   ` Stefan Kamphausen [this message]
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=85ll9xyf3i.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).