Yea but the question is the word "f^uck" really something that violates a company policy? I know here that in that case it wouldn't be. But if it was used in a violent or s^xual context then it would be.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of James Liddil Sent: Wednesday, December 18, 2002 1:23 PM To: Exchange Discussions Subject: RE: Blocking a newsletter Gee I never thought that what I thought was a simply query would go this far. As much as I think the f^ckedcompnay.com and internalmemos.com are eye opening one still needs to keep in mind that ones job is to enforce the policy. Management easily forgets what they agreed to until some employee gets bent about seeing a picture or reading something offensive. Then all hell breaks loose. And indeed as with any job there are ethics of behavior. Jim -----Original Message----- From: Dale Geoffrey Edwards [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 3:48 PM To: Exchange Discussions Subject: RE: Blocking a newsletter Like I said, in some companies they do, in others, they realize that the Mail Administrator has access to everything on the Network, and knows there has to be a certain amount of trust to go along with that title. As far as accessing other people's mailboxes, how do you troubleshoot what problems them might be having? We open Users' mailboxes that are having problems, inside out own mailbox and also log into their mailbox with their credentials 3 or 4 times a day. We then ask them to change their password. But all Mail Administrators know that if you know certain AD accounts and their passwords, you can get into anybody's mailbox. But does that mean you should? No. I have never just randomly selected someone's mailbox and opened it to see what the contents were. But I have worked with some people who have done it. There's where the trust has to come into play. I even showed management that they had logged into some very highly sensitive mailboxes. They then asked me to monitor their whereabouts on the Network and were eventually let go. Gèoff....... -----Original Message----- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 3:45 PM To: Exchange Discussions Subject: RE: Blocking a newsletter >>there is implicit trust That 'implicit trust' would have to be in writing in policy, or I am not touching it. William -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dale Geoffrey Edwards Sent: Wednesday, December 18, 2002 12:37 PM To: Exchange Discussions That's not true. As an Mail Administrator/Engineer, whatever you want to call yourself, there is implicit trust that you will not abuse your power to be able to view EVERYONE's email, due to the confidentiality of, oh say, the CEO or CFO. You have the power to view payroll and accounting documents. But as a Mail Administrator, it is a position of high sensitivity. Highly sensitive documents are passed through the mail system. You are expected not to sit down one afternoon and see what your boss or some other manager has been sending emails out about. It may not be written in some companies, but it is written in others. And I learned that the more you stay out of people's business, the more they will trust you not to look at sensitive documents. Gèoff....... -----Original Message----- From: Drew Nicholson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 3:22 PM To: Exchange Discussions Subject: RE: Blocking a newsletter that's not necessarily true. Unless he's been told to do it (which it appears he has), he doesn't have some sort of implicit right to do it. He has to be tasked with it. Drew Nicholson Technical Writer Network Engineer LAN Manager RapidApp 312-372-7188 (work) 312-543-0008 (cell) Born To Edit -----Original Message----- From: Dale Geoffrey Edwards [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 1:48 PM To: Exchange Discussions Subject: RE: Blocking a newsletter Rachel: As an Exchange Administrator, he has the right to browse ANYONE's mail. That mail belongs to the Company, so there shouldn't be anything in there that an enduser would be afraid of someone else seeing. Remember -- the email is on Company's equipment, software, etc. It is THEIRS. Gèoff....... -----Original Message----- From: Rachel Pickens [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 2:09 PM To: Exchange Discussions Subject: RE: Blocking a newsletter >From my point of view: If no one has asked you to monitor content and provided a written order, what are you doing browsing someone else' mail? Its bad form, and can get you fired. If you have been told to monitor then just enforce what is normally enforced. Don't ask the end user. They will talk you into an exception, and that one exception will become a chink in your armour that will be used and abused by everyone. I wasn't going to to register my opinion on this one, but I must tell you, taking advice from Hummert is a bad idea. Whatever you do, don't do it because Hummert says so. I (shudder) have seen the places Hummert considers normal and it makes me want to scrub off the top 2 layers of my skin. Sincerly, Rachel -----Original Message----- From: James Liddil [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 10:14 AM To: Exchange Discussions Subject: Blocking a newsletter Via Scanmail I find that a user is subscribed (or appears to be) to the f^ckedcompany.com newsletter. Besides the domain name there is other profanity in the newsletter. So do I follow company policy or let it slide? My gut reaction is to ask the person if they are subscribed and then politely ask them to unsubscribe and not have this kind of thing sent to a work address. Jim Liddil _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
