I can never find this info when I need it, and I’m terrible at remembering numbers so I decided to post it here for everybody’s edification. Incandescent bulbs are going away. Many governments are prohibiting their manufacture, so it’s only a matter of time. Replacement choices are either CF (compact fluorescent) or LED. These bulbs have a light output rated in Lumens, so it’s good to know what the Lumen equivalent is if you are replacing a 60W incandescent bulb and want the same amount of light.
- 40-watt incandescent bulb = 450 lumens
- 60-watt incandescent bulb = 800 lumens
- 100-watt incandescent bulb = 1600 lumens
Many CF bulbs have a slow start-up time, so it can take up to 2 minutes for the bulb to reach full brightness. If this is undesirable, then opt for an LED bulb as they are instant-on. LED also is lower heat and has less power draw, but can be more expensive than CF bulbs.
The other wrinkle is color temperature. We’re all familiar with “cool white” or “warm white” bulbs, but translating that into LED or CF specs on the packaging can be daunting. Here’s a handy chart that shows the Kelvin temperatures and the common vernacular equivalents.
As you can see, a cool white bulb is around 4200K, so when shopping for a replacement for a 100W cool white incandescent, you would want to buy a 1600 lumen 4200K bulb.
If you are like me, your company email is full of spam from vendors even though you have a spam filter system in place. It’s difficult for spam systems to nail all of this because a lot of these emails are generated by conference attendance and other such things which makes it a bit of a gray area. It’s not blatant spam, but you didn’t ask for it either. So… what to do about this inbox which has important email from your colleagues buried in a morass of useless information?
I had the idea that I’d create a rule or rules that would take any incoming email which originated outside my company and move it into a different folder. Then I thought it would be good to further hone that filter to only move things that were from people who weren’t in my contacts list either. This should be simple, right? WRONG! Outlook doesn’t necessarily respond the way you think it will.
Let’s say that my company has “email@example.com” as our email domain setup. My first thought was to create a rule which looks for “mycorp.com” in the sender’s address field, and move everything EXCEPT that to another box. The trouble is, for local users, exchange stores the user’s name (an active directory OU object), not their email address. When you do a rule for mycorp.com you don’t get many hits. To make along story short, it took a lot of fiddling to figure this out. Let’s cut to the chase and I’ll tell you how I solved the problem!
I created a rule which looks for “@” in the sender’s address, and I had Outlook move those emails to the “non-corp” folder. That worked like a charm! Every externally generated email ended up in the “non-corp” folder. I then refined it a bit by adding “except” with “mycorp.com” in the sender’s address (to catch some internally generated emails which come from systems reporting status, not from real users), and I added “except if sender is in Contacts address book”.
Now, my inbox contains only emails from co-workers and people in my address book. I’m no longer missing important emails, and when I get time to go through the “non-corp” folder, it’s pretty quick to delete things because I know most of the stuff in there is trash (as far as I am concerned) so I don’t spend much time on it at all.
Some of the other folks in my company liked this idea but wanted the result to be the other way around. They wanted a folder for “mycorp” which got everything internal, and they wanted to leave all the external stuff in “inbox”. How do you do that? Create a rule which looks for “/ou” instead of “@”. This will match all internally generated emails and let you move them to your specified folder. If you wanted everything matching your contacts list to go in there too you would need to create a second rule to do that because Outlook doesn’t have a way to do “OR” processing. If you try to do both in one rule it applies “and” logic (moves emails matching /ou AND in “contacts” – which won’t match very many at all).