• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

451 Error: queue file write error (when receiving emails)

fearz

Regular Pleskian
Hi,

I know that famous error when users trying to send emails from my server with large attachments,

recently i've been receiving such errors when users receive emails...

any ideas?

here is a transcript:


Transcript of session follows.

Out: 220 myserver.com ****
In: EHLO ****.linkedin.com
Out: 250-myserver.com
Out: 250-PIPELINING
Out: 250-SIZE 32504832
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:<[email protected]>
Out: 250 2.1.0 Ok
In: RCPT TO:<ssanad@****.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



Transcript of session follows.

Out: 220 myserver.com *****
In: EHLO kapo.*****.com
Out: 250-myserver.com
Out: 250-PIPELINING
Out: 250-SIZE 32504832
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: STARTTLS
Out: 220 2.0.0 Ready to start TLS
In: EHLO kapo.*****.com
Out: 250-myserver.com
Out: 250-PIPELINING
Out: 250-SIZE 32504832
Out: 250-ETRN
Out: 250-AUTH LOGIN PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:<mustafa@*****.com> SIZE=246060
Out: 250 2.1.0 Ok
In: RCPT TO:<aheshmat@*****.com>
Out: 451 4.3.0 Error: queue file write error
In: RCPT TO:<ahmedali@*****.com>
Out: 250 2.1.5 Ok
In: RCPT TO:<kezaby@*****.com>
Out: 250 2.1.5 Ok
In: RCPT TO:<mfaisal@*****.com>
Out: 250 2.1.5 Ok
In: RCPT TO:<mmohy@*****.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
 
Hi,

I know that famous error when users trying to send emails from my server with large attachments,

recently i've been receiving such errors when users receive emails...

any ideas?

here is a transcript:


Transcript of session follows.

Out: 220 myserver.com ****
In: EHLO ****.linkedin.com
Out: 250-myserver.com
Out: 250-PIPELINING
Out: 250-SIZE 32504832
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:<[email protected]>
Out: 250 2.1.0 Ok
In: RCPT TO:<ssanad@****.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



Transcript of session follows.

Out: 220 myserver.com *****
In: EHLO kapo.*****.com
Out: 250-myserver.com
Out: 250-PIPELINING
Out: 250-SIZE 32504832
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: STARTTLS
Out: 220 2.0.0 Ready to start TLS
In: EHLO kapo.*****.com
Out: 250-myserver.com
Out: 250-PIPELINING
Out: 250-SIZE 32504832
Out: 250-ETRN
Out: 250-AUTH LOGIN PLAIN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:<mustafa@*****.com> SIZE=246060
Out: 250 2.1.0 Ok
In: RCPT TO:<aheshmat@*****.com>
Out: 451 4.3.0 Error: queue file write error
In: RCPT TO:<ahmedali@*****.com>
Out: 250 2.1.5 Ok
In: RCPT TO:<kezaby@*****.com>
Out: 250 2.1.5 Ok
In: RCPT TO:<mfaisal@*****.com>
Out: 250 2.1.5 Ok
In: RCPT TO:<mmohy@*****.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

It's the same issue. Whether sending or receiving attachments: http://forum.parallels.com/showthread.php?t=85508

I switched to QMail and all my problems went away. Although with QMail you do get bare LF issues, but that can be fixed easily.

Thanks.
 
Very weird

I never had this problem when receiving emails, was only when sending, anyway i increased the smtpt connect time from 30 to 90..so far so good..

i'm really considering switching to qmail, but i faced that LF problem as well...which i didn't find any solution to...

So i'm stuck nowhere@!
 
I never had this problem when receiving emails, was only when sending, anyway i increased the smtpt connect time from 30 to 90..so far so good..

i'm really considering switching to qmail, but i faced that LF problem as well...which i didn't find any solution to...

So i'm stuck nowhere@!

Increasing the timeout will cause you more problems.

I was worried about switching to QMail too but it was so easy. Just one line:

/usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component qmail

The bare LF issue is completely fixed here: http://forum.parallels.com/showthread.php?t=94222

I had errors when compiling but I fixed that (as you can see at the end of that post).
 
Back
Top