Comment system changed
30/08/2009 10:51
I've just switched my commenting system over from HaloScan to Echo.
As a result all of the previous comments are currently unavailable but I'm working on getting them back.
Due to some other site changes the header images are also temporarily back to the theme default but I should have this fixed soon.
As a result all of the previous comments are currently unavailable but I'm working on getting them back.
Due to some other site changes the header images are also temporarily back to the theme default but I should have this fixed soon.
0 Comments
Articles merged with journal
29/08/2009 23:18
I've decided to merge the 'Articles' section of this website with the Journal.
All previous articles have been moved, and the old URLs are being redirected.
All previous articles have been moved, and the old URLs are being redirected.
Plesk Queue File Write Error
29/08/2009 22:10
One of the most anticipated features in Plesk 9 for me was the option to select Postfix instead of Qmail, and I did it as soon as I upgraded my own server to Plesk 9.
However, from time to time I would receive an error message email from Postfix indicating that one of my messages was not delivered, such as the following:
Out: 220 servername ESMTP Postfix
In: EHLO hostname
Out: 250-servername
Out: 250-PIPELINING
Out: 250-SIZE 102400000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN CRAM-MD5 PLAIN DIGEST-MD5
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM: SIZE=3368
Out: 250 2.1.0 Ok
In: RCPT TO:
Out: 250 2.1.5 Ok
In: DATA
Out: 354 End data with.
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye
There would also be an error message in the Plesk mail log such as:
postfix/spawn[16937]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
The Plesk knowledgebase article says that this issue will be fixed in a future release of Plesk and to change back to Qmail, something I didn't want to do so I set about finding a workaround of my own.
I discovered that by changing one line in /etc/postfix/master.cf from:
smtp inet n - - - - smtpd -o smtpd_proxy_filter=127.0.0.1:10025
to
smtp inet n - n - - smtpd
stops the error messages and allows those messages to be delivered.
Doing this breaks some features like spam filtering, but as my server sits behind an IronPort email security appliance for mail all messages are filtered prior to delivery anyway so this was a compromise I could live with.
However, from time to time I would receive an error message email from Postfix indicating that one of my messages was not delivered, such as the following:
Out: 220 servername ESMTP Postfix
In: EHLO hostname
Out: 250-servername
Out: 250-PIPELINING
Out: 250-SIZE 102400000
Out: 250-VRFY
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250-AUTH LOGIN CRAM-MD5 PLAIN DIGEST-MD5
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL FROM:
Out: 250 2.1.0 Ok
In: RCPT TO:
Out: 250 2.1.5 Ok
In: DATA
Out: 354 End data with
Out: 451 4.3.0 Error: queue file write error
In: QUIT
Out: 221 2.0.0 Bye
There would also be an error message in the Plesk mail log such as:
postfix/spawn[16937]: warning: command /usr/lib/plesk-9.0/postfix-queue exit status 255
The Plesk knowledgebase article says that this issue will be fixed in a future release of Plesk and to change back to Qmail, something I didn't want to do so I set about finding a workaround of my own.
I discovered that by changing one line in /etc/postfix/master.cf from:
smtp inet n - - - - smtpd -o smtpd_proxy_filter=127.0.0.1:10025
to
smtp inet n - n - - smtpd
stops the error messages and allows those messages to be delivered.
Doing this breaks some features like spam filtering, but as my server sits behind an IronPort email security appliance for mail all messages are filtered prior to delivery anyway so this was a compromise I could live with.
Back from the United States
20/08/2009 16:53
This morning I returned home after spending just under two weeks in the United States.
The primary purpose of the trip was for HostingCon, "The World’s Largest Gathering of Hosted Services Professionals", which was very worthwhile. I have a lot of ideas, and made a lot of new connections which I'll be spending the coming weeks and months exploring.
I also took a few days of leave and spent some time doing the tourist thing.
More info to come in time.
The primary purpose of the trip was for HostingCon, "The World’s Largest Gathering of Hosted Services Professionals", which was very worthwhile. I have a lot of ideas, and made a lot of new connections which I'll be spending the coming weeks and months exploring.
I also took a few days of leave and spent some time doing the tourist thing.
More info to come in time.