Gregory Machin a écrit : > Hi > I'm green to Postfix. I have 2 anti-spam servers that I upgraded > MailScanner to the latest version and a completely new install of > MailScanner and postfix etc. All three have the same problems . the > one thing that is common to all servers is the original configs. For > the google-ing and digging around I'm still non the wiser. I have > looked file permissions etc, reinstalled MailScanner etc .. I'm out of > ideas, If someone with more experience could please advise me. > > These are the errors I'm getting on all 3 servers : > > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: premature > end-of-input on private/smtp socket while reading input attribute name > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: private/smtp > socket: malformed response > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: transport smtp > failure -- see a previous warning/fatal/panic logfile record for the > problem description > Mar 20 23:08:13 spam10 postfix/master[2135]: warning: process > /usr/libexec/postfix/smtp pid 7304 exit status 1 > Mar 20 23:08:13 spam10 postfix/master[2135]: warning: process > /usr/libexec/postfix/smtp pid 7606 exit status 1 > Mar 20 23:08:13 spam10 postfix/master[2135]: warning: > /usr/libexec/postfix/smtp: bad command startup -- throttling > Mar 20 23:08:13 spam10 postfix/master[2135]: warning: process > /usr/libexec/postfix/smtp pid 7607 exit status 1 > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: premature > end-of-input on private/smtp socket while reading input attribute name > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: private/smtp > socket: malformed response > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: transport smtp > failure -- see a previous warning/fatal/panic logfile record for the > problem description > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: premature > end-of-input on private/smtp socket while reading input attribute name > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: private/smtp > socket: malformed response > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: transport smtp > failure -- see a previous warning/fatal/panic logfile record for the > problem description > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: premature > end-of-input on private/smtp socket while reading input attribute name > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: private/smtp > socket: malformed response > Mar 20 23:08:13 spam10 postfix/master[2135]: warning: process > /usr/libexec/postfix/smtp pid 7608 exit status 1 > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: transport smtp > failure -- see a previous warning/fatal/panic logfile record for the > problem description > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: premature > end-of-input on private/smtp socket while reading input attribute name > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: private/smtp > socket: malformed response > Mar 20 23:08:13 spam10 postfix/qmgr[2142]: warning: transport smtp > failure -- see a previous warning/fatal/panic logfile record for the > problem description > Mar 20 23:08:13 spam10 postfix/master[2135]: warning: process > /usr/libexec/postfix/smtp pid 7609 exit status 1 > > > mailq has these errors that I believe are related : > > 0920312D5 264064 Fri Mar 20 17:35:11 tku...@eeeeeeeeeee.com > (delivery temporarily suspended: unknown mail transport error) > jpdt...@nnnnn.co.za > > 0902812D4 13035 Fri Mar 20 14:34:33 brint...@uuuuuuu.co.za > (delivery temporarily suspended: unknown mail transport error) > rite...@nnnnnn.co.za > > 0636F12D3 594450 Fri Mar 20 01:19:13 revi...@ttttttttttttttttttttttt.co.za > (delivery temporarily suspended: unknown mail transport error) > ta...@xxxxxxxxxxxr.co.za > > 039B612D1 11579 Wed Mar 18 14:53:43 emboun...@eeeeeeeee.co.za > (delivery temporarily suspended: unknown mail transport error) > rus...@xxxxxxxxxxx.co.za > [snip]
just for your info, mailscanner isn't supported here. that said, it looks like you have a transport error. Unfortunately, you didn't show the corresponding logs. check other log lines for errors. you may have mail that should be routed via a transport that you removed (intentionally or not).
