[opendmarc-users] Problems with 1.3.2~Beta0..deb and this mailing list failing DMARC

Scott Kitterman sklist at kitterman.com
Mon Nov 7 14:47:20 PST 2016


On Monday, November 07, 2016 10:17:18 PM Mick wrote:
> Hello everyone,
> 
> I upgraded my Debian packages this morning (Debian 9 [stretch] testing)
> and OpenDmarc was upgraded to;
> [opendmarc_1.3.2~Beta0+dfsg-2_amd64.deb]
> .... but after the upgrade OpenDmarc failed to start.
> 
> systemd[1]: Failed to start OpenDMARC Milter.
> systemd[1]: opendmarc.service: Unit entered failed state.
> systemd[1]: opendmarc.service: Failed with result 'exit-code'.
> systemd[1]: opendmarc.service: Service hold-off time over, scheduling
> restart.
> systemd[1]: Stopped OpenDMARC Milter.
> systemd[1]: opendmarc.service: Start request repeated too quickly.
> systemd[1]: Failed to start OpenDMARC Milter.
> systemd[1]: opendmarc.service: Unit entered failed state.
> systemd[1]: opendmarc.service: Failed with result 'start-limit-hit'.
> 
> I tried removal, purging and finally removing dependencies before
> re-installing, still to no avail so have downgraded back to
> [opendmarc_1.3.1+dfsg-4_amd64.deb] using the apt archive cache.
> Thankfully good old faithful 1.3.1 is working fine (once again).
> 
> Packages do break on the testing version of Debian I know, but usually
> they are 'kept back' if there are any dependency issues rather than
> install. Have any dependencies changed? I've only mention this here in
> case those responsible for "Debianising" OpenDmarc may read this list
> and be interested.

Unfortunately no one noticed the problems until after it migrated to Testing.  
I'm the Debian maintainer.  I kind of made a hash of this upload.  I plan to 
update it in the next few days (I fixed some similar issues in opendkim 
packaging today and I'm going to wait just a bit and see if it explodes 
again).

Scott K


More information about the opendmarc-users mailing list