|
mac geekeryGet your geek on. |
|
|
mac geekeryGet your geek on. |
We're Idle, Kill It All!March 8, 2006 - 11:30pm
I use two machines – my PowerBook and my iMac, and I often walk away from the iMac and start using my PowerBook on the couch. And all is right and good until I remember that I left Mail checking my IMAP inboxes on the iMac. SleepWatcherAfter digging around a bit, I found SleepWatcher, which monitors your system for idle, dim, undim, sleep, and wake events, and allows you to execute shell commands at those times. Via /etc/sleepwatcher.confI created a config file for SleepWatcher at timeout=7200 idle=osascript -e "tell application \"Mail\" to quit" The Startup ItemI hacked the StartupItem a little, as well. Where /usr/local/sbin/sleepwatcher -V -d -f /etc/sleepwatcher.conf
About JC |
|
||||
It’s IMAP! Unlike POP3 its not like your messages are going to be download only to the iMac, they will still be available to view on the Powerbook!
Filters, my friend. Filters.
I’m not sure why you should be fighting so hard on the client to do things like this — it’s IMAP!! The whole point is that the work is done on the server.
Your filters should be on the server — by the time you log in, every message should be where it is supposed to be already (other than deleting a few spams that sneak through).
If you’re counting on client filters to accomplish important tasks with your mail, you’ll never be able to use IMAP as simply as it should be. The mere fact that you’re having to create Rube Goldberg devices to prevent one IMAP client from checking your mail before another is proof of that.
That’s not quite the entire point of IMAP, though it is a big selling point. For some users. I store my mail mixed between local and remote folders, based on whether they’re personal, business, or otherwise, and a small number of other factors. There’s some server-side procmail filtering going on, and a lot of client side filtering going on.
My personal uses are such: I check all Inboxes and all server folders on iMac, but I only check one Inbox on my PowerBook. In my setup, it’s not a deal killer if both clients run at once, but it’s a little annoying.
There’s another good reason to kill unused IMAP clients though – server side memory constraints. Each connected client has a memory footprint that, due to repeated checking by the client, can’t effectively be swapped out.
If you’re using a corporate IMAP server that is well funded, this is not a big deal. If you run your own server through a shared hosting provider, on the other hand, that can be a killer.