postfix – Why is SELinux is preventing opendkim from accessing private key files, and how do I fix it?

I’m trying to set up opendkim with Postfix (on CentOS).

Having copied my known good private key into place, I’m seeing this:

Nov 16 12:54:26 (host.domain) setroubleshoot(10093): SELinux is preventing opendkim from open access on the file /etc/opendkim/keys/(xxxxxx).private. For complete SELinux messages run: sealert -l 8de37e21-88ab-46af-9927-e6040f6bfc97
Nov 16 12:54:26 (host.domain) platform-python(10093): SELinux is preventing opendkim from open access on the file /etc/opendkim/keys/(xxxxxx).private.

       *****  Plugin restorecon (99.5 confidence) suggests   ************************

       If you want to fix the label.
       /etc/opendkim/keys/(xxxxxx).private default label should be etc_t.
       Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
       Do
       # /sbin/restorecon -v /etc/opendkim/keys/(xxxxxx).private

       *****  Plugin catchall (1.49 confidence) suggests   **************************

       If you believe that opendkim should be allowed open access on the (xxxxxx).private file by default.
       Then you should report this as a bug.
       You can generate a local policy module to allow this access.
       Do
       allow this access for now by executing:
       # ausearch -c 'opendkim' --raw | audit2allow -M my-opendkim
       # semodule -X 300 -i my-opendkim.pp