For everyone who has not updated to a 5.1.x version. This is a bug fix release and it is up to you if you want to upgrade. If you don’t have any current issues you don’t need to upgrade.

Check all the fixes that are listed on the release notes to see what issues are resolved and if you are affected.

I’ve compiled this version and did some simple tests on Leopard and Tiger and both can be compiled and installed using the instructions in the documentation set without problems.

Read the documentation on how to ugrade MySQL.

For everyone who has upgraded to a 5.1.x version. This is again a bug fix release like 5.1.39 and it is up to you if you want to upgrade. There are no apparent security issues solved in this release. This is a very quick release after 5.1.38.

Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. Most of them are concerning replication.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

For the people still running the Courier setup. Yes I know I still need to publish the migration scenario. The IMAP server got a small update. It is not a security fix so if you haven’t run into any problems you can skip this one.

Issues solved in this release are:

• outbox.c (imapd_sendmsg): Renamed sendmsg() to avoid library name clash.
• courier.sysvinit.in: Fix typo in init file.
• tls: change the default OpenSSL configuration to disable anonymous
  authentication ciphers.
• DROP options for couriertcpd, set in the esmtpd configuration file: drop connections from blacklisted IP addresses, rather than accepting connections and rejecting all mail from them.

PHP have released an update to the 5.2.x version. Many people still have problems with the backwards compatibility of 5.3 and are still using 5.2.10. In this release which is a security bug-fix and if you are running 5.2.10 I would urge you to upgrade.

Security Enhancements and Fixes in PHP 5.2.11:

• Fixed certificate validation inside php_openssl_apply_verification_policy.
• Fixed sanity check for the color index in imagecolortransparent().
• Added missing sanity checks around exif processing.
• Fixed bug #44683 (popen crashes when an invalid mode is passed).

Key enhancements in PHP 5.2.11 include:

• Fixed regression in cURL extension that prevented flush of data to output defined as a file handle.
• A number of fixes for the FILTER_VALIDATE_EMAIL validation rule
• Fixed bug #49361 (wordwrap() wraps incorrectly on end of line boundaries).
• Fixed bug #48696 (ldap_read() segfaults with invalid parameters)
• Fixed bug #48645 (mb_convert_encoding() doesn’t understand hexadecimal html-entities).
• Fixed bug #48619 (imap_search ALL segfaults).
• Fixed bug #48400 (imap crashes when closing stream opened with OP_PROTOTYPE flag).
• Fixed bug #47351 (Memory leak in DateTime).
• Over 60 bug fixes.

For instructions on how to upgrade PHP please read: Upgrading PHP.

I’m very busy with a lot of updates which I need to test on all my test machines and production systems that I wish there were more than 24 hours in a day to get everything done. My current dayjob is also very interesting and challenging and requires a lot of input from my brain. But I’m still chugging everything as well a I possibly can so expect some more blogposts in the coming week.

Here is nice one for the people wh recently bought a mini, someone found out that it will take 8 Gb of usable memory just like the newer MBP’s. It’s a shame that it still soooo expensive but it is a good thing to look forward to. I’m almost temped to by another mini just to see how this would perform. I think it would make a awesome server, although I must confess that of my current production server only half of it’s 1Gb is in active use.

For people looking to host a server at MacMiniColo.net, they have some second hand mini’s listed on the sign up page which will do the job perfectly for less money. I did this myself as well and it is stil working. I like their service so much I recently renewed for a two year period.

Back to testing…

Update: Forgot to mention that I’ve finished installing everything on a clean install of Snow Leopard. So that now works as it is supposed to do. Next up getting my mini ready for the update and installing everything in 32 bits.

A new verison of Dovecot has been released a few days ago but I’ve only been able to test it today, sorry busy week.

The bugfixes include:

• Authentication: DIGEST-MD5 and RPA mechanisms no longer require user’s login realm to be listed in auth_realms. It only made configuration more difficult without really providing extra security.
• zlib plugin: Don’t allow clients to save compressed data directly. This prevents users from exploiting (most of the) potential security holes in zlib/bzlib.
• Added pop3_save_uidl setting.
• dict quota: When updating quota and user isn’t already in dict, recalculate and save the quota.
• file_set_size() was broken with OSes that didn’t support posix_fallocate() (almost everyone except Linux), causing all kinds of index file errors.
• v1.2.4 index file handling could have caused an assert-crash
• IMAP: Fixes to QRESYNC extension.
• virtual plugin: Crashfix
• deliver: Don’t send rejects to any messages that have Auto-Submitted
  header. This avoids emails loops.
• Maildir: Performance fixes, especially with maildir_very_dirty_syncs.
• Maildir++ quota: Limits weren’t read early enough from maildirsize file (when quota limits not enforced by Dovecot)
• Message decoding fixes (mainly for IMAP SEARCH, Sieve).

I’ve updated my test server with Mac OSX 10.6.1 The update went without any problem and my setup was not affected in a negative way. It took me some time to check everything.

If you want to read more on what is affected in the updates I would suggest reading the Apple support site for the 10.6.1 update.

In case of doubt, please make a full bootable disk image backup with Carbon Copy Cloner before you start. There are some people having reported problems with previous update so better be safe then sorry!

This update is only for Leopard and Tiger users (Snow Leopard is not affected). I have not tested this on Tiger as I have no longer a machine with Tiger installed but I’ve tested the Leopard based update and that went without a problem. My production server and two of my test servers received the update and installed it without any problem.

Read more about the security update here.

n case of doubt, please make a full bootable disk image backup with Carbon Copy Cloner before you start. There are some people having reported problems with previous update so better be safe then sorry!

Allright, a bit later than I had anticipated and planned. But that’s what you get if Apple starts releasing stuff earlier then expected. It screws with your planning. But the instructions for installing the basic mailserver in 64 bits are finished and tested on my MacBook Pro. This new machine is a god send and worth every penny up to now.

Please note that these are my initial instructions using an upgraded machine. Next up I need to test the instructions on a clean install of Snow Leopard. When that’s done I will upgrade my Core Duo mini to Snow Leopard and see how the 32 bits version will work out.

Happy reading: The mailserver on Snow Leopard

Good luck and can you please let me know if it worked for you?

Here is a quick update on getting Apache, PHP and MySQL installations working again after the Snow Leopard upgrade.

For Apache I did a recompile and install because the config was completely lost (and I had no backup!) and this was the quickest way for me. The normal 64 bit Leopard instructions did the job for now, will look later at possible enhancements.

MySQL I could just startup with the System Preferences MySQL panel. Will do a recompile later today and will update this post with the findings. This as MySQL is updated to 5.1.38

PHP gave the most issues, but a comment from Nico helped out. This problem is valid for 5.2.9 and 5.3.0 but it should be solved in 5.3.1 as the bug was listed as solved in 5.3.1.dev

To solve the problem, follow the normal instructions on this site but after the configure statement you need to edit the Makefile which is created by ./configure

You need to add ‘-lresolv‘ at the end of the line which starts with ‘EXTRA_LIBS‘ like:

EXTRA_LIBS = -lmysqlclient -lssl -lcrypto -lz -lssl -lcrypto -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lmysqlclient -lz -lm -lmysqlclient -lz -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lresolv

As noted earlier, I will keep updating this blogpost till most issues are resolved or properly documented elsewhere on the site.

Update 1: MySQL compiled without a problem using the 64 bits Leopard instructions.

Update 2: Finished some of the PHP documentation on Snow Leopard:

• Compiling PHP in 64 bits mode on Snow Leopard
• Adding the GD module to PHP on Snow Leopard
• Adding the mcrypt module to PHP on Snow Leopard

Update 3: Added Apache install instructions:

• Compiling Apache in 64 bits mode on Snow Leopard

Update 4: Made a new page with all related Snow Leopard instructions. MAMP stack documented, mailserver will follow!

Last update: Mailserver instructions.