-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/09/14 12:07, Viktor Dukhovni wrote:
On Sat, Sep 27, 2014 at 03:50:24AM +0200, Benny Pedersen wrote:
. In order to figure out the version of a program it is common
to make
the binary print it to stdout if it is invoked with the
I asked a long time ago if the postfix version could be added to the
postconf -n output (like dovecot does), but was told it wasn't possible
for some technical reason I didn't understand...
On 9/26/2014 9:42 PM, Karl-Philipp krich...@posteo.de wrote:
Hi together,
In order to figure out the
Karl-Philipp:
[mail_owner GID bits]
These GID bits do not matter. Therefore it is not documented.
In the exceptional case that Postfix requires group permissions,
those permissions are cpntrolled by the setgid_group parameter.
As a general rule, Postfix manpages describe the things that are
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the version, release date, and so on.
Wietse
Charles Marcus:
I asked a long time ago if the postfix version could be added to the
postconf -n output (like
Karl-Philipp:
Sep 27 05:20:46 richtercloud postfix/smtpd[14253]: warning: SASL
authentication failure: cannot connect to saslauthd server: Access (rx)
on file|directory /absolute/path/to/file/directory caused error
Permission denied
Wrong mailing list. These warnings are produced by the
On Sep 27, 2014, at 07.48, Wietse Venema wie...@porcupine.org wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the version, release date, and so on.
this reminds me - some time long ago, i happened to notice
b...@bitrate.net:
On Sep 27, 2014, at 07.48, Wietse Venema wie...@porcupine.org wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the version, release date, and so on.
this reminds me - some time long
li...@rhsoft.net:
Am 27.09.2014 um 16:32 schrieb Wietse Venema:
b...@bitrate.net:
On Sep 27, 2014, at 07.48, Wietse Venema wie...@porcupine.org wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the
On Sat, Sep 27, 2014 at 10:24:13AM -0400, b...@bitrate.net wrote:
On Sep 27, 2014, at 07.48, Wietse Venema wie...@porcupine.org wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the version, release date,
Am 27.09.2014 um 16:42 schrieb Wietse Venema:
li...@rhsoft.net:
Am 27.09.2014 um 16:32 schrieb Wietse Venema:
b...@bitrate.net:
On Sep 27, 2014, at 07.48, Wietse Venema wie...@porcupine.org wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the
li...@rhsoft.net:
i suppose the question was why it is part of postconf -n
output while it is not mentioned in main.cf and so should
only appear in postconf -d
[root@mail-gw:~]$ cat main.cf | grep config_directory
[root@mail-gw:~]$ postconf -n | grep config_directory
config_directory
On 9/27/2014 7:48 AM, wie...@porcupine.org (Wietse Venema)
wie...@porcupine.org (Wietse Venema) wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the version, release date, and so on.
Thanks Wietse...
Please
Charles Marcus:
On 9/27/2014 7:48 AM, wie...@porcupine.org (Wietse Venema)
wie...@porcupine.org (Wietse Venema) wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the version, release date, and so on.
On Sep 27, 2014, at 10.42, Viktor Dukhovni postfix-us...@dukhovni.org wrote:
On Sat, Sep 27, 2014 at 10:24:13AM -0400, b...@bitrate.net wrote:
On Sep 27, 2014, at 07.48, Wietse Venema wie...@porcupine.org wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration
On 9/27/2014 11:07 AM, wie...@porcupine.org (Wietse Venema)
wie...@porcupine.org (Wietse Venema) wrote:
Would an updated postfinger command help? Wietse
Well... if it could provide the output I described, then certainly. The
suggestion for a new command was just to illustrate I was saying it
On Sat, Sep 27, 2014 at 10:42:27AM -0400, Wietse Venema wrote:
[root@mail-gw:~]$ postconf -n | grep config_directory
config_directory = /etc/postfix
You're welcome to fix that. I'm now working on other things,
supporting per-milter and per-policy service settings.
There's a subtlety
On Sep 27, 2014, at 10.32, Wietse Venema wie...@porcupine.org wrote:
b...@bitrate.net:
On Sep 27, 2014, at 07.48, Wietse Venema wie...@porcupine.org wrote:
Use postconf -d, not postconf -n. -n is for settings in the
configuration file, -d is for the built-in settings which include
the
On Sep 27, 2014, at 11.20, Viktor Dukhovni postfix-us...@dukhovni.org wrote:
On Sat, Sep 27, 2014 at 10:42:27AM -0400, Wietse Venema wrote:
[root@mail-gw:~]$ postconf -n | grep config_directory
config_directory = /etc/postfix
You're welcome to fix that. I'm now working on other things,
On Sat, Sep 27, 2014 at 11:41:08AM -0400, b...@bitrate.net wrote:
you read my mind. thanks for this detail.
If nevertheless it is desirable to have postconf -n suppress any
external value of config_directory for the primary instance,
then the patch below may do the job. It is not clear that
Viktor Dukhovni:
On Sat, Sep 27, 2014 at 11:41:08AM -0400, b...@bitrate.net wrote:
you read my mind. thanks for this detail.
If nevertheless it is desirable to have postconf -n suppress any
external value of config_directory for the primary instance,
then the patch below may do the job.
On Sat, Sep 27, 2014 at 02:23:12PM -0400, Wietse Venema wrote:
+if ((config_dir = safe_getenv(CONF_ENV_PATH)) != 0
+strcmp(config_dir, DEF_CONFIG_DIR) != 0) {
I prefer not to lie in software. Thus, config_dir will show up in
postconf -n output when there is any override,
Viktor Dukhovni:
On Sat, Sep 27, 2014 at 02:23:12PM -0400, Wietse Venema wrote:
+if ((config_dir = safe_getenv(CONF_ENV_PATH)) != 0
+ strcmp(config_dir, DEF_CONFIG_DIR) != 0) {
I prefer not to lie in software. Thus, config_dir will show up in
postconf -n output when there is
On Sat, Sep 27, 2014 at 02:51:37PM -0400, Wietse Venema wrote:
In other respects, is the rest of the patch sound (correct and
useful)? I am not advocating that the patch be adopted, just using
postconf does not suppress parameters based on string comparison.
Instead, suppression is based
Viktor Dukhovni:
On Sat, Sep 27, 2014 at 02:51:37PM -0400, Wietse Venema wrote:
In other respects, is the rest of the patch sound (correct and
useful)? I am not advocating that the patch be adopted, just using
postconf does not suppress parameters based on string comparison.
On Sat, Sep 27, 2014 at 03:14:11PM -0400, Wietse Venema wrote:
Viktor Dukhovni:
On Sat, Sep 27, 2014 at 02:51:37PM -0400, Wietse Venema wrote:
In other respects, is the rest of the patch sound (correct and
useful)? I am not advocating that the patch be adopted, just using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.09.2014 13:50, Wietse Venema wrote:
These warnings are produced by the Cyrus SASL library.
Which could be recognizable and self-explanatory as well... Thanks for
the clearification.
- -Kalle
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
26 matches
Mail list logo
