Your message dated Sat, 29 May 2010 04:11:49 +0800
with message-id <4c002385.7080...@goirand.fr>
and subject line No issue in fact
has caused the Debian Bug report #583355,
regarding dkimproxy can't read it's own private key
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 ow...@bugs.debian.org
immediately.)
--
583355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dkimproxy
Version: 1.2-5
Severity: grave
As I wanted to have dkimproxy behave well, and integrate in the /etc/ssl
folder, using the ssl-cert group, I changed the group of
/var/lib/dkimproxy/privakte.key. As a concequence, dkimproxy cannot read the
key file, and refuses to start.
Because I don't want version 1.2-5 to be migrated to testing, I'm submitting
an RC bug to my own package. A fix will come very soon.
As a reference:
http://forums.gplhost.com/phpBB2/dkimproxy-12-5-var-lib-dkimproxy-privatekey-unreadable-vt2417.html
Thomas
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-4-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
After testing it myself, I can confirm that what I did works. There's on
issue in the current SID package, that can migrate to Testing, so I'm
closing this bug.
Thomas
--- End Message ---
