Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Yuan MEI" <yuan.mei@gmail.com>
Subject: Re: How to use `~/.authfile' for POP account
Date: Mon, 15 Aug 2005 22:52:16 +0800	[thread overview]
Message-ID: <m28xz32qxr.fsf@may.fudan.edu.cn> (raw)
In-Reply-To: <m3ek92uvg9.fsf@mid.gehheimdienst.de>

I think you missed the point.  I know how to write a valid
`.authinfo'.  The problem is, 
for `imap',
(nnimap-authinfo-file "~/.authinfo") works,
for `smtp',
(setq smtpmail-auth-credentials "~/.authinfo") works,
however, for pop, I don't know which already-written function is
available, so I write that one to process it.

Frank Schmitt <usereplyto2005@frank-schmitt.net> writes:

> You should use ~/.authinfo (for all protocols).
> Write something like this in it:
> machine pop.isp.com login ymei password f.h637Fj

-- 
Yuan MEI


      reply	other threads:[~2005-08-15 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 17:24 Yuan MEI
2005-08-10  7:01 ` Frank Schmitt
2005-08-15 14:52   ` Yuan MEI [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=m28xz32qxr.fsf@may.fudan.edu.cn \
    --to=yuan.mei@gmail.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).