Viktor Dukhovni:
> > If all feature of Postfix can be represented as a list of name=value
> > pairs, for example:
> >
> > feature context | name = value
> > |=
> > main.cf | parameter = value
> > master.cf field |
On Fri, Nov 29, 2013 at 05:41:35PM -0500, Wietse Venema wrote:
> There is no '/' in master.cf service names because master.cf services
> must have sockets or FIFOs under the postfix-owned "private" or
> "public" directory. It's unsafe for the Postfix master daemon to
> open sockets or FIFOs in dir
Viktor Dukhovni:
> In postmast(1) there was no ambiguity between "." in a service name
> and "." between the service name and the service type, because
> these were specified separately "postmast [-s ] [-t ]
> ...". While integrating a super-set of postmast(1) functionality into
> postconf(1) Wiet
On Thu, Nov 28, 2013 at 09:09:32AM -0700, LuKreme wrote:
> Also, the Fields are all single words, and almost all the parameters
> have multiple_words_with_underscores, so there might be something
> there.
>
> myhostname mydomain myorigin mydestination and mynetworks seem
> to be the only paramete
On 27 Nov 2013, at 19:26 , Wietse Venema wrote:
> LuKreme:
>> On 27 Nov 2013, at 17:13 , Wietse Venema wrote:
>>> Examples are at http://www.porcupine.org/postfix-mirror/wip.html
>>> and at the top of the RELEASE_NOTES file. Documentation is also in
>>> the postconf(1) manpage (nroff -man man/m
Wietse Venema:
> LuKreme:
> > On 27 Nov 2013, at 17:13 , Wietse Venema wrote:
> > > Examples are at http://www.porcupine.org/postfix-mirror/wip.html
> > > and at the top of the RELEASE_NOTES file. Documentation is also in
> > > the postconf(1) manpage (nroff -man man/man1/postconf.1 | less).
> >
LuKreme:
> On 27 Nov 2013, at 17:13 , Wietse Venema wrote:
> > Examples are at http://www.porcupine.org/postfix-mirror/wip.html
> > and at the top of the RELEASE_NOTES file. Documentation is also in
> > the postconf(1) manpage (nroff -man man/man1/postconf.1 | less).
>
> My only comment is that t
On 27 Nov 2013, at 17:13 , Wietse Venema wrote:
> Examples are at http://www.porcupine.org/postfix-mirror/wip.html
> and at the top of the RELEASE_NOTES file. Documentation is also in
> the postconf(1) manpage (nroff -man man/man1/postconf.1 | less).
My only comment is that the delineation betwee
I have uploaded postfix-2.11-20131126-nonprod to the master FTP
site. This has revised DANE support as well as "advanced" master.cf
query/update support. The postconf code has been tested, but the
documentation is still rough.
Examples are at http://www.porcupine.org/postfix-mirror/wip.html
and at
Thanks for feedback.
Background information: the advanced query/update methods are
primarily for programmatic use by system management tools. This
means the "user" interface needs to be highly consistent.
Ideally, postconf enumerates Postfix main.cf and master.cf details
as a list of "name=val
* Wietse Venema :
> I recently picked up work on the postconf command that I suspended
> in January this year. It's probably best to just give a few examples.
>
> First, a word about notation. I wanted to describe master.cf
> properties with a kind of pathname notation. The original idea was
> to
11 matches
Mail list logo
