From: russell@coker.com.au (Russell Coker) Date: Fri, 3 Oct 2008 06:29:03 +1000 Subject: [refpolicy] services_amavis.patch In-Reply-To: <1222950698.4240.62.camel@gorn.columbia.tresys.com> References: <48DAA876.2030804@redhat.com> <200809271042.26493.russell@coker.com.au> <1222950698.4240.62.camel@gorn.columbia.tresys.com> Message-ID: <200810030629.08617.russell@coker.com.au> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com On Thursday 02 October 2008 22:31, "Christopher J. PeBenito" wrote: > On Sat, 2008-09-27 at 10:42 +1000, Russell Coker wrote: > > On Thursday 25 September 2008 22:19, Martin Orr wrote: > > > > The CentOS servers that I run have Amavis and ClamAV running > > > > unconfined because getting the policy to work was too difficult (the > > > > two daemons interact with each other a lot, trying to keep them > > > > separate is a lost cause). > > > > > > How do they interact with each other beyond communicating by a socket > > > and clamd reading amavis spool files? > > > > They can communicate by a socket or by running a program. > > Can you clarify what you mean by "running a program"? Amavis can run a clam program. ClamAV can be a daemon or a utility program. Amavis can even be configured to try both methods. -- russell at coker.com.au http://etbe.coker.com.au/ My Blog http://www.coker.com.au/sponsorship.html Sponsoring Free Software development