Postfix still sending hundreds 'queue file write error'

[IgorG]

Did you applied patch for "Unprocessed command" on your Plesk 9.3.0 Debian 4.0 93091230.06?

 

[Flamenetworks]

Did you applied patch for "Unprocessed command" on your Plesk 9.3.0 Debian 4.0 93091230.06?

Yes, no more "Unprocessed command" messages after patch installation.

Regards,

F.

 

[IgorG]

Guys,

This problem Postfix "queue file write error" is really became priority for us and I would like to receive the following information from you:

1. Version of Plesk and OS. Specify, if it is Virtuozzo container.
2. What of the published Postfix patches have been installed.
3. Do you have enabled any spam protections.
4. Conditions for occurrence of this error that you have noticed.
5. Your any additional information which you considers necessary to inform about this problem.

Please answer strictly on these points, shortly and with necessary details.
On the basis of this collected information I will prepare the analytical report for developers.
Thank you for cooperation.

 

[Brujo]

Guys,

This problem Postfix "queue file write error" is really became priority for us and I would like to receive the following information from you:

1. Version of Plesk and OS. Specify, if it is Virtuozzo container.
2. What of the published Postfix patches have been installed.
3. Do you have enabled any spam protections.
4. Conditions for occurrence of this error that you have noticed.
5. Your any additional information which you considers necessary to inform about this problem.

Please answer strictly on these points, shortly and with necessary details.
On the basis of this collected information I will prepare the analytical report for developers.
Thank you for cooperation.

Server 1
Plesk 9.2.3 - CentOS release 5.4 - postfix-2.3.3-2.1.el5_2
Patch: http://forum.parallels.com/showpost.php?p=396040&postcount=44
Activated: SpamAssassin, greylisting, domainkey - deactivated spf
queue write error mostly receiving from external (also with small mails)
sending mail >5MB mostly cause also queuefile write error

Server 2
Plesk 9.3 - CentOS release 5.4 - postfix-2.3.3-2.1.el5_2
Patch: http://forum.parallels.com/showpost.php?p=396040&postcount=44
Activated: SpamAssassin, greylisting, domainkey - deactivated spf
queue write error mostly receiving from external (also with small mails)
sending mail >5MB mostly cause also queuefile write error

Server 3
Plesk 9.3 - CentOS release 5.4 - manual compiled postfix 2.6.5
Patch: http://forum.parallels.com/showpost.php?p=396040&postcount=44
Activated: SpamAssassin, greylisting, domainkey - deactivated spf
queue write error mostly receiving from external (also with small mails)
sending mail >5MB mostly cause also queuefile write error

 

[kanada]

Hi,

about the details:

Plesk 9.2.3, OS: Fedora 11, postfix-2.5.6-3.fc11.i586
Spamassassin on, spf on, antivirus off, domainkeys on

Regards,
Alex

 

[schatje]

Guys,

This problem Postfix "queue file write error" is really became priority for us and I would like to receive the following information from you:

1. Version of Plesk and OS. Specify, if it is Virtuozzo container.
2. What of the published Postfix patches have been installed.
3. Do you have enabled any spam protections.
4. Conditions for occurrence of this error that you have noticed.
5. Your any additional information which you considers necessary to inform about this problem.

Please answer strictly on these points, shortly and with necessary details.
On the basis of this collected information I will prepare the analytical report for developers.
Thank you for cooperation.

1. CentOS release 5.4 (Final) Linux server.myserver.com 2.6.18-164.9.1.el5 #1 SMP Tue Dec 15 20:57:57 EST 2009 x86_64 x86_64 x86_64 GNU/Linux and psa-9.3.0-cos5.build93091230.06
2. http://kb.odin.com/en/6074
3. Yes, i am enable spamassassin and Greylisting
4. With these (3) patch... i got less error then before.., but when i enable GreyListing... after 10 or 20 minutes my smtp error, http://forum.parallels.com/showpost.php?p=404329&postcount=234
5. Here is http://forum.parallels.com/showpost.php?p=404658&postcount=237


Sc

 

[IgorG]

Thank you!

I would like to suggest you one hint.
Try to check current settings for timeouts with following commands:

postconf smtpd_timeout
postconf smtpd_proxy_timeout

Then increase it with

postconf -e smtpd_timeout=3600
postconf -e smtpd_proxy_timeout=3600

After that monitor 'queue file write error' and inform me with received results.
Looking forward for your reply.

 

[schatje]

Thanks IgorG

Before

[root@server vhosts]# postconf smtpd_timeout
smtpd_timeout = 300s
[root@server vhosts]# postconf smtpd_proxy_timeout 
smtpd_proxy_timeout = 100s

After

[root@server vhosts]# postconf smtpd_timeout
smtpd_timeout = 3600
[root@server vhosts]# postconf smtpd_proxy_timeout 
smtpd_proxy_timeout = 3600

Now both is 3600s.. i'll report later if there is still error

Sc

 

[schatje]

After running Greylisting 3 hours i got many proccess of postfix-queue

Here is report from ps aux:

[root@server vhosts]#[B] ps aux |grep postfix-queue[/B]
postfix   1058  0.0  0.0  54192  2252 ?        S    14:21   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        1439  0.0  0.0  11512   744 ?        Ss   14:22   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30        1440  0.0  0.0  11512   724 ?        Ss   14:22   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix   3462  0.0  0.0  55084  2252 ?        S    14:35   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix   3464  0.0  0.0  55084  2256 ?        S    14:35   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        4037  0.0  0.0  11516   748 ?        Ss   14:38   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30        4038  0.0  0.0  11512   724 ?        Ss   14:38   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        4165  0.0  0.0  11516   748 ?        Ss   14:39   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30        4166  0.0  0.0  11512   740 ?        Ss   14:39   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix   4280  0.0  0.0  54192  2256 ?        S    14:39   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix   4282  0.0  0.0  54192  2252 ?        S    14:39   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        4318  0.0  0.0  11516   744 ?        Ss   14:39   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30        4319  0.0  0.0  11516   732 ?        Ss   14:39   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix   4381  0.0  0.0  55084  2256 ?        S    14:40   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix   4383  0.0  0.0  54192  2252 ?        S    14:40   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        7076  0.0  0.0  11516   720 ?        Ss   14:54   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix   7758  0.0  0.0  54192  2252 ?        S    14:57   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix   7937  0.0  0.0  54192  2252 ?        S    14:58   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix   7939  0.0  0.0  55084  2252 ?        S    14:58   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        8955  0.0  0.0  11512   740 ?        Ss   15:01   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30        8956  0.0  0.0  11512   724 ?        Ss   15:01   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix   8998  0.0  0.0  54192  2228 ?        S    15:02   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix   9000  0.0  0.0  54192  2252 ?        S    15:02   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        9181  0.0  0.0  11516   748 ?        Ss   15:03   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30        9182  0.0  0.0  11516   732 ?        Ss   15:03   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30        9494  0.0  0.0  11512   740 ?        Ss   15:04   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30        9495  0.0  0.0  11512   724 ?        Ss   15:04   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
root      9619  0.0  0.0  61184   756 pts/0    S+   15:04   0:00 grep postfix-queue
postfix  16384  0.0  0.0  54192  2252 ?        S    13:21   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix  20792  0.0  0.0  54192  2252 ?        S    13:33   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix  20982  0.0  0.0  54192  2256 ?        S    13:33   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix  21000  0.0  0.0  54192  2256 ?        S    13:33   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix  25403  0.0  0.0  54192  2256 ?        S    13:50   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix  25405  0.0  0.0  54192  2252 ?        S    13:50   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix  27696  0.0  0.0  54192  2252 ?        S    13:59   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30       31565  0.0  0.0  11512   740 ?        Ss   14:13   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30       31566  0.0  0.0  11516   748 ?        Ss   14:13   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30       31918  0.0  0.0  11512   744 ?        Ss   14:15   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30       31919  0.0  0.0  11516   748 ?        Ss   14:15   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix  32154  0.0  0.0  54192  2252 ?        S    14:16   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix  32155  0.0  0.0  54192  2256 ?        S    14:16   0:00 spawn -n 127.0.0.1:10025 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
postfix  32157  0.0  0.0  54192  2256 ?        S    14:16   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
postfix  32160  0.0  0.0  54192  2252 ?        S    14:16   0:00 spawn -n 127.0.0.1:10027 -t inet user=mhandlers-user argv=/usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote
30       32323  0.0  0.0  11516   748 ?        Ss   14:16   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10027 before-queue
30       32324  0.0  0.0  11516   744 ?        Ss   14:16   0:00 /usr/lib64/plesk-9.0/postfix-queue 127.0.0.1 10026 before-remote

Is that normal ?

Sc

 

[IgorG]

Sorry guys,
Before mentioned commands, please apply this patch.

Upd. Patch will be updated soon.

 

[schatje]

Sorry guys,
Before mentioned commands, please apply this patch.

cd /usr/local/src
wget http://download1.sw-soft.com/Plesk/Autoupdate/update3.tar.gz
tar -xzvf update3.tar.gz
/etc/init.d/postfix stop;rm -f /usr/lib64/plesk-9.0/postfix-queue; cp update/dist-rpm-CentOS-5-x86_64/postfix-queue /usr/lib64/plesk-9.0/postfix-queue; chown mhandlers-useropuser /usr/lib64/plesk-9.0/postfix-queue; killall postfix-queue; /etc/init.d/postfix start

Bang!!!!...

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

After that i try run
/usr/local/psa/bin/grey_listing --update-server -status off
but still... can not sent email... now back to old postfix-queue

Sc

 

[IgorG]

Did you increased timeouts after patch applying?

 

[schatje]

Did you increased timeouts after patch applying?

This config already added to main.cf when i run
postconf -e smtpd_timeout=3600
postconf -e smtpd_proxy_timeout=3600

[root@server src]# tail /etc/postfix/main.cf
virtual_mailbox_base = /var/qmail/mailnames
virtual_uid_maps = static:110
virtual_gid_maps = static:31
virtual_transport = plesk_virtual
plesk_virtual_destination_recipient_limit = 1
smtpd_client_restrictions = reject_rbl_client sbl.spamhaus.org
message_size_limit = 10240000

smtpd_timeout = 3600
smtpd_proxy_timeout = 3600
[root@server src]# postconf smtpd_proxy_timeout 
[B]smtpd_proxy_timeout = 3600[/B]
[root@server src]# postconf smtpd_timeout 
[B]smtpd_timeout = 3600[/B]

Sc

 

[IgorG]

Ok. Let's wait other results and responses.

 

[Adrian Garcia]

Several servers, same versions on all of them and same behaviour.

Plesk 9.3 - CentOS 5.3 - postfix-2.3.3-2.1.el5_2

Enabled: spamd, dnsbl
Disabled: domainkey, spf, greylisting

smtpd_timeout = 300s
smtpd_proxy_timeout = 600s

Mail gets to the mailbox but remote server always retries, since it receives a 451, and the same message is delivered multiple times to the mailbox. It happens to messages as small as 1.5KB and as big as 10MB (my servers' message limit is 15MB).

 

[ClaudiaN]

Another system with the same problem

1. Version of Plesk and OS. Specify, if it is Virtuozzo container.
-> Plesk 9.3.0. x86_64 GNU/Linux OpenSUSE 11.1

2. What of the published Postfix patches have been installed.
-> "Unprocessed command" patch.

3. Do you have enabled any spam protections.
-> spamassassin. greylisting already switched off.

4. Conditions for occurrence of this error that you have noticed.
-> Mails with big attachments. Depending on how fast the internet access is, "big" might be 20 MB or just 5 MB.

5. Your any additional information which you considers necessary to inform about this problem.
-> Settings in main.cf:
smtpd_proxy_timeout=720s
smtp_data_xfer_timeout=600s
Also increased the message_size_limit to approx 50 MB.

 

[IgorG]

Here is updated patch. Please try it. And do not forget timeout settings.

 

[ClaudiaN]

I've installed the patch but am still receiving error messages.
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

 

[MichielK]

1. Version of Plesk and OS. Specify, if it is Virtuozzo container.
Debian 4.0 "etch" kernel 2.6.24-i686-etchnhalf, all packages up-to-date
Plesk 9.3.0 standalone (non-virtuozzo)

2. What of the published Postfix patches have been installed.
http://forum.parallels.com/showpost.php?p=396040&postcount=44
-r-xr-x--- 1 mhandlers-user root 81736 2010-01-29 10:39 /usr/lib/plesk-9.0/postfix-queue

3. Do you have enabled any spam protections.
enabled RBL protection and SpamAssassin

4. Conditions for occurrence of this error that you have noticed.
about 2% of total mail traffic

5. Your any additional information which you considers necessary to inform about this problem.

I even received the errors with a small 36kb sized message:
Out: 220 klaver.it ESMTP
In: EHLO s0.nanog.org
Out: 250-klaver.it
Out: 250-PIPELINING
Out: 250-SIZE 25600000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN PLAIN DIGEST-MD5 CRAM-MD5
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: STARTTLS
Out: 220 2.0.0 Ready to start TLS
In: EHLO s0.nanog.org
Out: 250-klaver.it
Out: 250-PIPELINING
Out: 250-SIZE 25600000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-AUTH LOGIN PLAIN DIGEST-MD5 CRAM-MD5
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:<[email protected]> SIZE=37641
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

 

[Juan Rey]

In last update patch, dist-rpm-SuSE-11.0-x86_64 dir is empty !!!