Re: [DNG] upgrade to ascii dkim stopped working

2019-02-28 Thread Gregory Nowak
On Thu, Feb 28, 2019 at 05:55:46PM +0100, info at smallinnovations dot nl wrote: > opendkim (2.11.0~alpha-8) unstable; urgency=medium On systems using > systemd, this version replaces /etc/default/opendkim with the files > /etc/systemd/system/opendkim.service.d/overrride.conf and >

Re: [DNG] upgrade to ascii dkim stopped working

2019-02-28 Thread info at smallinnovations dot nl
On 28-02-19 08:08, KatolaZ wrote: >> Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of >> systemd bugreports, notes about being a native systemd daemon but simply >> not working from postfix. I downgraded opendkim from 2.11 to 2.9 and >> everythings is working again. >> >> Of

Re: [DNG] upgrade to ascii dkim stopped working

2019-02-27 Thread KatolaZ
On Wed, Feb 27, 2019 at 10:30:29PM +0100, info at smallinnovations dot nl wrote: > On 25-02-19 00:18, Gregory Nowak wrote: > > On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl > > wrote: > >> After upgrading a production server to ascii from jessie, opendkim > >> stopped

Re: [DNG] upgrade to ascii dkim stopped working

2019-02-27 Thread J. Fahrner via Dng
Am 2019-02-27 22:30, schrieb info at smallinnovations dot nl: Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of systemd bugreports, notes about being a native systemd daemon but simply not working from postfix. I downgraded opendkim from 2.11 to 2.9 and everythings is

Re: [DNG] upgrade to ascii dkim stopped working

2019-02-27 Thread Gregory Nowak
On Wed, Feb 27, 2019 at 10:30:29PM +0100, info at smallinnovations dot nl wrote: > Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of > systemd bugreports, notes about being a native systemd daemon but simply > not working from postfix. I downgraded opendkim from 2.11 to 2.9

Re: [DNG] upgrade to ascii dkim stopped working

2019-02-27 Thread info at smallinnovations dot nl
On 25-02-19 00:18, Gregory Nowak wrote: > On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl > wrote: >> After upgrading a production server to ascii from jessie, opendkim >> stopped working. When i start opendkim manually i get the error >> "Starting OpenDKIM: install:

Re: [DNG] upgrade to ascii dkim stopped working

2019-02-24 Thread Gregory Nowak
On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl wrote: > After upgrading a production server to ascii from jessie, opendkim > stopped working. When i start opendkim manually i get the error > "Starting OpenDKIM: install: cannot create directory ‘’: No such file or >

[DNG] upgrade to ascii dkim stopped working

2019-02-24 Thread info at smallinnovations dot nl
After upgrading a production server to ascii from jessie, opendkim stopped working. When i start opendkim manually i get the error "Starting OpenDKIM: install: cannot create directory ‘’: No such file or directory". I kept the original configfiles. There is a update remark from debian about when