Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I'm not really happy with the SELinux policy for Zarafa. It is very incomplete;
caused a lot of pain already here. Looks like I need to investigate to support
you here.
There are various AVC denieds per default. Furthermore Zarafa is much more
flexible than what the SELinux policy covers at the moment. The policy does
also not cover the proprietary parts of Zarafa which are neccessary in some
business installations.
Can you provide me a link to a howto how to start with a SELinux policy? So
just the AVC msgs are not enough, e.g. not all Zarafa components have proper
contexts.
type=AVC msg=audit(1321836992.613:165593): avc: denied { name_connect } for pid=1386 comm="saslauthd" dest=236 scontext=unconfined_u:system_r:saslauthd_t:s0 tcontext=system_u:object_r:zarafa_port_t:s0 tclass=tcp_socket
type=SYSCALL msg=audit(1321836992.613:165593): arch=c000003e syscall=42 success=no exit=-13 a0=9 a1=89d50c a2=10 a3=7fffb909fe30 items=0 ppid=1385 pid=1386 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(n
one) ses=1298 comm="saslauthd" exe="/usr/sbin/saslauthd" subj=unconfined_u:system_r:saslauthd_t:s0 key=(null)
This won't be reproducible for you now as this piece of software hasn't been
made public yet, but will be in the next weeks. However saslauthd_t must be
able to connect to zarafa_port_t, which should be TCP ports 236/237.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1511.html