Your message dated Fri, 29 Dec 2023 15:12:58 +0100
with message-id <[email protected]>
and subject line Fwd: Bug#1059520: opendkim: Crashes when postfix accesses
opendkim.sock
has caused the Debian Bug report #1059520,
regarding opendkim: Crashes when postfix accesses opendkim.sock
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1059520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059520
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: opendkim
Version: 2.11.0~beta2-8+deb12u1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
when i send an email via postfix from localhost postfix logs the following:
warning: milter unix:/run/opendkim/opendkim.sock: can't read SMFIC_EOH reply
packet header: Application error
when i inspect the opendkim log i see:
opendkim.service: Failed with result 'signal'.
opendkim.service: Main process exited, code=killed, status=11/SEGV
running opendkim from command line with "-vf" gives "segmentation fault" in the
moment i send an email.
Please let me know if you need something else.
Greetings,
Markus
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-16-cloud-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages opendkim depends on:
ii adduser 3.134
ii dns-root-data 2023010101
ii init-system-helpers 1.65.2
ii libbsd0 0.11.7-2
ii libc6 2.36-9+deb12u3
ii libdb5.3 5.3.28+dfsg2-1
ii libldap-2.5-0 2.5.13+dfsg-5
ii liblua5.3-0 5.3.6-2
ii libmemcached11 1.1.4-1
ii libmilter1.0.1 8.17.1.9-2
ii libopendbx1 1.4.6-16+b1
ii libopendkim11 2.11.0~beta2-8+deb12u1
ii librbl1 2.11.0~beta2-8+deb12u1
ii libssl3 3.0.11-1~deb12u2
ii libunbound8 1.17.1-2+deb12u1
ii libvbr2 2.11.0~beta2-8+deb12u1
ii sysvinit-utils [lsb-base] 3.06-4
Versions of packages opendkim recommends:
ii opendkim-tools 2.11.0~beta2-8+deb12u1
opendkim suggests no packages.
-- Configuration Files:
/etc/opendkim.conf changed:
Syslog yes
SyslogSuccess yes
Canonicalization relaxed/simple
Mode sv
OversignHeaders From
UserID opendkim
UMask 007
Socket local:/run/opendkim/opendkim.sock
PidFile /run/opendkim/opendkim.pid
TrustAnchorFile /usr/share/dns/root.key
InternalHosts refile:/etc/opendkim/trusted
ExternalIgnoreList refile:/etc/opendkim/trusted
SigningTable refile:/etc/opendkim/signing.table
KeyTable /etc/opendkim/key.table
SignatureAlgorithm rsa-sha256
-- no debconf information
--- End Message ---
--- Begin Message ---
Poor style from opendkim to simply crash when misconfigured. But the
reporter’s problem is solved, so closing this bug.
-------- Forwarded Message --------
Subject: Re: Bug#1059520: opendkim: Crashes when postfix accesses opendkim.sock
Date: Wed, 27 Dec 2023 17:49:24 +0100
From: Markus Mitsch <[email protected]>
To: David Bürgin <[email protected]>
Hi,
finally:
DKIM-Signature field added (s=202312, d=mitschnet.de)
I thank you for pointing me to the config again. I followed an
incorrect tutorial and my key and signing table files were misformed.
I should have checked that, sorry.
Greetings
Markus
--- End Message ---
