search for: mail_spool_t

...ser group 35864Jun 10 03:35 ../ drw-------. 6 user group 4096 Jun 10 03:35 2004/ -rw-------. 6 user group 155296 Jun 10 03:35 2014_10_Jun_learned_spam -rw-------. 6 user group 996584 Jun 10 03:35 2014_10_Jun_learned_ham also as root: ls -laZlearned drw-------. 6 user group unconfined_u:object_r:mail_spool_t:s0. drw-------. 6 user group unconfined_u:object_r:mail_spool_t:s0.. drw-------. 6 user group unconfined_u:object_r:mail_spool_t:s02004 -rw-------. 6 user group system_u:object_r:mail_spool_t:s02014_10_Jun_learned_spam -rw-------. 6 user group system_u:object_r:mail_spool_t:s02014_10_Jun_learned_ha...

Hello, can any tell me the correct selinux Settings for the Maildir Setting ? in the Moment I have this setting Jan 8 15:04:52 2017 from 192.168.100.100 [root at mx03 ~]# ls -Z /srv/vmail drwx------. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 example.com drwx------. vmail vmail unconfined_u:object_r:mail_home_rw_t:s0 example.at drwx------. vmail vmail

Hi, I have set-up dovecot on a F17 box and am encountering weirdnesses with SELinux (who isn't??). Again, I am trying to refrain from disabling SWLinux all together, however tempting, but am stuck in troubleshooting and hope for some ideas... With SELinux set to permissive, I can connect to dovecot and log in to access my mail as expected. With SELinux enforcing, I can connect to dovecot,

...x security context after being restored. When the file was restored, it was assigned a context of "root:object_r:file_t", which is not a context that the Dovecot service has permissions to interact with. I had to re-label the files after restoring them with # chcon -R user_u:object_r:mail_spool_t foldername So the lesson here is to check /var/log/messages and look for sealert indicators when restoring files. ... Hopefully that helps some other people out when dealing with Red Hat / CentOS with SELinux set to enforcing mode.