--- dkim-milter-1.2.0.dfsg.orig/debian/dkim-filter.default +++ dkim-milter-1.2.0.dfsg/debian/dkim-filter.default @@ -0,0 +1,10 @@ +# Command-line options specified here will override the contents of +# /etc/dkim-filter.conf. See dkim-filter(8) for a complete list of options. +#DAEMON_OPTS="" +# +# Uncomment to specify an alternate socket +# Note that setting this will override any Socket value in dkim-filter.conf +#SOCKET="/var/run/dkim-filter/dkim-filter.sock" +#SOCKET="inet:54321" # listen on all interfaces on port 54321 +SOCKET="inet:8891@localhost" # Ubuntu default - listen on loopback on port 8891 +#SOCKET="inet:12345@192.0.2.1" # listen on 192.0.2.1 on port 12345 --- dkim-milter-1.2.0.dfsg.orig/debian/rules +++ dkim-milter-1.2.0.dfsg/debian/rules @@ -0,0 +1,66 @@ +#!/usr/bin/make -f + +CFLAGS = -Wall -g + +ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) + CFLAGS += -O0 +else + CFLAGS += -O2 +endif + +OBJDIR = obj.$(shell uname -s).$(shell uname -r).$(shell uname -m) + +configure: + +build: build-stamp + +build-stamp: $(CURDIR)/debian/site.config.m4 + dh_testdir + ./Build -f $(CURDIR)/debian/site.config.m4 + touch build-stamp + +clean: + dh_testdir + dh_testroot + rm -f build-stamp + rm -rf $(OBJDIR) + dh_clean + +allclean: clean + rm -rf obj.* + +install: build + dh_testdir + dh_testroot + dh_clean -k + dh_installdirs -a -i + + ./Build install DESTDIR=$(CURDIR)/debian/dkim-filter + #cp -f $(OBJDIR)/libdkim/libdkim.a $(CURDIR)/debian/libdkim-dev/usr/lib + # Remove empty /usr/lib + -rmdir $(CURDIR)/debian/dkim-filter/usr/lib + cp -f $(CURDIR)/debian/dkim-filter.conf $(CURDIR)/debian/dkim-filter/etc/ + +binary-indep: build install + +# Build architecture-dependent files here. +binary-arch: build install + dh_testdir + dh_testroot + dh_installchangelogs + dh_installdocs + dh_installexamples + dh_installinit + dh_installman + dh_link + dh_strip + dh_compress + dh_fixperms + dh_installdeb + dh_shlibdeps + dh_gencontrol + dh_md5sums + dh_builddeb + +binary: binary-indep binary-arch +.PHONY: build clean binary-indep binary-arch binary install configure --- dkim-milter-1.2.0.dfsg.orig/debian/dkim-filter.postrm +++ dkim-milter-1.2.0.dfsg/debian/dkim-filter.postrm @@ -0,0 +1,13 @@ +#!/bin/sh + +set -e + +if [ "$1" = "purge" ]; then + if [ -x /usr/sbin/deluser ] && id -u dkim-filter >/dev/null 2>&1; then + deluser --quiet dkim-filter + fi +fi + +#DEBHELPER# + +exit 0 --- dkim-milter-1.2.0.dfsg.orig/debian/site.config.m4 +++ dkim-milter-1.2.0.dfsg/debian/site.config.m4 @@ -0,0 +1,8 @@ +define(`confCC', `gcc')dnl +define(`confMANROOT',`/usr/share/man/man')dnl +define(`confINSTALL_RAWMAN')dnl +define(`confDONT_INSTALL_CATMAN')dnl +define(`confENVDEF',`-D_FFR_SELECT_SIGN_HEADERS -D_FFR_REQUIRED_HEADERS -D_FFR_SET_REPLY -D_FFR_STATS -D_FFR_ZTAGS')dnl +define(`confNROFF',`/bin/true')dnl +APPENDDEF(`confLIBS', `-lssl -lcrypto')dnl +APPENDDEF(`confLIBDIRS', `-L/usr/lib/libmilter')dnl --- dkim-milter-1.2.0.dfsg.orig/debian/dkim-filter.init +++ dkim-milter-1.2.0.dfsg/debian/dkim-filter.init @@ -0,0 +1,91 @@ +#! /bin/sh +# +### BEGIN INIT INFO +# Provides: dkim-filter +# Required-Start: $syslog +# Required-Stop: $syslog +# Should-Start: $local_fs $network +# Should-Stop: $local_fs $network +# Default-Start: 2 3 4 5 +# Default-Stop: 0 1 6 +# Short-Description: Start the DKIM Milter service +### END INIT INFO + +PATH=/sbin:/bin:/usr/sbin:/usr/bin +DAEMON=/usr/bin/dkim-filter +NAME=dkim-filter +DESC="DKIM Filter" +RUNDIR=/var/run/$NAME +USER=dkim-filter +GROUP=dkim-filter + +# How long to wait for the process to die on stop/restart +stoptimeout=5 + +test -x $DAEMON || exit 0 + +# Include dkim-filter defaults if available +if [ -f /etc/default/dkim-filter ] ; then + . /etc/default/dkim-filter +fi + +# This can be set via Socket option in config file, so it's not required. Set +# by default in Ubuntu in /etc/default/dkim-filter +if [ -n "$SOCKET" ]; then + DAEMON_OPTS="-p $SOCKET $DAEMON_OPTS" + else + DAEMON_OPTS="-p $RUNDIR/dkim-filter.sock $DAEMON_OPTS" +fi + +DAEMON_OPTS="-x /etc/dkim-filter.conf -u $USER -P $RUNDIR/$NAME.pid $DAEMON_OPTS" + +start() { + # Build the run directory if it doesn't exist + if [ ! -d ${RUNDIR} ] ; then + install -o ${USER} -g ${GROUP} -m 755 -d ${RUNDIR} || return 2 + fi + UMASK=`umask` + # Force group-writable socket + umask 002 + start-stop-daemon --start --quiet --exec $DAEMON -- $DAEMON_OPTS + # Detect exit status 64 (no key configured) and handle + ret=$? + # Revert to original umask out of extreme caution + umask $UMASK + if [ $ret -eq 64 ]; then + echo "See /usr/share/doc/dkim-filter/README.Debian.gz for help" + exit 0 + elif [ $ret -ne 0 ]; then + exit $ret + fi +} + +stop() { + start-stop-daemon --stop --retry $stoptimeout --exec $DAEMON +} + +case "$1" in + start) + echo -n "Starting $DESC: " + start + echo "$NAME." + ;; + stop) + echo -n "Stopping $DESC: " + stop + echo "$NAME." + ;; + restart|force-reload) + echo -n "Restarting $DESC: " + stop + start + echo "$NAME." + ;; + *) + N=/etc/init.d/$NAME + echo "Usage: $N {start|stop|restart|force-reload}" >&2 + exit 1 + ;; +esac + +exit 0 --- dkim-milter-1.2.0.dfsg.orig/debian/docs +++ dkim-milter-1.2.0.dfsg/debian/docs @@ -0,0 +1,3 @@ +FEATURES +KNOWNBUGS +README --- dkim-milter-1.2.0.dfsg.orig/debian/dkim-filter.examples +++ dkim-milter-1.2.0.dfsg/debian/dkim-filter.examples @@ -0,0 +1,2 @@ +dkim-filter/dkim-filter.conf.sample +dkim-filter/gentxt.csh --- dkim-milter-1.2.0.dfsg.orig/debian/compat +++ dkim-milter-1.2.0.dfsg/debian/compat @@ -0,0 +1 @@ +4 --- dkim-milter-1.2.0.dfsg.orig/debian/dkim-filter.postinst +++ dkim-milter-1.2.0.dfsg/debian/dkim-filter.postinst @@ -0,0 +1,26 @@ +#!/bin/sh + +set -e + +if [ "$1" = "configure" ]; then + if ! id -u dkim-filter >/dev/null 2>&1; then + adduser --quiet --system --group --home /var/run/dkim-filter dkim-filter + elif [ -n "$2" ] && dpkg --compare-versions "$2" lt "1.2.0.dfsg-1"; then + # Versions < 1.2.0.dfsg-1 shipped without the dkim-filter group + addgroup --quiet --system dkim-filter + usermod -g dkim-filter dkim-filter + fi + + # Set ownership if the admin has not overriden it. + if ! dpkg-statoverride --list /var/run/dkim-filter >/dev/null; then + # Build the run directory if it doesn't exist to make sure chown doesn't fail + if [ ! -d ${RUNDIR} ] ; then + install -o ${USER} -g ${GROUP} -m 755 -d ${RUNDIR} || return 2 + fi + chown dkim-filter:dkim-filter /var/run/dkim-filter + fi +fi + +#DEBHELPER# + +exit 0 --- dkim-milter-1.2.0.dfsg.orig/debian/copyright +++ dkim-milter-1.2.0.dfsg/debian/copyright @@ -0,0 +1,85 @@ +This package was debianized by Mike Markley on +Wed, 2 Nov 2005 15:52:53 -0800. + +It was downloaded from http://sourceforge.net/projects/dkim-milter + +Copyright Holder: Sendmail Inc. + +License: + SENDMAIL OPEN SOURCE LICENSE + +The following license terms and conditions apply to this open source +software ("Software"), unless a different license is obtained directly +from Sendmail, Inc. ("Sendmail") located at 6425 Christie Ave, Fourth +Floor, Emeryville, CA 94608, USA. + +Use, modification and redistribution (including distribution of any +modified or derived work) of the Software in source and binary forms is +permitted only if each of the following conditions of 1-6 are met: + +1. Redistributions of the Software qualify as "freeware" or "open + source software" under one of the following terms: + + (a) Redistributions are made at no charge beyond the reasonable + cost of materials and delivery; or + + (b) Redistributions are accompanied by a copy of the modified + Source Code (on an acceptable machine-readable medium) or by an + irrevocable offer to provide a copy of the modified Source Code + (on an acceptable machine-readable medium) for up to three years + at the cost of materials and delivery. Such redistributions must + allow further use, modification, and redistribution of the Source + Code under substantially the same terms as this license. For + the purposes of redistribution "Source Code" means the complete + human-readable, compilable, linkable, and operational source + code of the redistributed module(s) including all modifications. + +2. Redistributions of the Software Source Code must retain the + copyright notices as they appear in each Source Code file, these + license terms and conditions, and the disclaimer/limitation of + liability set forth in paragraph 6 below. Redistributions of the + Software Source Code must also comply with the copyright notices + and/or license terms and conditions imposed by contributors on + embedded code. The contributors' license terms and conditions + and/or copyright notices are contained in the Source Code + distribution. + +3. Redistributions of the Software in binary form must reproduce the + Copyright Notice described below, these license terms and conditions, + and the disclaimer/limitation of liability set forth in paragraph + 6 below, in the documentation and/or other materials provided with + the binary distribution. For the purposes of binary distribution, + "Copyright Notice" refers to the following language: "Copyright (c) + 1998-2004 Sendmail, Inc. All rights reserved." + +4. Neither the name, trademark or logo of Sendmail, Inc. (including + without limitation its subsidiaries or affiliates) or its contributors + may be used to endorse or promote products, or software or services + derived from this Software without specific prior written permission. + The name "sendmail" is a registered trademark and service mark of + Sendmail, Inc. + +5. We reserve the right to cancel this license if you do not comply with + the terms. This license is governed by California law and both of us + agree that for any dispute arising out of or relating to this Software, + that jurisdiction and venue is proper in San Francisco or Alameda + counties. These license terms and conditions reflect the complete + agreement for the license of the Software (which means this supercedes + prior or contemporaneous agreements or representations). If any term + or condition under this license is found to be invalid, the remaining + terms and conditions still apply. + +6. Disclaimer/Limitation of Liability: THIS SOFTWARE IS PROVIDED BY + SENDMAIL AND ITS CONTRIBUTORS "AS IS" WITHOUT WARRANTY OF ANY KIND + AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A + PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. IN NO EVENT SHALL SENDMAIL + OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED + TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, + OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY + OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING + WITHOUT LIMITATION NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE + USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + +$Revision: 1.1 $ $Date: 2006-10-21 23:55:19 $ --- dkim-milter-1.2.0.dfsg.orig/debian/control +++ dkim-milter-1.2.0.dfsg/debian/control @@ -0,0 +1,18 @@ +Source: dkim-milter +Section: mail +Priority: extra +Maintainer: Ubuntu MOTU Developers +XSBC-Original-Maintainer: Mike Markley +Build-Depends: debhelper (>= 4.0.0), m4, libmilter-dev, libssl-dev, libdb4.5-dev | libdb-dev +Standards-Version: 3.7.2 + +Package: dkim-filter +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends}, adduser +Description: DomainKeys Identified Mail for Sendmail + Implements a Sendmail Mail Filter (Milter) for the DomainKeys + Identified Mail (DKIM) standard. DKIM provides a way for senders to + confirm their identity when sending email by adding a cryptographic + signature to the headers of the message. + . + The dkim-milter implements both signing and verification. --- dkim-milter-1.2.0.dfsg.orig/debian/README.Debian +++ dkim-milter-1.2.0.dfsg/debian/README.Debian @@ -0,0 +1,111 @@ +dkim-milter for Debian +---------------------- + +Generating a key and publishing a TXT record +-------------------------------------------- + +The DKIM spec requires an RSA key between 512 and 2048 bits in length. +It also requires 1024 for keys that are "long-lived", so 1024 is a +good safe starting point. A simple recipe for generating the private +key file and the corresponding public key text follows; alternately, +you may use the gentxt.csh sample script provided in the directory +/usr/share/doc/dkim-filter/examples. + +$ openssl genrsa -out key 1024 +$ openssl rsa -in key -pubout -outform pem + +Note that this private key should be installed such that it's readable +only by the filter itself and any other software requiring access to +it. Anyone who is able to access it will be able to sign mail as your +domain. The maintainer's recommendation: Change the key file's ownership +to dkim-filter and its permissions to 400 (read-only by owner). + +The public key will go into your DNS TXT record under the name +._domainkey. The TXT record contains a number of tag/value +pairs as described in the DKIM specification. The required p= tag +contains the PEM-formatted (that is, base64-encoded DER) public key, +no header, footer, newlines or spaces. This can be obtained using +a command line like this: + +$ openssl rsa -in key -pubout -outform pem 2>/dev/null | \ +grep -v "^-" | tr -d '\n' + +Other useful but optional flags include k= (the key type, "rsa" +by default) and t= (which can have any of the flags "t" and "s", +indicating, respectively, testing mode and scope). Testing mode +instructs recipients to treat signed and unsigned email the same, +allowing the generation and verification of signatures without +any action (yet) being taken. + +For example: example.com wishes to sign all of their mail with DKIM. +They choose the selector "mail" and decide, for now, to indicate that +they are in testing mode", until they've verified their configuration. +They might put the following in their DNS: + +mail._domainkey.example.com TXT "k=rsa; t=y; p=" + +In addition, some receivers may support DomainKeys-style sender policy +as described in the DomainKeys specification at +http://www.ietf.org/internet-drafts/draft-delany-domainkeys-base-06.txt. +This particular build lacks DKIM SSP (Sender Signing Policy) support, as +that specification is still in its early stages and is subject to change +quite a bit. + +Note that this is not an exhaustive list of features or tags; see below +for a link to the DKIM specifications. + +General package notes +--------------------- + +Note that as of 0.5.2, the dkim-milter source contains several IETF +documents. These have been removed from the source tarball, but are +still accessible via the IETF web site. The removed documents are: + +http://tools.ietf.org/id/draft-hoffman-dac-vbr-00.txt +http://tools.ietf.org/id/draft-ietf-dkim-overview-05.txt +http://tools.ietf.org/id/draft-ietf-dkim-ssp-00.txt +http://tools.ietf.org/id/draft-ietf-dkim-ssp-requirements-04.txt +http://www.ietf.org/rfc/rfc4686.txt +http://www.ietf.org/rfc/rfc4871.txt + +As of the 0.6.x series, upstream intends to make the config file the +primary means of configuring the dkim-filter. As such, configuration +options have been moved into /etc/dkim-filter.conf as of 0.6.1-1. + +Notes for Postfix users +----------------------- + +Postfix users who wish to access the dkim-filter service via UNIX socket +(the default) may need to add their postfix user to the dkim-filter +group. The socket is writable by that group. + +Users may also need to move the socket into a directory accessible by the +Postfix chroot; this can be accomplished by setting the SOCKET variable +in /etc/default/dkim-filter. + +Alternately, you may opt to connect to the filter via TCP port. The +filter can be bound to localhost to prevent other hosts from accessing it. + + -- Mike Markley Wed, 27 Jun 2007 19:55:14 -0700 + +Notes for Ubuntu specific changes +-------------------------------- + +Postfix is the standard MTA in Ubuntu, so the dkim-filter init is modified +to use a TCP socket on localhost port 8891 when installed. This will work +with a chrooted Postfix (the Ubuntu default configuration). To use the +dkim-filter, add: + +# Milters for mail that arrives via the smtpd(8) server. +smtpd_milters = inet:localhost:8891 +milter_macro_daemon_name = SIGNING + +to your main.cf + +By default, if the milter is not available Postfix will defer messages. You +change this by also adding: + +milter_default_action = accept + +See the Postfix MILTER_README for additional information. + --- dkim-milter-1.2.0.dfsg.orig/debian/changelog +++ dkim-milter-1.2.0.dfsg/debian/changelog @@ -0,0 +1,98 @@ +dkim-milter (1.2.0.dfsg-1ubuntu2) gutsy; urgency=low + + * Clean up change from Unix socket to TCP socket: + - Make TCP socket default $SOCKET in debian/dkim-filter.default + - Change debian/dkim-filter.init to use $SOCKET from .default if provided + but fall back to Unix socket if a .default isn't provided. + - Update comments in debian/dkim-filter.default and debian/DEBIAN.Readme + * Add test/install of pid dir to debian/dkim-filter.postinst to be safe + + -- Scott Kitterman Thu, 16 Aug 2007 15:55:47 -0400 + +dkim-milter (1.2.0.dfsg-1ubuntu1) gutsy; urgency=low + + * Because /var/run is a tempfs in Ubuntu, add test/install of + pid dir in debian/dkim-filter.init + * Change default connection method from socket to localhost port 8891 in + debian/dkim-filter.default and comment out socket in + debian/dkim-filter.init for Postfix chroot compatibility + * In debian/DEBIAN.Readme describe the changes in default configuration + and Postfix configuration changes needed to use dkim-filter + * Change maintainer to MOTU + + -- Scott Kitterman Wed, 18 Jul 2007 02:46:06 +0000 + +dkim-milter (1.2.0.dfsg-1) unstable; urgency=low + + * New upstream version + * Support setting listening socket in /etc/default/dkim-filter + * Minor rephrasing of deluser test in postrm so the if block can + be later extended if needed + * Fixes for socket permissions; Closes: #428392 + - Create dkim-filter group and assign as primary GID of same user + in postinst + - Set umask in init script to force group writable socket + - dkim-filter now picks up primary GID of its run user + - Added a doc note for Postfix users who need write permissions + to the socket + * Remove pidfile on normal shutdown + + -- Mike Markley Tue, 26 Jun 2007 20:22:10 -0700 + +dkim-milter (1.0.0.dfsg-1) unstable; urgency=low + + * New upstream version + * Removed bits to rename dkim-filter.conf.4 to dkim-filter.conf.5 + since it's been corrected upstream + * Define confNROFF to /bin/true. Lack of nroff was causing the target + install-docs to fail, resulting in man pages not being installed. + nroff is only needed here for catman pages, which we don't install. + Closes: #425324 + * Updated conf file comments to reflect new default signing algorithm + version rfc4871 + * Made postrm deluser conditional on deluser availability + + -- Mike Markley Thu, 24 May 2007 22:27:04 -0700 + +dkim-milter (0.8.0.dfsg-1) unstable; urgency=low + + * New upstream version + * Fixed spurious : in init script restart stanza. + * KeyList comments in dkim-filter.conf had KeyFile instead of KeyList + as the commented-out option; fixed. + * Removed dkim-stats patch as it's been integrated upstream + * Removed dkim-stats manpage for same reason + * Removed _FFR_REPORTINFO & _FFR_QUARANTINE; they've been activated + upstream + * Added new _FFR_ZTAGS to provide DiagnosticDirectory option + * Add -L/usr/lib/libmilter to confLIBDIRS to support libmilter0 -> + libmilter1 transition. Also fixes FTBFS and Closes: #423758. + + -- Mike Markley Sat, 19 May 2007 14:07:02 -0700 + +dkim-milter (0.7.0.dfsg-1) unstable; urgency=low + + * New upstream version + * Reversioned source package with .dfsg since we've repackaged it with + IETF documents removed + * Added SET_REPLY feature to compile options + * Strategic rewording of description to reference upstream name and + ensure we can be found via a search + * Versions 0.6.5 and above exit with EX_USAGE if no key & selector + are configured. The init script now catches this cleanly and points + towards the README, which allows clean initial installs. In the + near future, this will likely be supplemented with a key generation + helper in postinst. + * Removed _FFR_MULTIPLE_KEYS and _FFR_OMIT_HEADERS from site.config.m4 + since they're now enabled by default + * Added _FFR_STATS and requisite build-deps on libdb4.5-dev | libdb-dev + * Applied patch for dkim-stats from Graham Murray on dkim-milter-discuss + + -- Mike Markley Sat, 05 May 2007 19:12:39 -0700 + +dkim-milter (0.6.4-1) unstable; urgency=low + + * New upstream version + * Initial upload to Debian archive + + -- Mike Markley Sat, 21 Apr 2007 20:05:04 -0700 --- dkim-milter-1.2.0.dfsg.orig/debian/dirs +++ dkim-milter-1.2.0.dfsg/debian/dirs @@ -0,0 +1,6 @@ +etc +usr/bin +usr/lib +usr/share/man/man5 +usr/share/man/man8 +var/run/dkim-filter --- dkim-milter-1.2.0.dfsg.orig/debian/dkim-filter.conf +++ dkim-milter-1.2.0.dfsg/debian/dkim-filter.conf @@ -0,0 +1,49 @@ +# Sane defaults: log to syslog +Syslog yes + +# Sign for example.com with key in /etc/mail/dkim.key using +# selector '2007' (e.g. 2007._domainkey.example.com) +#Domain example.com +#KeyFile /etc/mail/dkim.key +#Selector 2007 + +# This section attempts to describe the default settings. +# See dkim-filter.conf(5) for more information. +#AutoRestart no +#Background yes +#Canonicalization simple +#DNSTimeout 5 +#Mode sv +#SignatureAlgorithm rsa-sha256 +#SubDomains no +#Version rfc4871 +#X-Header no + +############################################### +# Other (less-standard) configuration options # +############################################### +# +# If enabled, log verification stats here +#Statistics /var/run/dkim-filter/dkim-stats +# +# KeyList is a file containing tuples of key information. Requires +# KeyFile to be unset. Each line of the file should be of the format: +# sender glob:signing domain:signing key file +# Blank lines and lines beginning with # are ignored. Selector will be +# derived from the key's filename. +#KeyList /etc/dkim-keys.conf +# +# If enabled, will generate verification failure reports for any messages +# that fail signature verification. These will be sent to the r= address +# in the policy record, if any. +#ReportInfo yes +# +# If enabled, will issue a Sendmail QUARANTINE for any messages that fail +# signature verification, allowing them to be inspected later. +#Quarantine yes +# +# If enabled, will check for required headers when processing messages. +# At a minimum, that means From: and Date: will be required. Messages not +# containing the required headers will not be signed or verified, but will +# be passed through +#RequiredHeaders yes --- dkim-milter-1.2.0.dfsg.orig/dkim-filter/dkim-filter.c +++ dkim-milter-1.2.0.dfsg/dkim-filter/dkim-filter.c @@ -5639,6 +5639,9 @@ dkimf_zapkey(); + if (pidfile != NULL) + unlink(pidfile); + return status; #endif /* DEBUG */ }