Apple Security Update 2005-003 (#3): Apple pulls Mac OS X server version of update; Site compatibility problems within Safari

Apple pulls Security Update 2005-003 for Mac OS X Server Likely because of the severe issues affecting IMAP and APOP e-mail service (caused by a modification to the Cyrus mail service component of OS X server) reported here on MacFixIt yesterday, Apple appears to have pulled Security Update 2005-003 for Mac OS X Server.

No word has yet surfaced on when a revised update will be released.

In the meantime, if you are one of the users who applied Security Update 2005-003 to Mac OS X Server 10.3.8 and are experiencing adverse reactions, follow the procedure in our tutorial "Reverting to an earlier version of Mac OS X," applying all updates through Mac OS X 10.3.8, excluding Security Update 2005-003 (which will no longer appear in Software Update anyhow).

One typical manifestation of the APOP/IMAP problems reported yesterday is described in a report from MacFixIt reader Jason Self:

"I applied the Security Updated 2005-003 to my copy of Mac OS X Server 10.3.8. Disk permissions were repaired before and after.

"My server is no longer delivering mail. It had been configured to use Procmail using the directions from http://www.afp548.com/articles/Panther/procmail.html.

"Now messages are queueing up in the Postfix queue with the error "temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ procmail: Program failure (75) of '/usr/bin/cyrus/bin/deliver'"

Site compatibility problems within Safari/Timeouts As is the case with most Apple security updates, changes to key Web page rendering/delivery components in Security Update 2005-003 break compatibility with a number of Web sites in Safari.

MacFixIt reader Nick reports issues with the popular AtomFilms Web site: Since installing Security Update 2005-003, Safari crashes every time when I visit the site www.atomfilms.com. I subscribe to this site, visit it regularly, and have never had this problem before. The site displays and behaves properly in Internet Explorer (on the same Mac). The crashes occur with every page on the Atom site that I have tried to access, and this happens just before the page has finished fully loading (status bar typically says 65 of 67 items loaded, or similar)."

A number of other readers report timeouts in Safari, which are similar to the aforementioned case -- Web pages start loading and fail, or never begin to load at all.

MacFixIt reader Mike writes "Since installing Security Update 2005-003 I have been having intermittent connectivity problems with Safari.

"Spontaneously (or so it seems), Safari's ability to access the web will fail, but I can still ping the sites from the command line, and open the URLs in other browsers. However, all attempts in Safari result in timeouts. Quitting and relaunching Safari fixes things."

Potential fix MacFixIt reader Daniel Welch reports a potential workaround which involves removing the Apple WebKitFramework (located in /System/Library/Frameworks/) then re-installing Safari:

Daniel writes:

"Just wanted to let you know that the latest security update left me with Safari completely unresponsive to clicks on links. To fix I downloaded Safari from Apple's website but didn't install it. I went to System/Library/Frameworks/WebkitFramework and dragged Webkit Framework to the trash. I then dragged Safari to the trash and reinstalled it from the new download. I repaired permissions from Disk Utility and everything works great again."

Note, however, that this procedure will remove any security modifications made by Apple as part of Security Update 2005-003.

Printer sharing difficulties Users continue to report problems with shared printers after applying Security Update 2005-003, likely due to modifications Apple made to the AFP (Apple File Protocol) as part of the update.

One reader writes:

"I also installed the Security Update on my G5 PowerMac. This seems to have broken the ability of my G5 to share a Brother laser printer and Canon ip 5000 attached via USB with an old iMac."

Potential Fix Some readers have reported that simply deleting then re-adding the afflicted printer from within Printer Setup Utility (located in Applications/Utilities on a standard Mac OS X installation) on the remote (not printer-attached) machine resolves the issue.

Peter Schooley writes:

"When I updated my desktop (the machine sharing the printer) my Powerbook could not detect my Desktop print server. I was able to fix this problem by deleting the printer in my shared printer list on my Powerbook and then re-adding the shared printer. I had repaired permissions and rebooted both machines without success. I tried deleting and adding the printer on my print server (the desktop) without success. Deleting and adding the printer on the client (Powerbook) is what did the trick."

Feedback? Late-breakers@macfixit.com.

Resources