dovecot_selinux(8)
πΈ dovecot_selinux(8) β the SELinux policy for dovecot, explained π
okay so this is dovecot_selinux, from the SELinux Policy dovecot manual fam π«Ά β and it's literally the whole vibe guide to how SELinux locks down your dovecot processes. buckle up bestie β¨
π« NAME π«
dovecot_selinux β Security Enhanced Linux Policy for the dovecot processes. that's it, that's the tweet π
π¦ DESCRIPTION π¦
Security-Enhanced Linux secures the dovecot processes via flexible mandatory access control. mandatory means you don't get a vote, and honestly? iconic π
The dovecot processes execute with the dovecot_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 dovecot_t
β¨ ENTRYPOINTS β¨
The dovecot_t SELinux type can be entered via the dovecot_exec_t file type. so like, that's the door πͺ
The default entrypoint paths for the dovecot_t domain are the following:
/usr/bin/dovecot
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system β one label per vibe, no cap.
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux dovecot policy is very flexible allowing users to setup their dovecot processes in as secure a method as possible.
The following process types are defined for dovecot:
dovecot_t, doveot_auth_t... no wait, dovecot_t, dovecot_auth_t, dovecot_deliver_t π
Note:semanage permissive -a dovecot_tcan be used to make the process typedovecot_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it's like, "i won't stop you but i WILL be taking notes" π
π BOOLEANS π
SELinux policy is customizable based on least access required. dovecot policy is extremely flexible and has several booleans that allow you to manipulate the policy and run dovecot with the tightest access possible. toggles on toggles, we love to see it ποΈ
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 confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default.
setsebool -P kerberos_enabled 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
π§ MANAGED FILES π§
The SELinux process type dovecot_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. yes, both. SELinux said "and also DAC", she's thorough like that π
cifs_tβ no default paths listed, she's mysterious like that π«οΈ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
data_home_t
/root/.local/share(/.*)?
/home/[^/]+/.local/share(/.*)?
dovecot_spool_t
/var/spool/dovecot(/.*)?
dovecot_tmp_tβ no default paths listed β¨dovecot_var_lib_t
/var/lib/dovecot(/.*)?
/run/dovecot/login/ssl-parameters.dat
dovecot_var_log_t
/var/log/dovecot(/.*)?
/var/log/dovecot.log.*
dovecot_var_run_t
/run/dovecot(-login)?(/.*)?
ecryptfs_t
/home/[^/]+/.Private(/.*)?
/home/[^/]+/.ecryptfs(/.*)?
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
mail_home_rw_t
/root/Maildir(/.*)?
/root/.esmtp_queue(/.*)?
/var/lib/arpwatch/.esmtp_queue(/.*)?
/var/cache/ddclient/.esmtp_queue(/.*)?
/home/[^/]+/.maildir(/.*)?
/home/[^/]+/Maildir(/.*)?
/home/[^/]+/.esmtp_queue(/.*)?
mail_spool_t
/var/mail(/.*)?
/var/spool/imap(/.*)?
/var/spool/mail(/.*)?
/var/spool/smtpd(/.*)?
nfs_tβ no default paths listed πroot_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
security_t
/selinux
user_home_t
/home/[^/]+/.+
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. yes, every file gets a little name tag π·οΈ
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 dovecot policy is very flexible allowing users to setup their dovecot processes in as secure a method as possible.
π EQUIVALENCE DIRECTORIES π
dovecot policy stores data with multiple different file context types under the /var/log/dovecot 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/log/dovecot /srv/dovecot
restorecon -R -v /srv/dovecot
like a "same energy" label for a whole other directory, slay π«
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the dovecot, 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 dovecot_exec_t '/srv/dovecot/content(/.*)?'
restorecon -R -v /srv/mydovecot_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex my beloved π
The following file types are defined for dovecot:
dovecot_auth_exec_tSet files with thedovecot_auth_exec_ttype, if you want to transition an executable to thedovecot_auth_tdomain.
Paths:
/usr/lib/dovecot/auth, /usr/libexec/dovecot/auth,
/usr/libexec/dovecot/dovecot-auth
dovecot_auth_tmp_tSet files with thedovecot_auth_tmp_ttype, if you want to store dovecot auth temporary files in the/tmpdirectories.dovecot_cert_tSet files with thedovecot_cert_ttype, if you want to treat the files as dovecot certificate data.
Paths:
/etc/pki/dovecot(/.*)?, /usr/share/ssl/certs/dovecot.pem,
/usr/share/ssl/private/dovecot.pem
dovecot_deliver_exec_tSet files with thedovecot_deliver_exec_ttype, if you want to transition an executable to thedovecot_deliver_tdomain.
Paths:
/usr/lib/dovecot/deliver, /usr/lib/dovecot/dovecot-lda,
/usr/libexec/dovecot/deliver, /usr/libexec/dovecot/dovecot-lda
dovecot_deliver_tmp_tSet files with thedovecot_deliver_tmp_ttype, if you want to store dovecot deliver temporary files in the/tmpdirectories.dovecot_etc_tSet files with thedovecot_etc_ttype, if you want to store dovecot files in the/etcdirectories.
Paths:
/etc/dovecot(/.*)?, /etc/dovecot.conf.*
dovecot_exec_tSet files with thedovecot_exec_ttype, if you want to transition an executable to thedovecot_tdomain.dovecot_initrc_exec_tSet files with thedovecot_initrc_exec_ttype, if you want to transition an executable to thedovecot_initrc_tdomain.dovecot_keytab_tSet files with thedovecot_keytab_ttype, if you want to treat the files as kerberos keytab files.dovecot_passwd_tSet files with thedovecot_passwd_ttype, if you want to treat the files as dovecot passwd data.dovecot_spool_tSet files with thedovecot_spool_ttype, if you want to store the dovecot files under the/var/spooldirectory.dovecot_tmp_tSet files with thedovecot_tmp_ttype, if you want to store dovecot temporary files in the/tmpdirectories.dovecot_var_lib_tSet files with thedovecot_var_lib_ttype, if you want to store the dovecot files under the/var/libdirectory.
Paths:
/var/lib/dovecot(/.*)?, /run/dovecot/login/ssl-parameters.dat
dovecot_var_log_tSet files with thedovecot_var_log_ttype, if you want to treat the data as dovecot var log data, usually stored under the/var/logdirectory.
Paths:
/var/log/dovecot(/.*)?, /var/log/dovecot.log.*
dovecot_var_run_tSet files with thedovecot_var_run_ttype, if you want to store the dovecot files under the/runor/var/rundirectory.
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. temporarychconis giving "sticker on the laptop that peels off",semanage fcontext+restoreconis giving permanent tattoo π
π«Ά 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 mouse girlies π±οΈβ¨
β AUTHOR β
This manual page was auto-generated using sepolicy manpage . (yes, there's a space before the period, we don't comment on it, she's doing her best π₯Ί)
π SEE ALSO π
selinux(8), dovecot(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), dovecot_auth_selinux(8), dovecot_auth_selinux(8), dovecot_deliver_selinux(8), dovecot_deliver_selinux(8)
(and yes, dovecot_auth_selinux(8) and dovecot_deliver_selinux(8) are each listed twice in the source and we are keeping that energy fr fr, they said it twice because they meant it π)
and that's the whole page bestie, tysm for reading π this was dovecot version 26-10-06, page dovecot_selinux(8) β go forth and label responsibly, mwah ππ¦β¨
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms