Here is a new version of Postfix, just released and I’ve got it tested on Snow Leopard and Leopard on my test machines. It solves some small bugs as listed below:

• Fixed a “signal 11″ bug with Postfix SMTP server debug logging at smtpd_tls_loglevel ≥ 3.
• The Postfix SMTP and QMQP servers no longer look up IPv6 address information while looking up the FCRDNS (forward-confirmed reverse DNS) hostname for an IPv4 remote client (and vice versa).
• The postscreen(8) daemon no longer logs a “connection reset by peer” warning when a remote SMTP client hangs up prematurely.
• Removed spurious configuration parameters from “postconf” output, by deleting the #ifdef MIGRATION_WARNING transitional code from postscreen(8).
• Assorted minor documentation fixes.

Note:
Some people have reported problems with updating from an older version that the TLS is no longer working. If you upgrade please add this line to your main.cf configuration file:

smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL

and restart postfix. Everything should work as expected.

As usual you can read the instructions on how to upgrade Postfix at Upgrading Postfix.

Wow, this is a big surprise. I never expected this. On the new Mac OS X Lion preview page there is a long list of the new features that are included. I almost didn’t notice the last part because I was overwhelmed by the first features and thought, oh yes there is going to be a server version as well. As there where earlier rumors that the server version would be discontinued.

But no, server is not going to be discontinued, its going to be part of the normal version. So no more $499,- for a server, it’s already included in the standard OS.

I’m not sure what this would mean for our site. I still need to let this sink in. I think we will wait and see until I’ve installed my version of Lion during the summer (I don’t have access to the developer version). One of the things that spring to mind is that it is difficult to manage multiple domains with many users in the server version of OS X as each user must be defined as a local user.

So we will keep our options open but we would love to hear your feedback on this bombshell.

What do you think, is there still a future for DIYMacServer?

As a follow up to an earlier blog post on backup and recovery strategies I read the article on MacWorld today from Lex Friedman detailing his backup strategy. I thought it was nice enough to share the article here.

In short his strategy comes down to Time Machine, plus a bootable clone via SuperDuper (or CarbonCopyCloner), plus offsite backup with CrashPlan, plus Dropbox, plus Google Docs. Please add a pinch of hysteria…

MySQL released version 5.1.55, this is a bug fix release which also includes some security fixes and it is up to you if you want to upgrade. Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. I’ve compiled it and did some tests on my servers and it worked without any problems.

Read the documentation on how to ugrade this version of MySQL.

MySQL also release a new version of the 5.5.x branch which is already usuable in our setup when you read this blogpost. It works perfectly on my test machine. It includes several high-impact changes to address scalability and performance issues in MySQL Server. These changes exploit advances in hardware and CPU design and enable better utilization of existing hardware. MySQL 5.5 also provides a number of other new enhancements. Read the release notes for more details.

Read this documentation on how to ugrade this version using the package installer of MySQL.

The hardworking folks over at clamav.net have released an upgrade to their virus scanning software. Upgrading is relatively easy and straight forward. All that needs to be done is remove the old version and install the new.

You can check the instructions on what to do here Upgrading ClamAV.

There is no need to reconfigure anything.