not logging to syslog

urable logging subsystem -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services/NPO/\ Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/ beh...@omroep.nl, 035-6773555 \/

Re: not logging to syslog

Op 09/07/2012 om 13:52:04 -0400, schreef Wietse Venema: > Leo Baltus: > > I would like postfix to not log to the default syslog-daemon to > > have better control over where each specific postfix instance logs to. I > > am running multiple instances on a server. > > Pos

Re: not logging to syslog

Op 10/07/2012 om 06:55:43 -0400, schreef Wietse Venema: > Leo Baltus: > > It would be nice if postfix could jut open a logfile and reopen on a > > signal like any other daemon does. > > Sending sighup to sendmail, postsuper, postqueue, etc. would not > be productive. &g

db.h in a non-standard place

IBS="-L$db/lib -ldb" Like http://www.postfix.org/DB_README.html tells me. Attached patch detects '-DHAS_DB' and just skips further tests. Would that be acceptable for future releases? -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services

upgrade to 2.10.1: pass_accept_attr: cannot receive connection attributes: Numerical result out of range

pd6 -o postscreen_cache_map=$data_directory/postscreen_cache_v6 This seems to occur only when upgrading. A stop/start with the same version, either 2.9.6 of 2.10.1, seems to work without a problem. Does anyone have an explanation for this? -- Leo Baltus, internetbeheerder /\

Re: upgrade to 2.10.1: pass_accept_attr: cannot receive connection attributes: Numerical result out of range

Op 19/08/2013 om 12:12:49 +, schreef Viktor Dukhovni: > On Mon, Aug 19, 2013 at 01:28:45PM +0200, Leo Baltus wrote: > > > We are upgrading our postfix instances from 2.9.6 to 2.10.1. > > Have you considered reading the release notes (for Postfix 2.10)? > Well, I d

$daemon_directory [Re: upgrade to 2.10.1: pass_accept_attr: cannot receive connection attributes: Numerical result out of range

Op 19/08/2013 om 10:14:40 -0400, schreef Wietse Venema: > Leo Baltus: > > However, I did notice that postfix exec()'s new processes using the > > path to the binaries it got from > > 'PATH=symlink_to_postfix/sbin postfix start' > > instead

Re: $daemon_directory [Re: upgrade to 2.10.1: pass_accept_attr: cannot receive connection attributes: Numerical result out of range

Op 19/08/2013 om 13:11:04 -0400, schreef Wietse Venema: > Leo Baltus: > > > > However, I did notice that postfix exec()'s new processes using the > > > > path to the binaries it got from > > > > 'PATH=symlink_to_postfix/sbin postfix

Re: $daemon_directory [Re: upgrade to 2.10.1: pass_accept_attr: cannot receive connection attributes: Numerical result out of range'

Op 23/08/2013 om 09:51:07 -0400, schreef Wietse Venema: > Wietse Venema: > > Leo Baltus: > > > Op 19/08/2013 om 13:11:04 -0400, schreef Wietse Venema: > > > > Leo Baltus: > > > > > > > However, I did notice that postfix exec()'s new proc

complementary groups for mail_owner

could set this group as the primary group for mail_owner, but that would break consistency as we embrace the idea of each uid having its own unique gid. Now, is there a compelling reason why mail_owner is not allowed to have supplementary groups? -- Leo Baltus, internetbehe

Re: complementary groups for mail_owner

Hi Wietse, Op 31/07/2008 om 11:52:18 -0400, schreef Wietse Venema: > Unfortunately (for you), Postfix currently does not use supplementary > groups, anywhere. It's not a quick hack to change this. > I can wait :-) Could you elaborate on this, is this a design decision you made?

k8s: auto reload after cert renewal

now I run a cronjob to just restart postfix every day, I gues with some serious hacking I could get postfix reload as a sidecar running in a loop but that would also be suboptimal. Any thoughts on why postfix cannot pick this up automatically? -- Leo Baltus, DevOps engineer serviced...@npo.nl, 035