Atomicorp

Hi,
On a CentOS 5.2 server with Plesk 9.0.1, I sometime got this error: Postfix return "451 4.3.0 Error: queue file write error"...
This is really strange as the limit of size of the mailbox concerned is unlimited, and the total server-wide maximum mail size is bigger thant the concerned message.

Here's the transcript of session:

Out: 220 myhost.com ESMTP Postfix
In: EHLO mx.senderhost.com
Out: 250-myhost.com
Out: 250-PIPELINING
Out: 250-SIZE 20480000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH CRAM-MD5 PLAIN DIGEST-MD5 LOGIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:<sender@senderhost.com> SIZE=121701
Out: 250 2.1.0 Ok
In: RCPT TO:<mymailbox@myhost.com> ORCPT=rfc822;mymailbox@myhost.com
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


Does anybody got the same problem?
Thanks for your advice!

Hmm... out of space on the file system? Or is selinux running?

Hello Scott, thanks for your reply!

Nope, around 200go free on the host, no SELINUX, no quota... I don't get it.
And I noticed that it always happens from the same hosts (they connect around 3 times/day to the SMTP and produce this error).

Are you by any chance using kaspersky or drweb?

Nope, I removed them and I'm using ClamAV (and also postgrey).

I was thinking that could be a timeout error to an external filter.

I've those lines in maillog:

Feb 25 06:51:47 myhost postfix/smtpd[2118]: lost connection after DATA from unknown[127.0.0.1]
Feb 25 06:51:47 myhost postfix/smtpd[2118]: disconnect from unknown[127.0.0.1]

and also:

Feb 25 07:51:47 myhost postfix/spawn[2116]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255

But I don't understand the problem better...

A ha! I think I know whats going on then, check out this kb article:

http://kb.parallels.com/en/6074

It has some fixes you need to apply to the box. This might be whats going on if this was happening to messages with attachments.

Hey, thanks for the KB!!!
I put the new postfix-queue (from the hotfix) on my host... but I still have those errors (with same hosts as before):
postfix/spawn[8663]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255

Booohohooooo....

well shucks... what happens when you back out your clamav and postgrey modules? Does it go away?

I will try to deactivate ClamAV and Postgrey... But I don't think it's the problem....

Note I had a different case than the other one:
Out: 220 myhost ESMTP Postfix
In: HELO mx.source.com
Out: 250 myhost
In: MAIL FROM:<user@myhost.com>
Out: 250 2.1.0 Ok
In: RCPT TO:<user@myhost.com>
Out: 250 2.1.5 Ok
In: RCPT TO:<user@myhost.com>
Out: 250 2.1.5 Ok
In: NOOP
Out: 250 2.0.0 Ok
In: NOOP
Out: 250 2.0.0 Ok
In: DATA
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye

Okay, now that I've the patch, the last errors seen linked to the queue file error all look like this in the maillog:
Mar 5 06:06:25 myhost postfix/spawn[926]: warning: command /usr/lib/plesk-9.0/postfix-queue killed by signal 11
Mar 5 05:06:25 myhost postfix/smtpd[891]: warning: lost connection with proxy 127.0.0.1:10025
Mar 5 06:06:25 myhost before-remote[929]: Lost connection
Mar 5 06:06:25 myhost before-remote[929]: Some error occured
Mar 5 05:06:25 myhost postfix/smtpd[930]: lost connection after DATA from unknown[127.0.0.1]
Mar 5 05:06:25 myhost postfix/smtpd[930]: disconnect from unknown[127.0.0.1]

I tried to add a proxy timeout as indicated here:
http://forums.meulie.net/viewtopic.php?f=44&t=307

But it didn't help... I'm still looking for a solution...

Same problem here and on a Plesk 9.2 where according the kb the new postfix is integrated... So any solution is welcome, because everydag postfix fails and no mail will come to the mailboxes!

I cannot believe this. 9.x has been out for a LONG time now and it still has bugs like this? Obviously they don't affect everybody/don't manifest in all OSes/whatever, but it is still very worrying.

We are still provisioning 8.6 for all our customers and I don't think that's going to change in the immediate future.

Faris.

Yeah hopefully another update against postfix will clean things up. I still use qmail here, but I'm planning on going to postfix eventually.