Give it up man! Flagging your emails and using a lot of exclamation marks does not make you important!
That's what inbound processing (Outlook Inbox Assistant for example) is all about.
In my previous job, a few people got exceptions up front, such as my supervisors (and they were very judicious about flags and importances and such; I was fortunate). Everyone else got all flags and importances reset to "normal." I realized early on in this all the machinery for this (headers and such) was at the whim of the sender, and usually had absolutely nothing to do with my reality. After all, sure, it's a big pain point for you, but how the heck are you suppoed to know all of what's happening in the rest of my world? Oh, yeah, you're my supervisor, so you do know, so that's one big reason you get excepted.
supposed to be for, yes. Used that way? not so much.
It's gotten so bad that anything that doesn't have a subject line, has "(no subject)" as the subject line (as some mailers do), or one word subject lines go straight away into a file called "rejects" which doesn't get looked at unless or until absolutely everything else is taken care of.
I too share frustration expressed by others, in that you'll regularly see "question for you" (instead of, ohidunno, "question about that tool you used last I saw you"), or "calendar reminder" (about what???), again, by people who are often well-meaning but are just close to clueless. The same holds true, BTW, for Microsoft and, among other things, their monthly updates. After all, please...how tough can it be, instead of writing "security update" followed by some obscure knowledgebase reference, to write "security update addressing lack of BITS service parameter validation" or whatever it happens to be? Oh, right, we are Gates of Borg (well, these days, Ballmer of Borg, but the graphic doesn't look that way), you will be assimilated--they're drones instead of intelligent people over there.
I especially like Automachron when it's run under FireDaemon. This thing works wonderfully to turn just about any program into a service, including Automachron.
Don't wait for that clock virus. Become virtually immune, and run Linux instead:).
But seriously...the Unix NTP daemon has ways of controlling access based upon cryptographic keys and IP addresses. Basically, your clock shouldn't be altered unless you allow it. I'm going to make the broad, gaping assumption that the Win time sync is somehow loosely based on the reference implementation from UDel, but in actuality, I don't know for sure. I wouldn't sweat it if your clock is being regulated by Internet NTP servers.
Slashdot Mirror
That's what inbound processing (Outlook Inbox Assistant for example) is all about.
In my previous job, a few people got exceptions up front, such as my supervisors (and they were very judicious about flags and importances and such; I was fortunate). Everyone else got all flags and importances reset to "normal." I realized early on in this all the machinery for this (headers and such) was at the whim of the sender, and usually had absolutely nothing to do with my reality. After all, sure, it's a big pain point for you, but how the heck are you suppoed to know all of what's happening in the rest of my world? Oh, yeah, you're my supervisor, so you do know, so that's one big reason you get excepted.
supposed to be for, yes. Used that way? not so much.
It's gotten so bad that anything that doesn't have a subject line, has "(no subject)" as the subject line (as some mailers do), or one word subject lines go straight away into a file called "rejects" which doesn't get looked at unless or until absolutely everything else is taken care of.
I too share frustration expressed by others, in that you'll regularly see "question for you" (instead of, ohidunno, "question about that tool you used last I saw you"), or "calendar reminder" (about what???), again, by people who are often well-meaning but are just close to clueless. The same holds true, BTW, for Microsoft and, among other things, their monthly updates. After all, please...how tough can it be, instead of writing "security update" followed by some obscure knowledgebase reference, to write "security update addressing lack of BITS service parameter validation" or whatever it happens to be? Oh, right, we are Gates of Borg (well, these days, Ballmer of Borg, but the graphic doesn't look that way), you will be assimilated--they're drones instead of intelligent people over there.
I especially like Automachron when it's run under FireDaemon. This thing works wonderfully to turn just about any program into a service, including Automachron.
That is correct. Someone told this to me when talking about W2K. MS started using Kerberos for auth, so they needed accurate time dissemination.
It's amazing to me that they started using what everyone else has been using (DNS, Kerberos) instead of trying to make their own standards (WINS).
Don't wait for that clock virus. Become virtually immune, and run Linux instead :).
But seriously...the Unix NTP daemon has ways of controlling access based upon cryptographic keys and IP addresses. Basically, your clock shouldn't be altered unless you allow it. I'm going to make the broad, gaping assumption that the Win time sync is somehow loosely based on the reference implementation from UDel, but in actuality, I don't know for sure. I wouldn't sweat it if your clock is being regulated by Internet NTP servers.