From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/39682 Path: main.gmane.org!not-for-mail From: Per Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: new Mail-Followup-To patch...please take a look... Date: Wed, 24 Oct 2001 19:08:40 +0200 Organization: The Church of Emacs Sender: owner-ding@hpc.uh.edu Message-ID: References: <87wv1m9y6j.fsf@mclinux.com> <87g08a9u14.fsf@mclinux.com> <87elnuxk3y.fsf@squeaker.lickey.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035175355 29275 80.91.224.250 (21 Oct 2002 04:42:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:42:35 +0000 (UTC) Return-Path: Original-Received: (qmail 9007 invoked from network); 24 Oct 2001 17:12:14 -0000 Original-Received: from malifon.math.uh.edu (mail@129.7.128.13) by mastaler.com with SMTP; 24 Oct 2001 17:12:14 -0000 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 15wRX4-0007Dy-00; Wed, 24 Oct 2001 12:09:34 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 24 Oct 2001 12:09:11 -0500 (CDT) Original-Received: from sclp3.sclp.com (qmailr@sclp3.sclp.com [209.196.61.66]) by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id MAA12517 for ; Wed, 24 Oct 2001 12:08:59 -0500 (CDT) Original-Received: (qmail 8948 invoked by alias); 24 Oct 2001 17:09:08 -0000 Original-Received: (qmail 8943 invoked from network); 24 Oct 2001 17:09:08 -0000 Original-Received: from sheridan.dina.kvl.dk (130.225.40.227) by gnus.org with SMTP; 24 Oct 2001 17:09:08 -0000 Original-Received: from ssv2.dina.kvl.dk (ssv2.dina.kvl.dk [130.225.40.226]) by sheridan.dina.kvl.dk (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id TAA05024; Wed, 24 Oct 2001 19:08:40 +0200 Original-Received: from abraham by ssv2.dina.kvl.dk with local (Exim 3.12 #1 (Debian)) id 15wRWC-0005xY-00; Wed, 24 Oct 2001 19:08:40 +0200 Original-To: ding@gnus.org X-Face: +kRV2]2q}lixHkE{U)mY#+6]{AH=yN~S9@IFiOa@X6?GM|8MBp/ In-Reply-To: (prj@po.cwru.edu's message of "Wed, 24 Oct 2001 12:31:39 -0400") Original-Lines: 51 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.106 (i686-pc-linux-gnu) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:39682 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:39682 prj@po.cwru.edu (Paul Jarc) writes: > Per Abrahamsen wrote: >> E.g. have a single parameter >> >> mail-address >> >> which states the main mail address associated with the folder, > > Can we make it a vector? Some lists have widely-used aliases in > addition to the primary address; all of these should be used for MFT. > For mail-types that apply to "a" and "f", we'd just use the first > entry. > > If it is a vector, then we might let it be a list of address-type > pairs, but I'm not sure that would be useful. I'd prefer using a list over a vector, and it should be named mail-addresses then. Other than that, I think it would be a good idea. Some people have multiple mail addresses, this would be a natural place to list them. >> mail-type >> Unknown (default) >> Personal use m-a for "a", don't set >> Open List use m-a for "a", set MFC >> Closed List use m-a for "a" and "f", set MFC >> >> which state what type of folder it is. > > What would Unknown mean? I.e., how would code react to it? I think > it might be better to have no Unknown value and make, say, Open List > the default; I imagine that'd be the most common case. Either that, > or ignore mail-address(es?) when mail-type is not set. (Since these > are new parameters, we won't be affecting any existing configurations > with the choice of default.) I did imagine "a" would be ignored for unknown types, but I have no strong opinion what the default should be. If "Open List" is most common, then that should probably be the choice. >> The "to-list" and "to-address" parameters should then be recognized >> for backward compatibility, > > Does this mean the MFT code should do anything with them, or only the > code that already uses them? If the default mail-type is open/closed list it would be more safe to ignore them. Otherwise, use them if it is not to much trouble to implement.