Created attachment 910501 [details] AVCs in permissive mode Description of problem: If I setup the dovecot-antispam plugin in Dovecot to train wrongly classified messages using DSPAM, SELinux blocks the call to the DSPAM binary and other operations related to updating the token database. Version-Release number of selected component (if applicable): selinux-policy-3.12.1-166.fc20.noarch dovecot-2.2.13-1.fc20.x86_64 The dovecot-antispam was built from source: http://git.sipsolutions.net/?p=dovecot-antispam.git How reproducible: Deterministic Steps to Reproduce: 1. Setup dovecot using IMAP 2. Setup DSPAM 3. Setup the dovecot-antispam plugin: protocol imap { mail_plugins = antispam } plugin { antispam_backend = dspam antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_trash = trash;Trash;Deleted Items;Deleted Messages antispam_spam = SPAM antispam_dspam_binary = /usr/bin/dspam antispam_dspam_args = --user;%u } 4. Try and move a message to the SPAM folder. This will generate AVCs. Additional info: If I run the plugin in permissive mode everything works. I registered the AVCs generated (attached). I run audit2allow and make a module to allow the operations (attached). Even with this module the plugin *still fails*. However, this time *no AVCs* are generated! Using this module the error message is generated by DSPAM, so it was run, but it complains about not being able to create directories that exist. Odd.
Created attachment 910502 [details] Module that fails to make the plugin work, but with no AVCs
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.