mailman_mail_selinux(8)

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

💅 mailman_mail_selinux — bestie's guide to the SELinux policy for mailman_mail processes ✨

okay so this is mailman_mail_selinux(8), the manual page that ships with the mailman_mail SELinux policy — and yes, we're gonna get through the whole thing together, no skimming, no "tl;dr bestie just read it" 🫶

🌸 NAME 🌸

mailman_mail_selinux — Security Enhanced Linux Policy for the mailman_mail processes. that's it, that's the whole vibe 💅

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the mailman_mail processes via flexible mandatory access control. like, it's the bouncer at the club and the club is your mailman 💖

The mailman_mail processes execute with the mailman_mail_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.

For example:

ps -eZ | grep mailman_mail_t

go off, ps 🔥

🚪 ENTRYPOINTS 🚪

The mailman_mail_t SELinux type can be entered via the mailman_mail_exec_t file type.

The default entrypoint paths for the mailman_mail_t domain are the following:

/usr/mailman.*/mail/wrapper, /usr/lib/mailman.*/mail/mailman,
/usr/lib/mailman.*/mail/wrapper, /usr/lib/mailman.*/bin/mailmanctl,
/usr/lib/mailman.*/scripts/mailman, /usr/lib/mailman.*/bin/mm-handler.*,
/usr/share/doc/mailman.*/mm-handler.*, /usr/lib/mailman/bin/mm-
handler.*, /usr/lib/mailman/mail/mailman,
/usr/lib/mailman/bin/mailmanctl

those are your doors, bestie — walk through one and you're in mailman_mail_t 🎀

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system — think of them as little vibes that each process carries around 🌈

You can see the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. SELinux mailman_mail policy is very flexible allowing users to setup their mailman_mail processes in as secure a method as possible.

The following process types are defined for mailman_mail:

mailman_mail_t

that's the one, the main character 👑

Note: semanage permissive -a mailman_mail_t can be used to make the process type mailman_mail_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.

so like, permissive = no more blocking, but the receipts (AVC messages) are still being printed 🙈 very "i'm not mad i'm just disappointed" energy.

🎚️ BOOLEANS 🎚️

SELinux policy is customizable based on least access required. mailman_mail policy is extremely flexible and has several booleans that allow you to manipulate the policy and run mailman_mail with the tightest access possible. lowkey obsessed with the level of control here 💅

  • 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

the -P is doing the heavy lifting btw — it makes the change persistent across reboots. periodt 💖

📂 MANAGED FILES 📂

The SELinux process type mailman_mail_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. (SELinux is generous, but not that generous — regular file permissions still apply, bestie 🫶)

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

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

mailman_archive_t

/var/lib/mailman.*/archives(/.*)?

mailman_data_t

/etc/mailman.*
/var/lib/mailman(/.*)?
/var/spool/mailman.*

mailman_lock_t

/run/lock/mailman.*
/run/lock/subsys/mailman.*

mailman_log_t

/var/log/mailman.*

mailman_mail_tmp_t

(no default paths listed for this one, she's mysterious like that 🦋)

mailman_var_run_t

/run/mailman.*

root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

that last one literally includes / — like, the whole root directory. iconique, slightly terrifying 💀

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type.

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 mailman_mail policy is very flexible allowing users to setup their mailman_mail processes in as secure a method as possible.

🎀 STANDARD FILE CONTEXT 🎀

SELinux defines the file context types for the mailman_mail, if you wanted to store files with these types in a 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 mailman_mail_exec_t
'/srv/mailman_mail/content(/.*)?'
restorecon -R -v /srv/mymailman_mail_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise up 🌸

The following file types are defined for mailman_mail:

mailman_mail_exec_t

  • Set files with the mailman_mail_exec_t type, if you want to transition an executable to the mailman_mail_t domain.

Paths:

/usr/mailman.*/mail/wrapper, /usr/lib/mailman.*/mail/mailman,
/usr/lib/mailman.*/mail/wrapper, /usr/lib/mailman.*/bin/mailmanctl,
/usr/lib/mailman.*/scripts/mailman, /usr/lib/mailman.*/bin/mm-
handler.*, /usr/share/doc/mailman.*/mm-handler.*,
/usr/lib/mailman/bin/mm-handler.*, /usr/lib/mailman/mail/mailman,
/usr/lib/mailman/bin/mailmanctl

mailman_mail_tmp_t

  • Set files with the mailman_mail_tmp_t type, if you want to store mailman mail temporary files in the /tmp directories.
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 "just for tonight" of labeling and semanage fcontext + restorecon is the "moving in together" 🫶

🛠️ COMMANDS 🛠️

  • 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 boolean can also be used to manipulate the booleans.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings.

a GUI?? for the girlies who don't live in the terminal?? we love options 💅✨

🧚 AUTHOR 🧚

This manual page was auto-generated using sepolicy manpage. (no human author to thank, she was born from a script 😭 iconic honestly)

🔍 SEE ALSO 🔍

selinux(8), mailman_mail(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)

go read those next, bestie, i believe in you 📚💖

and that's the whole page!! this one came from mailman_mail with the date 26-10-06 and the manual tag mailman_mail_selinux(8) — mwah, congrats on finishing, you ate that fr fr 🎀💜🦋

📦 where this page comes from