Le 12/12/2010 21:51, Philip A Colvin a écrit :
r...@ubuntu:~# ls -l /var/spool/MIMEDefang
total 8
-rw-r----- 1 defang defang 5 2010-12-12 12:30 mimedefang-multiplexor.pid
srw------- 1 defang defang 0 2010-12-12 12:30
mimedefang-multiplexor.sock
-rw-r----- 1 defang defang 5 2010-12-12 12:30 mimedefang.pid
srwxr-x--- 1 defang defang 0 2010-12-12 12:30 mimedefang.sock
so anyone outside of the 'defang' group has no access to the .sock
file. (you forgot 'file mimedefang.sock' to show file type. but let's
assume it's a real socket).
Sorry about forgetting the file mimedefang.sock. It is showing as a
socket..
/var/spool/MIMEDefang/mimedefang.sock: socket
Would putting the postfix user in the defang group get around the
permissions problem? The error does not show a permissions problem, just
that it cannot find the file. I'm guessing that has something to do with
the chroot.
maybe you have a chroot issue?
# grep smtpd master.cf
I don't think there is a chroot issue... see below
I think there is... see below;-p
r...@ubuntu:/# grep smtpd /etc/postfix/master.cf
smtp inet n - - - - smtpd
if you check master.cf, you should see:
#==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
#
==========================================================================
the 5th field is chroot and defaults to 'yes'. In your config, it is
'-', so it defaults to chrooted.
Sorry for asking these simple questions, but what are my choices for
dealing with the chroot issue?
all your lines should have 'n' as the 5th field. for example
smtp inet n - - n - - smtpd
see
http://www.postfix.org/DEBUG_README.html#no_chroot
http://www.postfix.org/BASIC_CONFIGURATION_README.html#chroot_setup
Thanks again for all the help.
Phil
