On Tue, Mar 26, 2013 at 3:21 PM, Wietse Venema <wie...@porcupine.org> wrote: > Lima Union: >> working. This MTA is behing a firewall, in a DMZ with a bidirectional >> mapping (1:1). I issued a grep ': connect from' and everything shown >> is 'connect from unknown[ip.add.re.ss]'. I'm using pdnsd for caching >> purposes. My resolv.conf points to 127.0.0.1 and seems to be working >> fine: >> >> $ dig +short -x 209.85.212.54 >> mail-vb0-f54.google.com. > > Turn off CHROOT for the SMTP daemon. > > http://www.postfix.org/DEBUG_README.html#no_chroot > > A common mistake is to turn on chroot operation in the master.cf > file without going through all the necessary steps to set up a > chroot environment. This causes Postfix daemon processes to fail > due to all kinds of missing files. > > The example below shows an SMTP server that is configured with > chroot turned off: > > /etc/postfix/master.cf: > # ============================================================= > # service type private unpriv chroot wakeup maxproc command > # (yes) (yes) (yes) (never) (100) > # ============================================================= > smtp inet n - n - - smtpd > > Inspect master.cf for any processes that have chroot operation not > turned off. If you find any, save a copy of the master.cf file, and > edit the entries in question. After executing the command "postfix > reload", see if the problem has gone away. > > Wietse
Wietse, ok, I'll disable the fqrdns check for now and check the chroot configuration after I return from holidays. Thanks all !
