On Tue, 6 Jun 2006, David Wheeler wrote:
On Jun 6, 2006, at 06:34, John Peacock wrote:
Nonetheless, Bricolage will be communicating with the qpsmtpd service via
an ip port (doesn't have to be 25), so there is no reason that qpsmtpd
needs to be the same user. There are no permissions issues involved as
qpsmtpd does not have any way to read files off disk (that it didn't
create).
The permissions issues are with the session files that Bricolage creates.
qpsmtpd has to run as the same user as Bricolage ...
That's not strictly true. It has to run as a user which has read (and
maybe write) access to the session and caching directories. If those
directories (and enclosing files) are group readable (and writable if need
be), then qpsmtpd and Bricolage can (and probably should) run as different
users.
so that Michael can use the
Bricolage API in his plugin and it will properly use the session and caching
directories that Bricolage itself creates and uses.
Best,
David
