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) -- package dkimproxy 1.2-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 https://bugs.launchpad.net/bugs/588960 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
