Postfix Mail Queue error

[nobody]

Hello.

I am using Postfix with Plesk 9.0.1

Everything was working perfectly until I tried to send attachments larger than 1mb getting this error.


Transcript of session follows.

Out: 220 server.domain.com ESMTP Postfix
In: EHLO PHOVOS
Out: 250-server.something.com
Out: 250-PIPELINING
Out: 250-SIZE 10240000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH CRAM-MD5 LOGIN DIGEST-MD5 PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: AUTH LOGIN
Out: 334 VXNlcm5hbWU6
In: YWxleC5zdGFtYXRpc0BkYXJwaXguY29t
Out: 334 UGFzc3dvcmQ6
In: YXJ4aWRpYW1hbnRvbGVz
Out: 235 2.0.0 Authentication successful
In: MAIL FROM: <my@email>
Out: 250 2.1.0 Ok
In: RCPT TO: <reciepients@email>
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

[nobody]

OK. Found out what was going on !

Everyone using plesk 9.0 and postfix had the same and other problems with that up until 3 days ago. The bad thing is that everyone for 2 months was seeking for a solution and noone in Plesk would help. I read at least 50 people being left alone into this problem even when they had paid a ticket. Anyway.

There was a plesk hot fix which was not working for at least a month that they were re uploading it every once in a while. So if you have this problem and tried this hot fix in the past try it again because apparently now the hot fix is actually working !

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

Make sure that you replace the file , set permissions and immediately restart the postfix mail service.

If you follow their instructions everything should be fine.

What they did was actually change the timeout in 300 seconds.
Off course this will not help everyone ... You would expect more to be done in this issue. And generally I've understood that the mailing in plesk inst the best you can get as far as everything handling,quota etc ...

Attention : Keep a backup of the old file. For some reason the first time I applied the solution it did not work and generated crazy errors ! I rolled back to the old file. Restarted then redid the whole process and now it is working... Everything was done correctly the first time. Don't know how this is even possible but it did happen. So take your measures and be prepared...