From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: ~/.authinfo is now ignored for nnimap
Date: 17 May 2004 11:11:25 -0400 [thread overview]
Message-ID: <4noeonjdgi.fsf@lifelogs.com> (raw)
In-Reply-To: <m3oeonytoo.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 17 May 2004 17:11:51 +0200")
On Mon, 17 May 2004, larsi@gnus.org wrote:
> "Ted Zlatanov" <tzz@lifelogs.com> writes:
>
>> I'm not able to log in automatically through my ~/.authinfo file, like
>> I used to before (I get a LOGIN passphrase query). This is probably
>> due to the changes made over the weekend. Could someone look into it?
>
> It's fixed in CVS...
Thank you!
Ted
next prev parent reply other threads:[~2004-05-17 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 17:20 Use flim's sasl.el to authenticate to IMAP servers Kim Minh Kaplan
2004-05-16 14:25 ` Lars Magne Ingebrigtsen
2004-05-17 2:02 ` Katsumi Yamaoka
2004-05-17 12:36 ` Lars Magne Ingebrigtsen
2004-05-17 12:38 ` Katsumi Yamaoka
2004-05-17 13:49 ` ~/.authinfo is now ignored for nnimap (was: Use flim's sasl.el to authenticate to IMAP servers) Ted Zlatanov
2004-05-17 15:11 ` ~/.authinfo is now ignored for nnimap Lars Magne Ingebrigtsen
2004-05-17 15:11 ` Ted Zlatanov [this message]
2004-05-17 8:00 ` Use flim's sasl.el to authenticate to IMAP servers anti
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=4noeonjdgi.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
/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).