Robert Moskowitz:
It does raise a question if there is an uncomment option? For example
submission is commented in the master.cf and a very frequent uncomment
target.
I don't understand how that would work.
Wietse
On 01/14/2013 03:59 AM, Wietse Venema wrote:
Robert Moskowitz:
It does raise a question if there is an uncomment option? For example
submission is commented in the master.cf and a very frequent uncomment
target.
I don't understand how that would work.
Actually, I don't either!
SInce both
Le 11/01/2013 21:47, Wietse Venema a écrit :
Viktor Dukhovni:
The only part that is tricky is the command + args column, where
users arguably may want to add/delete -o flags, but in general
the various -o flags one may want to add are not necessarily
othogonal, and it is not always safe to
On 01/11/2013 03:47 PM, Wietse Venema wrote:
Viktor Dukhovni:
The only part that is tricky is the command + args column, where
users arguably may want to add/delete -o flags, but in general
the various -o flags one may want to add are not necessarily
othogonal, and it is not always safe to add
Robert Moskowitz:
My thoughts on this is which provides a better delete function?
For main.cf, postconf already uses the following syntax:
postconf mynetworks ... show main.cf entry(or entries)
postconf -# mynetworks ... comment out main.cf entry
postconf -X mynetworks ...
On 01/13/2013 02:54 PM, Wietse Venema wrote:
Robert Moskowitz:
My thoughts on this is which provides a better delete function?
For main.cf, postconf already uses the following syntax:
postconf mynetworks ... show main.cf entry(or entries)
postconf -# mynetworks ... comment out
On Fri, Jan 11, 2013 at 03:47:41PM -0500, Wietse Venema wrote:
If the concerns with '=' and '.' in service names can be overcome,
then the mouss syntax would simplify the user interface to query
or update a master.cf attribute.
Neither is actually a problem provided we use strrchr to find
the
Viktor Dukhovni:
On Fri, Jan 11, 2013 at 03:47:41PM -0500, Wietse Venema wrote:
If the concerns with '=' and '.' in service names can be overcome,
then the mouss syntax would simplify the user interface to query
or update a master.cf attribute.
Neither is actually a problem provided we
This note discusses some user-interface issues with upcoming
postconf(1) features that will be used to manage the content of
master.cf files.
User-interface consistency is important, especially for people who
work a lot with Postfix: fewer things to remember means fewer
mistakes to make (it's
* Wietse Venema postfix-users@postfix.org:
This note discusses some user-interface issues with upcoming
postconf(1) features that will be used to manage the content of
master.cf files.
User-interface consistency is important, especially for people who
work a lot with Postfix: fewer things
: postconf user interface
* Wietse Venema postfix-users@postfix.org:
This note discusses some user-interface issues with upcoming
postconf(1) features that will be used to manage the content of
master.cf files.
User-interface consistency is important, especially for people who
work a lot
Patrick Ben Koetter:
Next, a few examples that are likely to be implemented:
postconf -M# service-type ...
postconf -M# service-type.service-name ...
postconf -MX service-type ...
postconf -MX service-type.service-name ...
Delete (or comment) out the
Le 08/01/2013 22:00, Wietse Venema a écrit :
This note discusses some user-interface issues with upcoming
postconf(1) features that will be used to manage the content of
master.cf files.
User-interface consistency is important, especially for people who
work a lot with Postfix: fewer things
Le 08/01/2013 23:06, Wietse Venema a écrit :
Patrick Ben Koetter:
[snip]
Should postconf be able/offer to make backup copies before it acts a request
out?
Should it with main.cf? Should we enourage the use of version control?
given that people use different version control systems, I
mouss:
I am contemplating a new class of master.cf operations that operate
column-wise. These currently have no main.cf equivalent.
postconf -Mu chroot=n inet unix fifo pass
I like the mib syntax of main.cf. so I'd prefer something like
postconf -e service.submission.chroot=n
* Wietse Venema postfix-users@postfix.org:
Patrick Ben Koetter:
Next, a few examples that are likely to be implemented:
postconf -M# service-type ...
postconf -M# service-type.service-name ...
postconf -MX service-type ...
postconf -MX
On Tue, Jan 08, 2013 at 04:00:34PM -0500, Wietse Venema wrote:
However, the syntax differs from postconf -M commands that can
target multiple services, such as postconf -M inet or postconf
-Mu chroot=n inet. There, a service is better specified as
service-type or service-type.service-name.
On 1/8/2013 5:26 PM, Patrick Ben Koetter wrote:
* Wietse Venema postfix-users@postfix.org:
Patrick Ben Koetter:
Next, a few examples that are likely to be implemented:
postconf -M# service-type ...
postconf -M# service-type.service-name ...
postconf -MX service-type ...
18 matches
Mail list logo
