Queue Write failure 1

[tlcscousin]

We have a plesk 9.2 server on Debian 4 running Postfix and suddenly after 2 years of no real issues are getting a Queue Write failure.
Plesk has a patch but really hate running patches from them as they usually pooch something else patching things.
Is there any fix for the Queue write errors? Some articles talk about disk space being low on Var but this is not the case. Some say edit the conf file and change the timeout to 3600. Any pointers or thoughts on why it would suddenly start throwing the error and if so has anyone had success fixing that error?

 

[tlcscousin]

We have resolved the issue by removing the SPF file. Once removed email started flowing as normal. WE then added the SPF record back in again and everything still worked as per normal.

 

[Noway2]

Thanks for following up on this thread with what you found the problem to be. I admit that I am curious how the SPF record caused this problem and more so how it still worked when it was put back in.

What lead you to suspect / try the SPF record? A write error to the queue sounds more like a disk access or permission issue. My understanding of the SPF record is that receiving domains use it to verify that the machine sending messages is designated as an email server. I would think that if the SPF record were to cause a problem, that it would be the inability to send mail (which you had) but that the result would be a bounce.

 

[tlcscousin]

It was actually the bounce back from people trying to send to the domain that showed the queue write error.I am not very versed in Linux so had a friend who is very knowledgable in linux look at the mail logs. He said there were plenty of errors pointing to SPF. We decided to remove the spf record as a test and immediately the same people that were unable to send were then getting mail delivered.
We waited a few days then recreated the SPF record and email was still flowing.
Looking at the SPF record we recreated it is identical to the one we removed.
I actually had read several posts suggesting upgrading postfix but several who had done so still had the same issue and they in turn removed SPF and fixed the issue.