Bug#511037: Looks very similar to that last one ...

dkimsign is not called by dkimproxy, so it is safe to rename it, omit it from the package, or put it in a different location. In the future, dkimsign and dkimverify will probably not be installed to $bindir. Jason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a sub

Bug#509045: python-dkim: tries to overwrite file owned by dkimproxy

Thomas Goirand 12/18/08 1:49 AM >>> > >Now, would it be easy for you to rename dkimverify to something else? I >have put the upstream author (Jason) of dkimproxy as a copy of his email >so he can tell what kind of problems we might find if we rename dkimverify. I don't know the full context

Bug#481796: dkimproxy: fails to authenticate since Perl update to version 5.10

Thomas Goirand <[EMAIL PROTECTED]> 5/19/08 3:06 AM >>> > >In the hope for help, I've also added the upstream author of dkimproxy >to this thread, and the user mailing list of the project: >[EMAIL PROTECTED] It certainly sounds like an issue with the Net::DNS module, which is used by dkimpro