Hi Wietse Venema: I get output in the logs but nothing (no error) why it is held (still) in the queue. BTW Could one somehow bad email holt up the entire queue?!
Jul 17 21:16:00 gFort postfix/smtpd[32024]: master_notify: status 1 Jul 17 21:16:00 gFort postfix/smtpd[32024]: connection closed Jul 17 21:16:00 gFort postfix/smtpd[32024]: watchdog_stop: 0x7fbd30c9da10 Jul 17 21:16:00 gFort postfix/smtpd[32024]: watchdog_start: 0x7fbd30c9da10 Jul 17 21:16:03 gFort postfix/smtpd[32024]: auto_clnt_close: disconnect private/tlsmgr stream Jul 17 21:16:03 gFort postfix/smtpd[32024]: rewrite stream disconnect Jul 17 21:16:03 gFort postfix/smtpd[32024]: watchdog_stop: 0x7fbd30c9da10 Jul 17 21:16:03 gFort postfix/smtpd[32024]: watchdog_start: 0x7fbd30c9da10 so should there be coming forth anything after postfix/smtpd?! The qmnr again?! *via www.LinuxMint.com 16:Petra* Am 17.07.2014 21:01, schrieb Wietse Venema: > XYZFounder: >>> postfix 30554 0.0 0.0 44248 2548 ? S 20:00 0:00 smtp >>> -t unix -u -c -vv > Configured in this way. the SMTP client runs in a chroot jail. Turn > that off in master.cf. > > # ========================================================================== > # service type private unpriv chroot wakeup maxproc command + args > # (yes) (yes) (yes) (never) (50) > # ========================================================================== > ... > smtp unix - - n - - smtp > > The chroot column must be "n" for all programs. > > Then "postfix reload", and you should have some logging. > > Wietse
