David Cottle: [ Charset ISO-8859-1 unsupported, converting... ] > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > All, > > I see this a lot in my mail.log (unknown): > > Feb 10 20:38:28 server postfix/smtpd[21977]: connect from > unknown[72.4.168.106] > Feb 10 09:38:30 server postfix/smtpd[21977]: NOQUEUE: reject: RCPT > from unknown[72.4.168.106]: 554 5.7.1 Service unavailable; Client host
Try: http://www.postfix.org/DEBUG_README.html#no_chroot. If it works, send a complaint to your vendor. I, the Postfix author, do not recommend that chroot is turned on except by experts. Wietse Try turning off chroot operation in master.cf ============================================= 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. If turning off chrooted operation made the problem go away, then congratulations. Leaving Postfix running in this way is adequate for most sites. If you prefer chrooted operation, see the Postfix BASIC_CONFIGURATION_README file for information about how to prepare Postfix for chrooted operation.
