spamd_selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

💖 spamd_selinux(8) — SELinux Policy for spamd 🎀

okay bestie, sit down, hydrate, and let's talk about the spamd_selinux manual page — it's the SELinux policy page for the spamd processes, and honestly? it's a lot, but we're gonna slay it together ✨

🌸 NAME 🌸

spamd_selinux — Security Enhanced Linux Policy for the spamd processes 💅

🦋 DESCRIPTION 🦋

Security-Enhanced Linux secures the spamd processes via flexible mandatory access control. no cap, that's the whole vibe — SELinux is the bouncer at the club and spamd has a very specific guest list.

The spamd processes execute with the spamd_t SELinux type. you can check if you've got these processes running by executing the ps command with the -Z qualifier 👑

for example:

ps -eZ | grep spamd_t

that's it, that's the vibe check 🔥

🚪 ENTRYPOINTS 🚪

The spamd_t SELinux type can be entered via the spamd_exec_t file type — that's the doorway, the main character entrance 🌟

the default entrypoint paths for the spamd_t domain are:

  • /usr/bin/spamd
  • /usr/bin/pyzord
  • /usr/bin/spampd
  • /usr/bin/mimedefang
  • /usr/bin/mimedefang-multiplexor
  • /usr/libexec/mimedefang-wrapper

like, those are literally the doors. periodt 🚪✨

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system.

you can see the context of a process using the -Z option to ps 🔍

policy governs the access confined processes have to files. SELinux spamd policy is very flexible, allowing users to set up their spamd processes in as secure a method as possible 🛡️

the following process types are defined for spamd:

  • spamd_update_t
  • spamd_t
Note: semanage permissive -a spamd_t can be used to make the process type spamd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking but it's still gonna gossip about you in the logs 💀

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. spamd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run spamd with the tightest access possible 🔒

if you want to allow spamd to read/write user home directories, you must turn on the spamd_enable_home_dirs boolean. Disabled by default.

setsebool -P spamd_enable_home_dirs 1

if you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.

setsebool -P daemons_dontaudit_scheduling 1

if you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.

setsebool -P fips_mode 1

if you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.

setsebool -P nis_enabled 1

four booleans, four little switches, all iconic in their own way 🌈

🔌 PORT TYPES 🔌

SELinux defines port types to represent TCP and UDP ports.

you can see the types associated with a port by using the following command:

semanage port -l

policy governs the access confined processes have to these ports. SELinux spamd policy is very flexible, allowing users to set up their spamd processes in as secure a method as possible 🫶

the following port types are defined for spamd:

  • spamd_port_t

Default Defined Ports:

tcp 783,10026,10027

those are the ports, bestie. memorize them, they're cute 🍓

📂 MANAGED FILES 📂

The SELinux process type spamd_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. note: the process's UID still needs to have DAC permissions — SELinux is not out here overriding your regular permissions, it's an extra layer, okay? 💅

  • antivirus_db_t
    • /var/amavis(/.*)?
    • /var/clamav(/.*)?
    • /var/lib/clamd.*
    • /var/lib/amavis(/.*)?
    • /var/lib/clamav(/.*)?
    • /var/virusmails(/.*)?
    • /var/opt/f-secure(/.*)?
    • /var/spool/amavisd(/.*)?
    • /var/lib/clamav-unofficial-sigs(/.*)?
  • cifs_t — no default paths listed, it's giving mysterious ✨
  • cluster_conf_t
    • /etc/cluster(/.*)?
  • cluster_var_lib_t
    • /var/lib/pcsd(/.*)?
    • /var/lib/cluster(/.*)?
    • /var/lib/openais(/.*)?
    • /var/lib/pengine(/.*)?
    • /var/lib/corosync(/.*)?
    • /usr/lib/heartbeat(/.*)?
    • /var/lib/heartbeat(/.*)?
    • /var/lib/pacemaker(/.*)?
  • cluster_var_run_t
    • /run/crm(/.*)?
    • /run/cman_.*
    • /run/rsctmp(/.*)?
    • /run/aisexec.*
    • /run/heartbeat(/.*)?
    • /run/pcsd-ruby.socket
    • /run/corosync-qnetd(/.*)?
    • /run/corosync-qdevice(/.*)?
    • /run/pcsd.socket
    • /run/corosync.pid
    • /run/cpglockd.pid
    • /run/rgmanager.pid
    • /run/cluster/rgmanager.sk
  • ecryptfs_t
    • /home/[^/]+/.Private(/.*)?
    • /home/[^/]+/.ecryptfs(/.*)?
  • exim_spool_t
    • /var/spool/exim[0-9]?(/.*)?
  • fusefs_t
    • /run/user/[0-9]+/gvfs
  • krb5_host_rcache_t
    • /var/tmp/krb5_0.rcache2
    • /var/cache/krb5rcache(/.*)?
    • /var/tmp/nfs_0
    • /var/tmp/DNS_25
    • /var/tmp/host_0
    • /var/tmp/imap_0
    • /var/tmp/HTTP_23
    • /var/tmp/HTTP_48
    • /var/tmp/ldap_55
    • /var/tmp/ldap_487
    • /var/tmp/ldapmap1_0
  • logwatch_cache_t
    • /var/lib/epylog(/.*)?
    • /var/lib/logcheck(/.*)?
    • /var/cache/logwatch(/.*)?
  • mail_spool_t
    • /var/mail(/.*)?
    • /var/spool/imap(/.*)?
    • /var/spool/mail(/.*)?
    • /var/spool/smtpd(/.*)?
  • nfs_t — again, no default paths listed 👀
  • root_t
    • /sysroot/.aleph-version.json
    • /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
    • /
    • /initrd
    • /var/lib/ntp
  • spamass_milter_state_t
    • /var/lib/spamass-milter(/.*)?
  • spamc_home_t
    • /root/.pyzor(/.*)?
    • /root/.razor(/.*)?
    • /root/.spamd(/.*)?
    • /root/.spamassassin(/.*)?
    • /home/[^/]+/.pyzor(/.*)?
    • /home/[^/]+/.razor(/.*)?
    • /home/[^/]+/.spamd(/.*)?
    • /home/[^/]+/.spamassassin(/.*)?
  • spamd_compiled_t
    • /var/lib/spamassassin/compiled(/.*)?
  • spamd_etc_t
    • /etc/pyzor(/.*)?
    • /etc/razor(/.*)?
  • spamd_log_t
    • /var/log/spamd.log.*
    • /var/log/mimedefang.*
    • /var/log/pyzord.log.*
    • /var/log/sa-update.log.*
    • /var/log/razor-agent.log.*
  • spamd_spool_t
    • /var/spool/spamd(/.*)?
    • /var/spool/spampd(/.*)?
    • /var/spool/spamassassin(/.*)?
  • spamd_tmp_t — no default paths listed, temporary queen behavior 🌸
  • spamd_var_lib_t
    • /var/lib/razor(/.*)?
    • /var/lib/pyzord(/.*)?
    • /var/lib/spamassassin(/.*)?
  • spamd_var_run_t
    • /run/spamassassin(/.*)?
    • /var/spool/MIMEDefang(/.*)?
    • /var/spool/MD-Quarantine(/.*)?
  • user_home_t
    • /home/[^/]+/.+

that's a whole lotta file types and every single one of them matters, i don't make the rules 💜

🗂️ FILE CONTEXTS 🗂️

SELinux requires files to have an extended attribute to define the file type. it's like a little name tag but for files 🏷️

you can see the context of a file using the -Z option to ls 🔍

policy governs the access confined processes have to these files. SELinux spamd policy is very flexible, allowing users to set up their spamd processes in as secure a method as possible 🛡️

🧚 EQUIVALENCE DIRECTORIES 🧚

spamd policy stores data with multiple different file context types under the /var/lib/spamassassin directory. if you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping ✨

if you wanted to store this data under the /srv directory you would execute the following command:

semanage fcontext -a -e /var/lib/spamassassin /srv/spamassassin
restorecon -R -v /srv/spamassassin

like, that's the whole trick and it's honestly iconic 🎀

📜 STANDARD FILE CONTEXT 📜

SELinux defines the file context types for spamd. if you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk 🖊️

semanage fcontext -a -t spamd_update_exec_t '/srv/spamd/content(/.*)?'
restorecon -R -v /srv/myspamd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. yes, regex, in your labels, it's giving chaos but make it secure 💀

the following file types are defined for spamd:

  • spamd_compiled_t — set files with the spamd_compiled_t type if you want to treat the files as spamd compiled data.
  • spamd_etc_t — set files with the spamd_etc_t type if you want to store spamd files in the /etc directories.
    • Paths:
      • /etc/pyzor(/.*)?
      • /etc/razor(/.*)?
  • spamd_exec_t — set files with the spamd_exec_t type if you want to transition an executable to the spamd_t domain.
    • Paths:
      • /usr/bin/spamd
      • /usr/bin/pyzord
      • /usr/bin/spampd
      • /usr/bin/mimedefang
      • /usr/bin/mimedefang-multiplexor
      • /usr/libexec/mimedefang-wrapper
  • spamd_initrc_exec_t — set files with the spamd_initrc_exec_t type if you want to transition an executable to the spamd_initrc_t domain.
    • Paths:
      • /etc/rc.d/init.d/mimedefang.*
      • /etc/rc.d/init.d/spamd
      • /etc/rc.d/init.d/pyzord
      • /etc/rc.d/init.d/spampd
  • spamd_log_t — set files with the spamd_log_t type if you want to treat the data as spamd log data, usually stored under the /var/log directory.
    • Paths:
      • /var/log/spamd.log.*
      • /var/log/mimedefang.*
      • /var/log/pyzord.log.*
      • /var/log/sa-update.log.*
      • /var/log/razor-agent.log.*
  • spamd_spool_t — set files with the spamd_spool_t type if you want to store the spamd files under the /var/spool directory.
    • Paths:
      • /var/spool/spamd(/.*)?
      • /var/spool/spampd(/.*)?
      • /var/spool/spamassassin(/.*)?
  • spamd_tmp_t — set files with the spamd_tmp_t type if you want to store spamd temporary files in the /tmp directories.
  • spamd_unit_file_t — set files with the spamd_unit_file_t type if you want to treat the files as spamd unit content.
  • spamd_update_exec_t — set files with the spamd_update_exec_t type if you want to transition an executable to the spamd_update_t domain.
    • Paths:
      • /usr/share/spamassassin/sa-update.cron
      • /usr/bin/sa-update
  • spamd_update_unit_file_t — set files with the spamd_update_unit_file_t type if you want to treat the files as spamd update unit content.
    • Paths:
      • /usr/lib/systemd/system/sa-update.timer
      • /usr/lib/systemd/system/sa-update.service
  • spamd_var_lib_t — set files with the spamd_var_lib_t type if you want to store the spamd files under the /var/lib directory.
    • Paths:
      • /var/lib/razor(/.*)?
      • /var/lib/pyzord(/.*)?
      • /var/lib/spamassassin(/.*)?
  • spamd_var_run_t — set files with the spamd_var_run_t type if you want to store the spamd files under the /run or /var/run directory.
    • Paths:
      • /run/spamassassin(/.*)?
      • /var/spool/MIMEDefang(/.*)?
      • /var/spool/MD-Quarantine(/.*)?
Note: file context can be temporarily modified with the chcon command. if you want to permanently change the file context you need to use the semanage fcontext command. this will modify the SELinux labeling database. you will need to use restorecon to apply the labels. so chcon is the temporary tattoo and semanage fcontext + restorecon is the actual commitment, okay? 🙈

okay that's a whole semester's worth of file context lore and we're literally not even done — there's more of this page coming, so keep your hydration up and your labels correct 🧚💖

💅 COMMANDS 💅

okay so these are the other command-line besties that can also poke at the same SELinux settings — not replacements for this page, just tools with main character energy 👑

  • semanage fcontext — can also be used to manipulate default file context mappings ✨
  • semanage permissive — can also be used to manipulate whether or not a process type is permissive 👀
  • semanage module — can also be used to enable/disable/install/remove policy modules 🎀
  • semanage port — can also be used to manipulate the port definitions 🔥
  • semanage boolean — can also be used to manipulate the booleans 💖
  • system-config-selinux — is a GUI tool available to customize SELinux policy settings 🖥️✨

🎀 AUTHOR 🎀

This manual page was auto-generated using sepolicy manpage 🫶

🌈 SEE ALSO 🌈

go read these too, bestie — they're all part of the same little SELinux universe 💫

okay that's the whole page, bestie 💖 this was spamd_selinux(8) from source/version spamd, dated 26-10-06 — slay and stay SELinux-safe ✨💅🦋

📦 where this page comes from