On 3.4.2007, at 16.20, Uldis Pakuls wrote:
Timo Sirainen wrote:
The other possibility is to disable chrooting with deliver.
Is it possible to disable chrooting for deliver only? What about
maildir/box paths then?
What userdb do you use? There's no simple disable chrooting
setting, but if
Timo Sirainen wrote:
The other possibility is to disable chrooting with deliver.
Is it possible to disable chrooting for deliver only? What about
maildir/box paths then?
Uldis
Timo Sirainen wrote:
**sieve plugin tries to forward mail... and fails when chroot enabled.
Put the sendmail binary inside chroot and change sendmail_path setting.
Although I don't know if even that will work. It might want to write
directly to the mail spool instead of connecting to the
Timo Sirainen wrote:
You don't start deliver as root (or setuid root), so it can't do the
chrooting.
Usually MTAs don't allow starting deliver as root, so your only
possibilities are setuid root (see the wiki page) or not using chrooting
with deliver.
setuid works, but another problem arise:
