From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/12703 Path: main.gmane.org!not-for-mail From: Christian Limpach Newsgroups: gmane.emacs.gnus.general Subject: Re: ideas needed for nnmail-pop3-movemail Date: 26 Oct 1997 19:05:22 +0100 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035152192 5216 80.91.224.250 (20 Oct 2002 22:16:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:16:32 +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.8) with ESMTP id LAA03945 for ; Sun, 26 Oct 1997 11:40:44 -0800 Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA12465 for ; Sun, 26 Oct 1997 13:42:07 -0600 (CST) Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no (8.8.7/8.8.7/ifi0.2) with SMTP id TAA10680 for ; Sun, 26 Oct 1997 19:36:54 +0100 (MET) Original-Received: (qmail 25656 invoked by uid 504); 26 Oct 1997 18:36:50 -0000 Original-Received: (qmail 25653 invoked from network); 26 Oct 1997 18:36:49 -0000 Original-Received: from nice.ethz.ch (129.132.71.53) by claymore.vcinet.com with SMTP; 26 Oct 1997 18:36:49 -0000 Original-Received: (from uucp@localhost) by nice.ethz.ch (8.8.7/8.8.7) id TAA11999 for gnus.org!ding; Sun, 26 Oct 1997 19:36:47 +0100 (MET) Original-Received: (from chris@localhost) by delight.pin.lu (8.7.6/8.7.3) id TAA04508; Sun, 26 Oct 1997 19:05:24 +0100 (MET) Original-To: "(ding)" In-Reply-To: Stainless Steel Rat's message of "25 Oct 1997 23:33:11 -0500" Original-Lines: 36 X-Mailer: Gnus v5.4.59/Emacs 19.34 Xref: main.gmane.org gmane.emacs.gnus.general:12703 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:12703 Stainless Steel Rat writes: > Well, if iteration is handled by nnmail through an alist of mailboxes, then > nnmail properly should also maintain cache of passwords, either in the same > alist or a parallel alist, assuming that password caching is enabled (which > by default it should not). Within the let form that temporarilly binds > pop3-maildrop and pop3-mailhost, pop3-password is bound to the cached > password for the mailhost/maildrop or nil. Then pop3-movemail is called > within that let form, and everything just works. If it is so, then the code which asks for passwords should be removed from pop3 altogether. Otherwise there will be two routines which query for pop3 passwords and this is bad: if the user doesn't enter a password at the first query (like to skip that pop server) pop3.el will ask again (current API: no password = ask, right ?). Also nnmail will not know wheter to save the password or not, as pop3.el doesn't report why it failed. Another advantage of pop3.el handling the password caching is that there could be multiple clients (gnus, vm) and the user would still only have to enter the password once. And finally I prefer to trust pop3.el with my password (after I have seen the code) than some client. If you look at my code, you will see, that I have indeed used a let form to bind all the pop3 variables. I had first added the parsing of the pop-server specification to pop3.el, but then I decided that it would be better to make as few changes to pop3.el as possible. The result was that I could move everything out of pop3.el except for password caching. What I don't like about my implementation is that it doesn't allow a single host to be used several times with different users/ports/... but this can be changed easily by extending the key used to lookup the password in the alist. christian