• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

451 Error: queue file write error (only when using postfix)

Maybe it is already clear, but nevertheless: I get this error only after attaching a big file to a message (e.g. 2MB), so this message will not be sent. Normal ('small') mails work fine with postfix on my machine with CentOS 5. But of course we seriously need to send that kind of files, so please give this problem a high priority in development... thank you.
 
I would say the issue is still not fixed and also exist without big attachments. I have two Servers one with Plesk 9.2.3 and the other with 9.3 and on both I have the queuefile write errors. However I belive this is not just one issue there are a lot of issues around the postfix-queue...

Once we recieved just the half of Mails again and again and for each mail the queuefile write error. The Plesk implementation of Posfix is just useless on a production server

Brujo




Brujo
 
Postfix problem remains on plesk 9.3.0

Hi there i can confirm the Postfix 'queue file write error' problem still exists for me after upgrading to Plesk 9.3.0 running Debian Etch.

Unfortunately I am unable to switch back to Qmail because we need some of the features offered in postfix for virtual hosts.

Has anyone tried working around this problem by using a backup MX server running Qmail ? (the backup MX delivery to the primary MX could be tweaked to work around this problem)
 
Hi,

I think actually the best approach is to loose the greylisting feature and bypass the postfix proxy as described serveral messages above.

Greetings
 
Well, I have been monitoring this thread since installing 9.2.3 and "upgrading" to 9.3. I am yet another sysadmin with this issue, but I'll save you all the trauma of reading another log excerpt and error email.

What is quite outrageous is that, quite simply, this product is not fit for the purpose for which it is marketed and sold, and it is about time Parallels realised this. There are only two possible reasons why this issue exists:
1) Parallels are unable to fix it
2) Parallels are unwilling to fix it

Given that the general consensus is that Postfix is a reliable mailserver with thousands of reliable installations across the world, I simply have to conclude that it is quite possible to implement a correctly-working server if Parallels choose to. It seems that they do not.

I am loath to switching to QMail because, upon trying it before, I received innumerable blank messages (20,000-odd) in my inbox from what would appear to be a rogue process at work. Rebooting the server did not help resolve that, and therefore I am forced to stay with Postfix. If Parallels cannot fix this issue, what hope do I have that they can successfully script a MTA switcher without issues?!! So, no thanks to that ...!

It is my hunch that this issue occurs only on 64-bit implementations and not 32-bit ones, as I recently migrated all my domains from a fully functional, non-erroring 32-bit Plesk v9.2.3. The only other difference is that we've gone from RHEL 4 to RHEL 5.
 
I have updated posted already Workaround with new version of patch for fixing 'Unprocessed command' error.
Please try it and update this thread with results.

Problem still exists (Debian Etch, Plesk 9.3.0, Postfix 2.3.8-2):

Out: 220 www3........net ESMTP Postfix (Debian/GNU)
In: EHLO [10.157.209.211]
Out: 250-www3........net
Out: 250-PIPELINING
Out: 250-SIZE 30720000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN CRAM-MD5 DIGEST-MD5 PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: STARTTLS
Out: 220 2.0.0 Ready to start TLS
In: EHLO [10.157.209.211]
Out: 250-www3.........net
Out: 250-PIPELINING
Out: 250-SIZE 30720000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-AUTH LOGIN CRAM-MD5 DIGEST-MD5 PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: AUTH PLAIN AGluZm9AY29ja3RhaWxzdGFyLmRlAHJtNkh0cDQ5
Out: 235 2.0.0 Authentication successful
In: MAIL FROM:<[email protected]>
Out: 250 2.1.0 Ok
In: RCPT TO:<[email protected]>
Out: 250 2.1.5 Ok
In: DATA
Out: 354 End data with <CR><LF>.<CR><LF>
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye


Feb 12 18:39:58 www3 before-remote[24135]: errno: Broken pipe
Feb 12 18:39:58 www3 before-remote[24135]: System error: Broken pipe
Feb 12 18:39:58 www3 before-remote[24135]: Unable to write data to stream
Feb 12 18:39:58 www3 before-remote[24135]: Some error occured
Feb 12 18:39:58 www3 before-queue[24133]: errno: Connection reset by peer
Feb 12 18:39:58 www3 before-queue[24133]: System error: Connection reset by peer
Feb 12 18:39:58 www3 before-queue[24133]: Unable to write data to stream
Feb 12 18:39:58 www3 before-queue[24133]: Some error occured

Feb 12 18:39:58 www3 before-remote[24135]: errno: Broken pipe
Feb 12 18:39:58 www3 before-remote[24135]: System error: Broken pipe
Feb 12 18:39:58 www3 before-remote[24135]: Unable to write data to stream
Feb 12 18:39:58 www3 before-remote[24135]: Some error occured
Feb 12 18:39:58 www3 postfix/spawn[24134]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Feb 12 18:39:58 www3 before-queue[24133]: errno: Connection reset by peer
Feb 12 18:39:58 www3 before-queue[24133]: System error: Connection reset by peer
Feb 12 18:39:58 www3 before-queue[24133]: Unable to write data to stream
Feb 12 18:39:58 www3 before-queue[24133]: Some error occured
Feb 12 18:39:58 www3 postfix/spawn[24132]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255

It's an absolute annoying situation!
Please bring up a WORKING SOLUTION - not a Workaround over a Workaround!

Thank You.
 
No more errors for me, but a lot of processes of postfix-queue (about 1000 in just 24 hours) not finishing :(
Reverted to saved postfix-queue :(
 
I got same problem on my server Centos 5.4 (Final) and Pleak 9.3
Fix with this patch http://kb.odin.com/en/6074
But after fix.. my greylisting make trouble.. now for temporary i disable GL

Hope this help you

Sc
 
I got same problem on my server Centos 5.4 (Final) and Pleak 9.3
Fix with this patch http://kb.odin.com/en/6074
But after fix.. my greylisting make trouble.. now for temporary i disable GL

Hope this help you

Sc

This Patch is for Plesk 9.0 and should be included in Plesk 9.3.
"The recompiled utility with timeout value 300 seconds is included to Parallels Plesk Panel since version 9.2."...

Best regards
 
I'm using Plesk 9.3, but also have got the same problem.
I've tried installing the patch from http://kb.odin.com/en/6074,
it helps only for a small size attachment.

If email contains large attachment (not so large actually, about 2-3MB), I still get the same error in Mailog:
Feb 18 17:33:25 ls1 before-remote[5224]: check handlers for addr: [email protected]
Feb 18 17:33:25 ls1 before-remote[5224]: Processing handlers...
Feb 18 17:33:25 ls1 before-queue[5223]: check handlers for addr: [email protected]
Feb 18 17:33:25 ls1 before-queue[5223]: Processing handlers...
Feb 18 10:33:27 ls1 postfix/smtpd[21288]: timeout after DATA from unknown[127.0.0.1]
Feb 18 10:33:27 ls1 postfix/smtpd[21288]: disconnect from unknown[127.0.0.1]
Feb 18 17:33:27 ls1 before-remote[1782]: Timeout reading data from stream
Feb 18 17:33:27 ls1 before-remote[1782]: Unable to read data from stream
Feb 18 17:33:27 ls1 before-remote[1782]: Some error occured
Feb 18 17:33:27 ls1 postfix/spawn[13413]: warning: command /usr/lib64/plesk-9.0/postfix-queue exit status 255
Feb 18 17:33:30 ls1 postfix/spawn[28841]: warning: /usr/lib64/plesk-9.0/postfix-queue: process id 26938: command time limit exceeded

Anyone.. please suggest, how to make Postfix 100% working with attachment?
My domains also need to receive a large attachment, not only a small one..
 
Postfix on Plesk make me Crazy!!!!!
Mine just work for 2 days... after that... problem again... now i must DISABLE greylisting... all problem GONE.. but got new PROBLEM!!... to many SPAM come in to my server...

I dont know.. this is problem on GL or postfix ? buat IGor said it's postfix problem....
So... to the parallels team... please FIX it !!!

Sc
 
Last edited by a moderator:
cPanel???

Just switch to Qmail if you have problems with Postfix....
 
cPanel???

Just switch to Qmail if you have problems with Postfix....

Opss... sorry... i mean Plesk :)

When i switch to qmail my server can not receive any mails with this tutorial
http://kb.odin.com/en/5801

I was try it... here is the log:

Code:
1. Take more than 25 minutes to switch to qmail on....
[B]Trying to executing mail_restore to synchronize mail server settings and Plesk Database...[/B]

When this process all client can not sent and received email... when try receive always keep asking password

When send email.. i got log on my office smtp server like this:
Feb 10 19:18:27 proxy postfix/smtp[6462]: A270A64903: to=<[email protected]>, relay=mail.myserver.net[65.60.xx.yy]:25, delay=1.9, delays=0.07/0.01/1.5/0.32, dsn=5.0.0, status=bounced (host mail.myserver.net[65.60.xx.yy] said: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) (in reply to RCPT TO command))

2. After process finish (now use qmail) i can not sent email to [email protected]
On my office smtp-server maillog:
Feb 10 19:27:06 proxy postfix/smtp[6513]: A19B064903: to=<[email protected]>, relay=mail.myserver.net[65.60.xx.yy]:25, delay=2, delays=0.05/0.01/1.1/0.81, dsn=4.0.0, status=deferred (host mail.myserver.net[65.60.xx.yy] [B]said: 451 qq trouble in home directory[/B] (#4.3.0) (in reply to end of DATA command))

And this email bounce to postmaster of this server:

[root@server plesk-9.0]# cat /var/qmail/mailnames/myserver.com/postmaster/Maildir/new/1265801188.M8886P21824V0000000000000805I0000000001A46F36.server.myserver.com,S=1730
DomainKey-Status: no signature
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
server.myserver.com
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=7.0 tests=AWL,MISSING_MID,NO_RELAYS
autolearn=ham version=3.2.5
Received: (qmail 21636 invoked by alias); 10 Feb 2010 19:24:04 +0800
Delivered-To: [email protected]
Received: (qmail 25010 invoked for bounce); 10 Feb 2010 19:22:02 +0800
Date: 10 Feb 2010 19:22:02 +0800
From: [email protected]
To: [email protected]
Subject: failure notice

Hi. This is the qmail-send program at server.myserver.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[email protected]>:

--- Below this line is a copy of the message.

Return-Path: <[email protected]>
Received: (qmail 2679 invoked for bounce); 10 Feb 2010 19:20:23 +0800
Date: 10 Feb 2010 19:20:23 +0800
From: [email protected]
To: [email protected]
Subject: failure notice

Hi. This is the qmail-send program at server.myserver.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[email protected]>:
Sorry. Although I'm listed as a best-preference MX or A for that host,
it isn't in my control/locals file, so I don't treat it as local. (#5.4.6)

--- Below this line is a copy of the message.

Return-Path: <[email protected]>
Received: (qmail 26090 invoked by alias); 10 Feb 2010 19:19:43 +0800
Delivered-To: [email protected]

Sc
 
Strange !!!... just try activated GL and everythings is OK... no more write queue error or error like this on client side
Code:
An unknown error has occurred. Subject 'invoice for nusaduabalixyz.com', Account: 'mail.myserver.com', Server: 'mail.mailserver.com', Protocol: SMTP, Server Response: '451 mail server temporary failed', Port: 25, Secure(SSL): No, Server Error: 451, Error Number: 0x800CCC6A

Sc
 
I have updated posted already Workaround with new version of patch for fixing 'Unprocessed command' error.
Please try it and update this thread with results.

Thanks. This totally resolved the problem for us. Updates 3 of our Plesk Servers with Postfix using this patch and it works great now. Please include this to further upgrades.
 
No luck on my server

Code:
[root@server src]# md5sum /usr/lib64/plesk-9.0/postfix-queue*
2aec66472202f4a0f291a593902a2197  /usr/lib64/plesk-9.0/postfix-queue
333d4816857ef1cfed35210e8b9838b2  /usr/lib64/plesk-9.0/postfix-queue.bak
faa8849685972d9ca4813d753fe048a6  /usr/lib64/plesk-9.0/postfix-queue.good

[root@server src]# ls -al /usr/lib64/plesk-9.0/postfix-queue*
-r-xr-x--- 1 mhandlers-user popuser 178841 Feb 24 12:36 /usr/lib64/plesk-9.0/postfix-queue
-r-xr-x--- 1 mhandlers-user popuser  79384 Dec 30 08:11 /usr/lib64/plesk-9.0/postfix-queue.bak
-r-xr-x--- 1 mhandlers-user popuser  95947 Feb 18 15:49 /usr/lib64/plesk-9.0/postfix-queue.good

If i use postfix-queue.good there is no more Out: 451 4.3.0 Error: queue file write error
But still can not activate/enable greylistings, actually it is work just for couple hours after that i got
An unknown error has occurred. Subject 'invoice for nusaduabalixyz.com', Account: 'mail.myserver.com', Server: 'mail.mailserver.com', Protocol: SMTP, Server Response: '451 mail server temporary failed', Port: 25, Secure(SSL): No, Server Error: 451, Error Number: 0x800CCC6A

If i use postfix-queue some times still got Out: 451 4.3.0 Error: queue file write error (tested 4 hours got 11 error)
And does not have problem on GreyListings.. just working perfectly...

Use parallels Plesk 9.3.0 on Centos 5.4 64bit

Sc
 
I have Plesk v9.3.0, CentOS v5 32bits and still get the error.

Transcript of session follows.

Out: 220 nsxxxxxxx.ovh.net ESMTP Postfix
In: EHLO llsd410-a04.servidoresdns.net
Out: 250-nsxxxxxxx.ovh.net
Out: 250-PIPELINING
Out: 250-SIZE 10240000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH PLAIN DIGEST-MD5 CRAM-MD5 LOGIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:<[email protected]> SIZE=182555
Out: 250 2.1.0 Ok
In: RCPT TO:<[email protected]>
Out: 250 2.1.5 Ok
In: DATA
Out: 354 End data with <CR><LF>.<CR><LF>
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye

And

Transcript of session follows.

Out: 220 nsxxxxxxx.ovh.net ESMTP Postfix
In: EHLO OPTIP
Out: 250-ns203371.ovh.net
Out: 250-PIPELINING
Out: 250-SIZE 10240000
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH PLAIN DIGEST-MD5 CRAM-MD5 LOGIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: AUTH LOGIN
Out: 334 xxxxxxxx
In: xxxxxxxxxxxxxxxxxxx==
Out: 334 xxxxxxxxxx
In: xxxxxxxxxxx
Out: 235 2.0.0 Authentication successful
In: MAIL FROM: <[email protected]>
Out: 250 2.1.0 Ok
In: RCPT TO: <[email protected]>
Out: 250 2.1.5 Ok
In: DATA
Out: 354 End data with <CR><LF>.<CR><LF>
Out: 451 4.3.0 Error: queue file write error

Session aborted, reason: lost connection
 
Last edited by a moderator:
productive usage of Plesk with Postfix not possible :(

Prolem still present(Debian 4 / Ples 9.3.0 with latest Updates / Potfix):

Patch from http://forum.parallels.com/showpost.php?p=396040&postcount=43 is installed!

/var/log/mail.info
Mar 18 12:13:07 mserver1 before-remote[29091]: errno: Broken pipe
Mar 18 12:13:07 mserver1 before-remote[29091]: System error: Broken pipe
Mar 18 12:13:07 mserver1 before-remote[29091]: Unable to write data to stream
Mar 18 12:13:07 mserver1 before-remote[29091]: Some error occured
Mar 18 12:13:07 mserver1 postfix/spawn[27768]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Mar 18 12:13:07 mserver1 before-queue[29090]: Unable to write data to stream
Mar 18 12:13:07 mserver1 before-queue[29090]: Some error occured
Mar 18 12:13:07 mserver1 postfix/spawn[27800]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
Mar 18 12:13:07 mserver1 postfix/smtpd[27173]: warning: lost connection with proxy 127.0.0.1:10025

Please fix it imediately... thanks
 
Last edited by a moderator:
Back
Top