Month: February 2014

Email Productivity Tip: Differentiate email sent “to” you, “cc”‘ing you, or including you on a list

~ Matt Smith ~ Leave a comment

Do you receive hundreds of emails per day, with varying levels of relevance and criticality?  Do you already apply mail filters to route certain lists or senders into folders, but still suffer with trying to triage email that doesn’t come from a one of these predefined origins?

There is no magic bullet, but I noticed a simple pattern that has provided me more gains than the low effort it took to implement:

Mail addressed directly to me, where my email address is explicitly in the “To” line, is generally more important to me than email in which I am only in the “CC” line.  Similarly, email received as part of a distribution list, where I do not explicitly appear in either “To” or “CC”, is generally of lower importance.

<

p>So, I have implemented a very simple set of filters to capitalize on this pattern.  Note that I have done this in the past with Thunderbird, Evolution, Outlook, and most recently with Zimbra.

  • Email where I am in the “To” field and the sender is one of a very specific set of VIPs (such as my wife or boss) gets highlighted a very bright color, like Yellow or Light Green
  • Email where I am in the “To” field gets highlighted a bright color, like Red or Blue
  • Email where I am in the “CC” field gets highlighted a lesser color, generally a pastel
  • Email where I am in neither the “To” nor the “CC” gets reduced color, such as light gray.

<

p>At a glance, this helps me determine what I should look at immediately, versus what can wait till later and doesn’t need to distract me now. YMMV, but I figured I would share.

One of those “D’oh” moments: chown .*

~ Matt Smith ~ 1 Comment

UPDATED: Repair process below

Want to change the ownership of all files in a directory to a user named ‘foo’?  Think this is a good way to do it?

chown -R foo * .*

Yeah, don’t do that. In one of those awesomely awful “D’oh” moments, I did that.  Remember: “.*” matches “..”.  So that will traverse up one level, and then recursively back down.

And of course …. I ran this in /mnt .   It took me about 5 seconds to realize what I had just done, before hitting ^c.  Yeah, my system is b0rked. 🙁

Resolution provided by Simon Sekidde at Red Hat:

On Red Hat Enterprise Linux (and derivatives), there is an easy way to re-initialize the ownership and permissions of RPM-installed files:

for i in `rpm -qa`; do  rpm --setugids $i;  rpm --setperms $i; done

Make sure to use –setugids before –setperms; if the order is reversed, changing the ownership with –setugids will reset any suid/sgid bits set by –setperms.