Earlier today, I posted about the ability to find previously deleted emails using the Spotlight search on the iPhone, adding to the already intense swarm of news surrounding this issue. My findings were that, by ensuring your trash folder was emptied and refreshed, the problem appeared to be solved.

However, many of you responded indicating that this did not work for you, and that you were still seeing cached messages. Then Cult of Mac posted an update to their original piece, suggesting that the problem was more specific to POP accounts. Although I had tested both POP and IMAP accounts with similar results, I decided to investigate further.

First, to clarify: The problem here is *not* with Spotlight caching the contents of your email, as many have suggested. Spotlight simply indexes the available content on your phone, and logs a pointer to it. When you tap a search result, it opens the associated application and tells that app to view the content. In this case, it sees an email message and asks Mail.app to open it, which it does, because Mail.app still has the message content stored locally. Secondly, this appears to be specific to POP accounts. On IMAP or Exchange accounts, deleted email messages do appear in Spotlight results until the trash folder is emptied, as described in my earlier post.

I created a fresh account and configured it for POP access, then downloaded the mail. Searching spotlight, I could see the message I was looking for. I then went back to the message and deleted it, and that's where the fun starts. I conducted this same test multiple times, and found that sometimes, the message would now show up in Spotlight twice, one result opened the message, intact, with the Inbox listed as the folder to return to; the other displaying a message in the trash folder, but with an error displaying the body of the message. Other times, I would only see one result, pointed directly to the trash.

Being the Kool-aid sipping, Apple fanatic that you are, I'm sure you have already updated to the latest versions of iLife and iWork, right? If you have then it's not unlikely for you to be experiencing the same kind of problem that Rob Griffiths over at Macworld is dealing with as well.

Following his recent upgrade to the latest (and greatest!) version of iPhoto, Rob noticed some inconsistencies in the way Help was providing him information. Specifically, he had trouble with locating documentation on the new Faces feature when navigating through iPhoto's Help menu and launching the Help application. Rob was able to locate the documents he sought by using Leopard's Spotlight-esque Help-searching feature and querying for "Faces."

During our review of iPhoto '09 we did not come across any issues with the Help documentation. But we here at the TUAW headquarters at the Winter office in Hawaii are too stubborn to read directions. Rob's problem seems to be an old one that has occasionally plagued users through many versions of OS X. He points to another article at Macworld by Chris Breen which covers some tactics for wrangling Help back into line.

The culprit in this whodunit case turns out to be Help's cache file (in the library with the candlestick). According to Rob, "Help relies heavily on cache files to present its information to the user." For reasons unknown, upgrading an application does not necessarily cause the cache files to rebuild. In order to force the system to accomplish this, first quit iPhoto then navigate to the current user's home directory -> Library -> Caches (~/Library/Caches) and locate "com.apple.helpui." Once the cache file is located, drag it into the trash and restart iPhoto. Boom! You now have a working-as-intended iPhoto Help viewer.

While any application's help cache can become obsolete, Rob notes an increase in likelihood for Apple's own applications. Whether you're experiencing problems with an Apple app or not, deleting the cache file is very likely the solution. Have you had any issues with an application's help viewer? If so, which app was it and how did you resolve it? Let us know in the comments!

Apple's Mac OS X 10.5.5 update (and Security Update 2008-006) fixes a critical DNS vulnerability that could allow attackers to trick victims into visiting malicious Web sites using what's known as a "cache poisoning attack." We wrote about the vulnerability in August.

Although Apple's release notes say BIND was updated "to address performance issues," the update also delivers the promised address port randomization that protects users from such cache poisoning attacks. The original patch offered protection for Apple's servers but did not completely protect client systems.

Apple's updates fixed flaws in several applications and system components, including some that attackers could use to run unauthorized software on a user's computer.

[Via IDG.]

TUAW reader Simon wrote in to us, to share one of his favorite new Leopard features--and its unexpected consequences. After clicking on an All Images search, he was astonished to find any number of odd gifs and jpgs pertaining to, um, Viagra, and er, male enhancement. He quickly realized that All Images was displaying bits (and we do mean bits) from Mail's download cache. This means that although he set Mail to not download HTML images, they're getting downloaded anyway. Simple annoyance or possible security breech? You tell us in the comments.