Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: future wishes - ACAP and LDAP support
Date: 04 Oct 1997 21:17:11 +0200	[thread overview]
Message-ID: <kigiuvd5oeg.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Oct 1997 00:10:10 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> 1) A greater flexibility in specifying how mail is to be fetched.  For
> instance, you may have several POP maildrops with different user names
> and passwords, as well and local mail spools, MAPI servers, Qmail
> spools and other animals.  We need a way to specify this.

This is quite easy.  For instance, you can use VM's model for POP
specification:

    A POP maildrop specification has the following format:

       \"HOST:PORT:AUTH:USER:PASSWORD\"

    HOST is the host name of the POP server
    PORT is the TCP port number to connect to (should normally be 110).
    USER is the user name sent to the server.
    PASSWORD is the secret shared by you and the server for
    authentication purposes.  How is it used depends on the value of
    the AUTH parameter.  If the PASSWORD is \"*\", VM will prompt
    you for the password the first time you try to retrieve mail from
    maildrop.  If the password is valid, VM will not ask you for the
    password again during this Emacs session.

    AUTH is the authentication method used to convince the server you
    should have access to the maildrop.  Acceptable values are
    \"pass\", \"rpop\" and \"apop\".  For \"pass\", the PASSWORD is sent to
    the server with the POP PASS command.  For \"rpop\", the PASSWORD
    should be the string to be sent to the server via the RPOP
    command.  In this case the string is not really a secret;
    authentication is done by other means.  For \"apop\", an MD5 digest
    of the PASSWORD appended to the server timestamp will be sent to
    the server with the APOP command.  In order to use \"apop\" you
    will have to set the value of vm-pop-md5-program appropriately to
    point at the program that will generate the MD5 digest that VM
    needs.


Alternatively, we could make `nnmail-spool-file' be more than just a
list of strings, for instance:

(setq nnmail-spool-file '("/var/mail/hniksic"
                          (pop :host "regoc" :user "hniksic" :password "uhoh")
                          (mapi :host "fubar")
                          ...))

It would be backward-compatible, and straightforward to implement.
More or less, anyway.

Also, it should be renamed to something nicer, like
`nnmail-spool-methods', the old variable being just a varalias.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
* Q: What is an experienced Emacs user?
* A: A person who wishes that the terminal had pedals.


  parent reply	other threads:[~1997-10-04 19:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-30 22:40 Richard Coleman
1997-10-01  1:38 ` Andrew J Cosgriff
1997-10-01  2:36 ` Jason R Mastaler
1997-10-01  6:57 ` Rolf Marvin B|e Lindgren
1997-10-01 14:31   ` William M. Perry
1997-10-03 22:10   ` Lars Magne Ingebrigtsen
1997-10-03 23:11     ` David Kågedal
1997-10-12 13:11       ` Lars Magne Ingebrigtsen
1997-10-04 19:17     ` Hrvoje Niksic [this message]
1997-10-05 17:02       ` Paul Franklin
1997-10-12 13:48         ` Lars Magne Ingebrigtsen
1997-10-05 10:00     ` Kim-Minh Kaplan
1997-10-05 20:29     ` Kai Grossjohann
1997-10-12 13:50       ` Lars Magne Ingebrigtsen

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=kigiuvd5oeg.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).