package dkimproxy 1.2-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Sig]

Binary package hint: dkimproxy

trying to install from Software Center.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: dkimproxy 1.2-3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Wed Jun 2 18:09:35 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: dkimproxy
Title: package dkimproxy 1.2-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Ubunter (samer-alnasir)]

I got the same, in relation with dtc-toaster, each one drop the error to the other, any news???

[adrian donraadt (adriandonraadt)]

adrian@adrians-compaq:~$ sudo apt-get install dkimproxy
[sudo] password for adrian:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De status informatie wordt gelezen... Klaar
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
  dkimproxy
0 pakketten opgewaardeerd, 1 pakketten nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
Er moeten 0B/44,5kB aan archieven opgehaald worden.
Door deze operatie zal er 262kB extra schijfruimte gebruikt worden.
Selecteren van voorheen niet geselecteerd pakket dkimproxy.
(Database inlezen ... 482909 bestanden en mappen geïnstalleerd.)
Uitpakken van dkimproxy (uit .../dkimproxy_1.2-3_all.deb) ...
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Instellen van dkimproxy (1.2-3) ...
addgroup: De groep `dkimproxy' bestaat reeds als systeemgroep. Stoppen.
De systeemgebruiker `dkimproxy' bestaat reeds. Stoppen.
 * Starting inbound DomainKeys-filter dkimproxy.in Unknown option: hostname
Usage:
      dkimproxy.in [options] LISTENADDR:PORT RELAYADDR:PORT
        smtp options:
          --conf_file=FILENAME
          --listen=LISTENADDR:PORT
          --relay=RELAYADDR:PORT
          --reject-error

        verification options:
          --reject-fail
          --hostname=HOSTNAME

        daemon options:
          --daemonize
          --user=USER
          --group=GROUP
          --pidfile=PIDFILE

      dkimproxy.in --help
        to see a full description of the various options

                                                                                                                                                      [fail]
invoke-rc.d: initscript dkimproxy, action "start" failed.
dpkg: fout bij afhandelen van dkimproxy (--configure):
 subproces installed post-installation script gaf een foutwaarde 2 terug
Fouten gevonden tijdens behandelen van:
 dkimproxy
E: Sub-process /usr/bin/dpkg returned an error code (1)

adrian@adrians-compaq:~$ dkimproxy.in LISTENADDR:143 RELAYADDR:143
Becoming sub class of "Net::Server::PreFork"
2010/08/06-14:52:49 main (type MySmtpProxyServer) starting! pid(19157)
Binding to TCP port 143 on host LISTENADDR
2010/08/06-14:52:49 Can't connect to TCP port 143 on LISTENADDR [Ongeldig argument]
  at line 88 in file /usr/share/perl5/Net/Server/Proto/TCP.pm
2010/08/06-14:52:49 Server closing!

[UndiFineD (k.dejong)]

issue persists with version 1.2-5

[UndiFineD (k.dejong)]

I had a small but important detail removed from the /etc/init.d/dkimproxy startup script.
I changed the line with `hostname -d` to `hostname`
and now dkimproxy started ok
it seems that hostname -d resolves to ''
that's right, nothing. now this may be a problem with my configuration
but so far everything else works fine.

now dpkg still thinks dkimproxy and dtc-toaster are unconfigured

[UndiFineD (k.dejong)]

fixed it :-)

root@head:~# /etc/init.d/dkimproxy stop
 * Shutting down inbound DomainKeys-filter dkimproxy.in [ OK ]
 * Shutting down outbound DomainKeys-filter dkimproxy.out [ OK ]
root@head:~# dpkg --configure dkimproxy
Setting up dkimproxy (1.2-5) ...
addgroup: The group `dkimproxy' already exists as a system group. Exiting.
The system user `dkimproxy' already exists. Exiting.
The user `dkimproxy' is already a member of `ssl-cert'.
 * Starting inbound DomainKeys-filter dkimproxy.in [ OK ]
 * Starting outbound DomainKeys-signing dkimproxy.out [ OK ]

root@head:~# dpkg --configure dtc-toaster
Setting up dtc-toaster (0.30.10-1) ...
root@head:~#

[Thomas Goirand (thomas-goirand)]

Hi,

I can confirm that there's absolutely NO issue in dkimproxy when I read the above. Here, the issue is a user that didn't know how to setup the hostname of his server before doing any kind of setup. Using:

hostname -d

should return a valid domain name, which it seems it didn't. This is a configuration issue not directly related to dkimproxy, which has a lot of chances to break many other things.

Also, I have just uploaded dkimproxy 1.2-6 to SID that fixes the ownership of the privatekey of dkimproxy. I would highly recommend that you guys synch from the new SID version, for which I will ask a freeze exception so that it enters Squeeze.

The maintainer,

Thomas Goirand (zigo)

[Alexander Milanov (amilanov-deactivatedaccount)]

I'm a bit late, but I can also confirm that this is an issue of hostname without domain name. I had the same problem when I first tried to install dkimproxy.

All you have to do is add a domain name to your hostname. I wrote an article on that (http://amilanov.com/articles/how-to-setup-dkim-signing-on-ubuntu/), if you need a guide.

Actually, UndiFineD almost got it.

[pked (pked09)]

Hi Alex

Thanks for that mate .
I will have a look at your guide

On 11/10/10 18:38, Alexander Milanov wrote:
> I'm a bit late, but I can also confirm that this is an issue of hostname
> without domain name. I had the same problem when I first tried to
> install dkimproxy.
>
>
> All you have to do is add a domain name to your hostname. I wrote an
> article on that (http://amilanov.com/articles/how-to-setup-dkim-signing-
> on-ubuntu/), if you need a guide.
>
>
> Actually, UndiFineD almost got it.
>
>