From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/12519 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: future wishes - ACAP and LDAP support Date: 04 Oct 1997 21:17:11 +0200 Message-ID: References: <19970930184007.48935@redwood.math.gatech.edu> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035152040 4178 80.91.224.250 (20 Oct 2002 22:14:00 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:14:00 +0000 (UTC) Return-Path: Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by altair.xemacs.org (8.8.7/8.8.7) with ESMTP id NAA26337 for ; Sat, 4 Oct 1997 13:22:43 -0700 Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id PAA24673 for ; Sat, 4 Oct 1997 15:15:41 -0500 (CDT) Original-Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Sat, 4 Oct 1997 21:17:45 +0200 Original-Received: (from hniksic@localhost) by jagor.srce.hr (8.8.7/8.8.6) id VAA00399; Sat, 4 Oct 1997 21:17:11 +0200 (MET DST) Original-To: ding@ifi.uio.no X-Attribution: Hrvoje X-Face: Mie8:rOV<\c/~z{s.X4A{!?vY7{drJ([U]0O=W/xDi&N7XG KV^$k0m3Oe/)'e%3=$PCR&3ITUXH,cK>]bci&Ff%x_>1`T(+M2Gg/fgndU%k*ft [(7._6e0n-V%|%'[c|q:;}td$#INd+;?!-V=c8Pqf}3J In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Oct 1997 00:10:10 +0200" Original-Lines: 57 X-Mailer: Quassia Gnus v0.10/XEmacs 20.3(beta26) - "Riga" Xref: main.gmane.org gmane.emacs.gnus.general:12519 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:12519 Lars Magne Ingebrigtsen 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 | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- * Q: What is an experienced Emacs user? * A: A person who wishes that the terminal had pedals.