OS X

Moving mailman from one server to another

Yesterday brought the much anticipated (dreaded) task of moving mailman from one server to another. The move was necessary to retire a FreeBSD server and consolidate services on a Mac OS X 10.4 Server box. There are good documents on the web about setting up mailman on OS X 10.4 Client but not as many on the setup of a standard mailman install on the server platform.

The first question that may jump out at folks is why? Mac OS X 10.4 Server comes with Mailman already installed. Why not use it? The installation included in OS X is highly customized in order to work with Apple's server administration tools. Also in my case I was moving a Mailman 2.1.6 installation on FreeBSD and the OS X Server version is still 2.1.5 (though it has been nearly six months since the release of the security patches in 2.16). Looking at the documentation there is little suggestion changes would have prevented the newer files from working but as a Nevadan I prefer the house's odds to those of the gambler.

Software Update problem not with DirecWay

After setting up a new iMac G5 recently there were a plethora of software updates to be downloaded. The problem is that after the first time where the update window showed two pages of available updates it subsequently refused to show any at all.

Thinking that the problem might have to do withDirecWay as the DirecWay XML-RPC does.

However, the fault seems to be with OS X instead. If there is a cache file in the following directory remove it and all should be well:

/Users/yourname/Library/Caches/com.apple.softwareupdate/00/14

Apple issues security update

Apple Computer today released a security update for its Mac OS X 10.3 and 10.4 operating systems. The update addresses several potential vulnerabilities. The worst of these allow a malicious website to execute code on a browser's computer through the Safari web browser. With the quick patching of these issues the chances of exploitation are low. However, this provides a great reminder why one should limit browsing from a server computer as much as possible.

iPod blues

I've been working on a friend's iPod recently. The otherwise healthy iPod has started freezing every time you move songs to it. Choose a batch of 20 songs and 5 or 6 will transfer fine and seven will die. The real problem is that it is not just the iPod that freezes but the whole computer. The machine (running Mac OS X 10.4) will stop completely. A few processes are "stuck" but even attempting to shut-d. own or restart the computer don't work. The only solution is to power down the computer and restart it. After a restart the whole scenario plays out again.

After several tries with other iPods and the computer it seemed to be a problem with the specific iPod. A trip to Apple Care and back and they report the iPod is just fine. Upon transferring the next set of songs the familiar freeze was back. The iMac locked up completely. Had Apple Care missed something? Why did this computer that works with other iPods not work with this iPod.

Eventually I decided to reload the iTunes library to make sure there wasn't a problem with the library itself. After taking all the files out and re-importing them there was no difference. Could it be the cable? The cable had been used for a couple of years and had never really been taken anywhere or used in any other way. However, it occurred to me at that point that the "other iPods" that were working fine were all USB models. Plugging the ill-functioning iPod into the USB cable it performs flawlessly. Somewhere along the line one of two things has happened. Either there is a problem with the firewire cable, which I'm still skeptical about, or there is a problem with the OS on the iMac and how it recovers from firewire errors.

OS X 10.4 vs. Drupal Mailhandler

After upgrading from OS X Server 10.3 to OS X Server 10.4 the Drupal Mailhandler stopped working on the server. Clients could login and get mail no problem. Even Squirrelmail worked flawlessly.

However when the mailhandler module would try to login the response in the error log was:

TLS server engine: cannot load CA data
TLS server engine: No CA file specified. Client side certs may not work
STARTTLS negotiation failed:

A few sites suggested permission problems with the /etc/certificates directory but that did not seem to be the problem in my case. Ultimately it was fixed by going to Server Admin's general settings and re-creating the server's self-signed certificate.

How did I ever?

Over the weekend I finally got around to downloading iScroll2 a two-finger scrolling trackpad driver for older Apple laptops that don't come with the functionality. Honestly I thought I'd play with it a little and decide I didn't care one way or the other. What's the big deal with two-finger trackpad scrolling. I couldn't have been more wrong. It is a fantastic new addition to PowerBooks.

Safari's Home Button

Dave Winer comments on Apple's decision not to include a "Home" button in the default toolbar of Safari. As pictured above it can easily be put back by choosing Customize Address Bar... from the View menu. I've often wondered about the choice but don't often think of it because it's solved in the first few seconds I use Safari and never an issue again.

Terminal Widget

Needing to do a little system administration from the road I stopped in the local Apple Store. Unfortunately they've decided to lock up the terminal application in a password protected archive. That is one place Widget Term comes in handy.... Download it and viola even a machine without terminal now has a terminal.

The Mighty Mouse

No, it's not a Disney creation or Pixar either. Steve Jobs' other company has announced the new Mighty Mouse. I'll have to go in and take a look at one to see if it will be appealing. For several years I've been a die-hard trackball user and don't know if this gem will sway me or not.

Identification of the problem

James Goodlet has identified the cause of the evil exited, signaled to death by 6 errors in Mac OS X Server. Really, it is a problem with the Cyrus IMAP server. Goodlet explains as well why the problem occurs when checking email with Mail.app and Entourage but not with Thunderbird. The short version is that the Cyrus IMAP server's reconstruct command rebuilds the message index with INTERNALDATE having a length of 0. This condition is illegal. Mail.app and Entourage request the INTERNALDATE attribute but Thunderbird and WebMail do not.

The long and short is this is a problem that has to be fixed on Mac OS X Server. It is not a client problem (there are other problems with Mail.app).

Subscribe to OS X