Half an hour was tormented with OpenDKIM (the package is in lower case) from the Debian sid repository
He didn’t want to listen to his default tcp port, pointed it out in the config, but he still listens to the unix socket.
In htop, I noticed that the daemon starts with the -p local:/var/run/opendkim/opendkim.sock , I looked into its systemd unit and really found the option -p local:/var/run/opendkim/opendkim.sock , as it is not difficult to guess this option indicates that you need to listen to the specified unix socket, it seems to me not to be right, it breaks compatibility with old versions and does not even correspond to the instructions on wiki.debian.org , the instruction is no more than an ancient one I consider https: //wiki.debian.org/opendkim
In connection with these there are several questions:
1. Where to turn? In the description of the package is the email maintainer, do you need him to write to the email?
2. Is there a description of each change in the package, that is, can I find a comment explaining why this argument was added to the unit script?
3. Should I report this "bug"? After all, this argument is probably better understood by a person than me and I would not like to argue with him, and even more so through google translate

1 answer 1

As it turned out, I made a mistake at the expense of the bug, the unit is dynamically generated there and the listening socket is read from / etc / default / opendkim, for some reason I have not considered and generated the unit with the default unix socket, and from the configuration file the socket should not read at all, or rather it is blocked by passing the option -p <сокет считаный с файла /etc/default/opendkim> , after a complete reinstallation of the package, everything was fine.

And now the sequence of actions that I would advise those who wish to send a bug report on a package:
1. Try to first reinstall the package completely and check whether the bug is playing after that.
2. Check carefully whether this is really a bug and not you are doing something wrong.
3. Analyze the bug so that you can describe it normally.
4. Read the information on this link https://wiki.debian.org/reportbug (Thanks @alexander barakin).
5. Install the reportbug package, enter reportbug <имя пакета с багом> and follow the instructions.