From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: nnimap server denied
Date: 24 Nov 1999 00:16:36 +0100 [thread overview]
Message-ID: <iluyabool2j.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Matt McClure's message of "23 Nov 1999 18:08:01 -0500"
Matt McClure <matt.mcclure@ccur.com> writes:
> I've tried with and without the nnimap-stream and nnimap-authenticator
> variables, but the result is the same in all cases. The connection to
> the IMAP server is denied. The following shows up in the *nnimap-debug*
> buffer:
What does the *imap-log* buffer contain? (edit out passwords before
mailing)
> Connecting to the IMAP server from Pine works just fine.
I believe Pine sometime log in by doing 'rsh mailserver imapd', nnimap
doesn't so things might differ.
next prev parent reply other threads:[~1999-11-23 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 23:08 Matt McClure
1999-11-23 23:16 ` Simon Josefsson [this message]
1999-11-24 18:53 ` Matt McClure
1999-11-24 20:29 ` Simon Josefsson
1999-11-24 21:16 ` Matt McClure
1999-11-24 21:09 ` David Maslen
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=iluyabool2j.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
--cc=ding@gnus.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).