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
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
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
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: