Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Packages in EPEL are high-quality add-on packages that complement the Red Hat Enterprise Linux and are prepared for a specific RHEL version. However, you can find rpm package for this tool in EPEL. As of this article in the knowledge base part of Red Hat Customer Portal,
https://access.redhat.com/solutions/3358
How to use Extra Packages for Enterprise Linux (EPEL)
the EPEL project is led by community-led volunteers, packages from this project are not provided by Red Hat and therefore they are not supported.
Closing this bz, I've just cloned it though for addressing in Fedora.
Description of problem: SELinux blocks postfix from connecting to the openarc milter. Version-Release number of selected component (if applicable): selinux-policy-38.1.11-2.el9_2.3.noarch How reproducible: Always Steps to Reproduce: 1. Configure postfix to add the openarc milter 2. 3. Actual results: type=AVC msg=audit(1687527199.794:156): avc: denied { write } for pid=4174 comm="smtpd" name="openarc.sock" dev="tmpfs" ino=1105 scontext=system_u:system_r:postfix_smtpd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=sock_file permissive=1 Expected results: Successful connection. Additional info: Current dkim_milter_data_t is as follows. [root@seawitch ~]# semanage fcontext -l | grep dkim_milter_data_t /var/lib/dkim-milter(/.*)? all files system_u:object_r:dkim_milter_data_t:s0 /var/run/dkim-milter(/.*)? all files system_u:object_r:dkim_milter_data_t:s0 /var/run/opendkim(/.*)? all files system_u:object_r:dkim_milter_data_t:s0 /var/run/opendmarc(/.*)? all files system_u:object_r:dkim_milter_data_t:s0 /var/spool/opendkim(/.*)? all files system_u:object_r:dkim_milter_data_t:s0 /var/spool/opendmarc(/.*)? all files system_u:object_r:dkim_milter_data_t:s0 The /run/openarc directory is missing: [root@seawitch ~]# ls -alZ /run/openarc total 4 drwxr-x---. 2 openarc openarc system_u:object_r:var_run_t:s0 80 Jun 24 10:43 . drwxr-xr-x. 60 root root system_u:object_r:var_run_t:s0 1480 Jun 24 10:44 .. -rw-rw----. 1 openarc openarc system_u:object_r:var_run_t:s0 5 Jun 24 10:43 openarc.pid srwxrwx---. 1 openarc openarc system_u:object_r:var_run_t:s0 0 Jun 24 10:43 openarc.sock Workaround: semanage fcontext -a -t dkim_milter_data_t '/var/run/openarc(/.*)?'