This is a discussion on Re: FreeTDS support for table lookups within the mailing.postfix.users forums, part of the Mail Servers and Related category; On Sun, 9 May 2004, Wietse Venema wrote: > Victor.Duchovni@MorganStanley.com: > > - All of multi-parameter map ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Sun, 9 May 2004, Wietse Venema wrote:
> Victor.Duchovni@MorganStanley.com: > > - All of multi-parameter map types support both external ".cf" and > > "mapsource_" prefix notation in main.cf. > > The "mapsource_" prefix notation is deprecated. It is confusing > because the parameters don't show up in postconf(1) output, and > it encourages storage of passwords in main.cf. OK, if you insist (an alternative is to enhance "postconf" to output parameters that are defined in main.cf). The key thing I want to add is ${parameter} substitution even when the map is being defined in external files. If it were up to me, I would use ${variable} only for main.cf parameters and use %[alphabet-soup] for key/result substitutions. Likely that is too radical a change, so we will need to support both with ${special-variable} taking precedence over ${parameter}. > > - Parameters that hold passwords are read from a file when the parameter > > value starts with a "file:/" prefix. > > There are other main.cf parameters (myhostname) that also need file > name support. This would avoid the need for Debian's /etc/hostname hack. > > Introducing file name syntax for non-map lookup needs to be thought > out carefully to avoid conflicts (either in code or in the user's > brain) with map lookup. > Yes, I think this makes sense. > With "mapsource_" prefix notation going away, what is the urgency > of changing configuration file syntax? > I want to be able to say: server_host = $myldap_host server_port = $myldap_port ... in /etc/postfix/everymap.cf. This of course means, that I will be manually defining my own parameters that don't show up in postconf output (just as I do for "-o parameter=$transport_specific_value", ...) I really do think that "postconf" and "postconf -n" (but clearly not "-d") should show ad-hoc parameter values. -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:majordomo@postfix.org?body=unsubscribe%20p ostfix-users> |