Wietse Venema wrote (on Wed, Jan 07, 2009 at 09:03:42PM -0500): > I'd say, run "postfix set-permissions" and if that does not > do the job, kill off or update SELINUX, APPARMOR, etc. > > Wietse
# postfix/postfix-script: fatal: usage: postfix start (or stop, reload, abort, flush, or check) a little digging convinced me that you meant: # /etc/postfix/post-install set-permissions but that gave a string of (I think) meaningless errors - fix one, another pops up, etc. (Now I'm up to "chown: cannot access `/usr/share/man/man1/mailq.postfix.1.bz2': No such file or directory") SELINUX is not installed, and APPARMOR is in complain mode. Anyway, I've had a total of eight errors over two days, all with the same host/sender/recipient, apparently three different messages (the double bounce message doesn't have the original message body, but it does have the SMTP transaction, and therefore the message size.) So, I'm going back to my original supposition that something in the message(s) is causing the error, especially as the error happens in the data phase: In: DATA Out: 354 End data with <CR><LF>.<CR><LF> Out: 451 4.3.0 Error: queue file write error puzzling. -- _________________________________________ Nachman Yaakov Ziskind, FSPA, LLM aw...@ziskind.us Attorney and Counselor-at-Law http://ziskind.us Economic Group Pension Services http://egps.com Actuaries and Employee Benefit Consultants
