http://bugzilla.zimbra.com/show_bug.cgi?id=21441 

Zimbra version 5.0.5 supports Leopard, a boon for those organizations wanting to use new Mac hardware to run the popular mail and collaboration server software. Note this is for running the software yourself, if you just want to use Zimbra, you can avoid licensing or server hardware/maintenance/hosting fees, instead use an authorized, Zimbra hosting provider such as 01.com .

http://www.zimbra.com/blog/archives/2008/03/caldav_leopard_goodne

http://docs.info.apple.com/article.html?artnum=107657

01.com has confirmed it’s upgrading to Zimbra 5 this weekend.

See their blog about the planned update to Zimbra 5.0.2 here .

Zimbra is the collaboration suite that provides, email, calendar and contact sharing and delegation for Macs, that also works with Windows and Linux, making a top tool for mixed, cross-platform environments, instead of Exchange, Notes, Groupwise or Google Apps.

Commenting on this announcement of Zimbra 5’s improved support for Safari 3, iCal and the iPhone, Daniel Stone, Channel Manager for 01.com , an authorized Zimbra hosting provider, said, “We are building a strong network of Mac Consulting resellers around the world, and this is great news for them and our mutual customers. They’ve been successfully positioning Zimbra as an alternative to Microsoft Exchange for the last year, delivering better Mac email, calendar and contact integration at a lower cost, and the solution is just getting better.”

Find out more about the Zimbra technology at http://faqs.01.com

Find out about 01.com’s Zimbra reseller plan at http://reseller.01.com

Read more about the recent press release about Zimbra and Apple technology here, from Yahoo!’s press room .

“This update addresses a responsiveness issue on MacBook and MacBook Pro notebook computers. Some MacBook and MacBook Pro systems may occasionally experience a temporary suspension of keyboard input which can last a minute or longer. The Mac OS X 10.5.1 update is required before installing the MacBook, MacBook Pro Software Update 1.1.”

You have to go to iCal prefs and select show birthday calendars and then resync the iPhone. Then in iTunes, you’ll have the Birthdays calendar available to check off. Resync and you’re in business. Screen shots included below.

1. Check off show birthdays calendar under ical>preferences.

2. Sync Your iPhone.

3. You will now have a Birthdays calendar to choose in iTunes under info.

4. Now just sync the phone again and you are all set.

1. There is a script called Manage SMTP Servers.scpt which is stored in Macintosh HD/Library/Scripts/Mail Scripts/ Double clicking the script file will launch the Script Editor. Since we are only wanting to execute the script press Run. This will bring up a list of SMTP severs that are not associated with an account in Mail.app. Hilight the servers you no longer want (you can select multiple by using the command-click method) and press OK. All those old servers are now gone.

2. Under OSX.3 and OSX.4 the Mail.app software allows the user to edit the SMTP server list when configuring an account. Navigate to Mail.app >Preferences >Accounts >Select any listed account on the left >Click Outgoing Mail Server on the right >Scroll through the list to the bottom and choose Edit Server List >Hilight the server to be removed >Click Remove Server. You will want to remove any server not associated with an active account. If you happen to delete an active server you will need to edit that email account’s settings and add the appropriate SMTP information again before sending email with that account.

3. If you would rather start Mail.app with a fresh slate and get rid of all the references to old accounts, present accounts, and personal tweaks you should close Mail.app. You can then can drag the ~/Library/Preferences/com.apple.mail.plist file to the desktop and restart the application. Mail.app will act as it did the first time it was started and will ask for account information. If you don’t like the results of this, close Mail and simply drag the file back to it’s previous location and restart.

Posted on 05 Nov 2007 12:07 PM

After upgrading to Leopard, I had no trouble accessing my server-based home directory. For reasons not worth going into here, I wiped the drive clean and reinstalled Leopard, and now cannot log in using any server-based account. I’ve set up the LDAP connection in Directory Utility, and verified that everything there matches the setup on another (working) computer, but am still unable to log into the computer using a server-based account. The server is still Tiger, but it can’t be a Tiger-Leopard incompatibility because it worked after my initial Leopard upgrade. It’s not just my account; other server-based accounts don’t work either with this fresh Leopard install — accounts that do work on other (Tiger) computers. I’ve deleted and re-done the LDAP setup, but it still doesn’t work. Suggestions?

Posted on 06 Nov 2007 08:59 PM

[We suggest] Go back to Tiger.

We’re not recommending the upgrade to Leopard for production environments for at least a few months, as we’re confident there will be updates that will resolve the majority of issues.

If you want to experiment, use a non-production system.

Posted on 07 Nov 2007 03:41 PM

But some of us have to live on the bleeding edge, right?

While good advice, this was not a real viable option for me. After originally upgrading my computer to Leopard, Mail.app did some conversion to the mail files the first time I opened it. While mail worked in Leopard, this “conversion” rendered my mail inaccessible from Tiger; I could still see all my mail folders in Tiger’s Mail.app, but they were all empty, and nothing I did got their contents to show. This was strictly a Tiger-client-with-server-home-directory issue: from my home computer (Leopard, but not using a server-based home directory), squirrelmail and iPhone, all my mail was visible and worked correctly. I’m assuming the conversion affected only the cached versions of my mail in my home directory, not the actual files sitting on the IMAP server.

So, unless I wanted to go without Mail.app for “at least a few months,” I needed to get my server-based account login to work in Leopard. Since it had stopped working when I did a fresh Leopard install, but did work after my original Tiger-to-Leopard upgrade, I decided to try that route again: wiped out Leopard, installed Tiger (and updated it to 10.4.10), then upgraded to Leopard — and now my account login works again, as does my Mail.

So my problem is resolved, and I just thought I would pass along the details of this experience to add to what I’m sure is your rapidly growing database of Leopard trivia, in case somebody else finds themselves in the same situation.

—- end —-

Consider the details passed! Thanks for letting us share.

While we’re happy to work with clients to trouble-shoot issues caused by the upgrade to Leopard (that’s what we get paid for), we also get paid to provide quality advice to our clients, advice that saves them time and $$. Most businesses will benefit from the upgrade to Leopard, and there’s no need to be first through the gate, unless Leopard is fixing a problem, or providing a solution, for which you simply cannot wait.

In the last day there’s been some news about a new bit of somewhat-malware on the mac. “Somewhat” because at least in its current form, and relative to some very nasty virii out there, this code rates as just above harmless. That it was announced on Halloween is probably the scariest thing about it. Never-the-less, it is an unwanted and uninvited bit of code, and here’s how to determine if you’ve been infected.

The new malware apparently changes your DNS settings, and in doing so, reveals itself, as well as adding a Cron job, among other code. In Lepard, OS X 10.5, it’s easy enough to see if your domain name servers have been changed. You can use the Advanced Network settings preferences in your system preferences. In OS X 10.4 or earlier, however, the graphical user interface (GUI) in the Network preferences does not reveal your domain name servers. You’ll need to launch Terminal, which if you’re not already familiar with it should make you feel very old-school as this runs the command line interface (CLI) for the Mac, and can be found in the Utilities folder/directory, which is in your Applications folder/directory.

In the terminal, copy and past the following command, then click enter/return to execute/run it:

cat /etc/resolv.conf

This will show your domain name server(s) (DNS), which are the servers your computer uses to translate host and domain names, such as www.01.com, to network address numbers, such as 38.98.186.151.

Digression on DNS lookups, etc: note that you can use another utility in your Utility folder, called Network Utility, to perform various lookup functions in a GUI on the mac, or you can just use the Dig command. If you want to learn more about the Dig command, to bring up the manual on “Dig” in the Terminal type:


man dig

While it’s possible that a cron job (the scheduled start of a program) can be associated with another user on your system, if you want to check for cron jobs associated to your username, you can run this command:

crontab -l