Pyzor is a distributed, collaborative spam detection and filtering network.
All of the rules required to administrate an pyzor environment
Parameter: | Description: | Optional: |
---|---|---|
domain |
Domain allowed access. | No |
role |
The role to be allowed to manage the pyzor domain. | No |
terminal |
The type of the user terminal. | No |
Execute pyzor with a domain transition.
Parameter: | Description: | Optional: |
---|---|---|
domain |
Domain allowed access. | No |
Execute pyzor in the caller domain.
Parameter: | Description: | Optional: |
---|---|---|
domain |
Domain allowed access. | No |
Execute pyzor server in the pyzor domain.
Parameter: | Description: | Optional: |
---|---|---|
domain |
The type of the process performing this action. | No |
Read user pyzor home files.
Parameter: | Description: | Optional: |
---|---|---|
domain |
The type of the process performing this action. | No |
Send generic signals to pyzor
Parameter: | Description: | Optional: |
---|---|---|
domain |
Domain allowed access. | No |
The per role template for the pyzor module.
This template allows pyzor to manage files in a user home directory, creating files with the correct type.
This template is invoked automatically for each user, and generally does not need to be invoked directly by policy writers.
Parameter: | Description: | Optional: |
---|---|---|
userdomain_prefix |
The prefix of the user domain (e.g., user is the prefix for user_t). | No |