• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Spamassassin DCC Permission issue (SElinux)

Kaspar

API expert
Plesk Guru
Server operating system version
Centos 7.9
Plesk version and microupdate number
18.0.51
I am running into a permission issue after installing DCC for Spamassassin. I suspect this is due to selinux, because when (temporarily) disabling selinux the error is doesn't show. I can't quite figure out how to solve this one.

Code:
dccproc [27291] lock_open(/var/lib/dcc/whiteclnt.dccx): Permission denied; file not writeable for locking
dccproc [27291] open(/var/lib/dcc/map): Permission denied

All files inside the /var/lib/dcc/ directory (and the directory itself) are owned by the popuser user and group. I also did apply selinux security labels to the files.
Code:
restorecon -Rv /usr/bin/cdcc
restorecon -Rv /usr/bin/dcc*
restorecon -Rv /var/lib/dcc/
restorecon -Rv /usr/libexec/dcc/

I suspect I am missing something. Any one any clue? @danami perhaps?
 
@Kaspar Sorry it's been a while since I've looked at DCC. A quick fix might be to make the process type dcc_client_t permissive.

Code:
semanage permissive -a dcc_client_t

Permissive process types are not denied access by SELinux (AVC messages will still be generated).
 
Back
Top