No you should let it go. It's a pretty good news letter. Check out the
site and see what I mean, they basically talk about how screwed up some
company policies are and they have good stories on them. Thus the name
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Beh
Oh here's an interesting story about Robin Wolaner who worked for Cnet
and blocked access to f^uckedcompany.com. She was harassed and
humiliated by the people that checked out that site that she actually
quit her job
http://www.internalmemos.com/memos/memodetails.php?memo_id=7
http://www.internalm
One could argue that the newsletter is similar to subscribing to the WSJ
newsletter or a Motley Fool newsletter, since it provides insight into
companies which may be in your industry or which the user might be invested.
I browse the f-kedcompany.com website once a month at least to see what's
goin
Do you tell your employees to not curse while talking on the phone?
Drew Nicholson
Technical Writer
Network Engineer
LAN Manager
RapidApp
312-372-7188 (work)
312-543-0008 (cell)
Born To Edit
-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2
:33 AM
To: Exchange Discussions
Subject: Re: Blocking a newsletter
One could argue that the newsletter is similar to subscribing to the WSJ
newsletter or a Motley Fool newsletter, since it provides insight into
companies which may be in your industry or which the user might be
invested. I browse the
I agree. The only thing that hurts them is the name.
-Original Message-
From: Chris Scharff [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 8:33 AM
To: Exchange Discussions
Subject: Re: Blocking a newsletter
One could argue that the newsletter is similar to subscribing to
I agree but what about when the mail contains phrases like @ss-raped? Sure
it is a fine line.
Jim
-Original Message-
From: Drew Nicholson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 11:53 AM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
Do you tell
lf Of James Liddil
Sent: Wednesday, December 18, 2002 9:24 AM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
I agree but what about when the mail contains phrases like @ss-raped?
Sure it is a fine line.
Jim
-Original Message-
From: Drew Nicholson [mailto:[EMAIL PROTECTED]]
Check with HR. Put the ball in their court.
- Original Message -
From: "James Liddil" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Wednesday, December 18, 2002 12:23 PM
Subject: RE: Blocking a newsletter
I agree but what abou
EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 11:24 AM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
I agree but what about when the mail contains phrases like @ss-raped?
Sure it is a fine line.
Jim
-Original Message-
From: Drew Nicholson [mailto:[EMAIL PROTECTED]]
sday, December 18, 2002 09:43
Subject: RE: Blocking a newsletter
If they forward that email, and someone gets offended, it's a different
issue. But simply subscribing to it?
Drew Nicholson
Technical Writer
Network Engineer
LAN Manager
RapidApp
312-372-7188 (work)
312-543-0008 (cell)
Born
iddil [mailto:[EMAIL PROTECTED]]
Posted At: Wednesday, December 18, 2002 11:24 AM
Posted To: MSExchange Mailing List
Conversation: Blocking a newsletter
Subject: RE: Blocking a newsletter
I agree but what about when the mail contains phrases like @ss-raped? Sure
it is a fine line.
Jim
-Ori
>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
Forums.somethingawful.com come join us in FYAD..you'll love it there
:)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Rachel Pickens
Sent: Wednesday, December 18, 2002 11:09 AM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
>
-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 do
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 o
ember --
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 vi
Damn liberals keep screwing everything up
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Alexander Wall
Sent: Wednesday, December 18, 2002 11:54 AM
To: Exchange Discussions
Subject: Re: Blocking a newsletter
Well, that opens an entirely different
block it all...
-Original Message-
From: Christopher Hummert [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 2:58 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
Damn liberals keep screwing everything up
-Original Message-
From: [EMAIL PROTECTED
Damn Hummerts keep posting.
- Original Message -
From: "Christopher Hummert" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Wednesday, December 18, 2002 2:58 PM
Subject: RE: Blocking a newsletter
Damn liberals keep screwing ever
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
actions.
Gèoff...
-Original Message-
From: Alexander Wall [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 2:54 PM
To: Exchange Discussions
Subject: Re: Blocking a newsletter
Well, that opens an entirely different discussion. We drafted a consent
form that every emp
27;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 mo
I hate those guys
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Andy David
Sent: Wednesday, December 18, 2002 12:00 PM
To: Exchange Discussions
Subject: Re: Blocking a newsletter
Damn Hummerts keep posting.
- Original Message -
From
Gèoff...
-Original Message-
From: Depp, Dennis M. [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 3:02 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
While I agree the mail belongs to the company and the company has the right
to review anyone's email, has that resp
My gut reaction would be to take a hit of diet pepsi and ask myself why I felt so
threatened by this newsletter. If i still felt this way after i finished the whole
can, I'd probably go and ask them why, and if it were not for work purposes I'd ask
them to consider unsubbing.
But then by th
l)
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
--Original Message-
> From: Dale Geoffrey Edwards [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 2:48 PM
> To: Exchange Discussions
> Subject: RE: Blocking a newsletter
>
>
> Rachel: As an Exchange Administrator, he has the right to
> browse ANYONE'
8, 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 Write
[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 3:10 PM
> To: Exchange Discussions
> Subject: RE: Blocking a newsletter
>
>
> My gut reaction would be to take a hit of diet pepsi and ask
> myself why I felt so threatened by this newsletter. If i
> still felt this way
18, 2002 3:02 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
While I agree the mail belongs to the company and the company has the
right
to review anyone's email, has that responsiblitiy been passed down
simply
because I am an Exchange Administrator? I don't think so.
[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,
]
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 N
18, 2002 2:37 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
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 confidential
y, 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:[EMA
We bounce it back to them
and tell them they need managerial approval.
Gèoff...
-Original Message-
From: Drew Nicholson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 3:46 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
Um, no. Even though I am the
dwards [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 2:52 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
That's what I said in the beginning. You may the "rights" to do it, but that doesn't
mean you should. I don't go anywhere that a ma
sions
Subject: RE: Blocking a newsletter
I think you need to check the Dictionary.com site again.
<>
That implies not only the ability, but the sanction.
Drew Nicholson
Technical Writer
Network Engineer
LAN Manager
RapidApp
312-372-7188 (work)
312-543-0008 (cell)
Born To Edit
-Origi
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
Sub
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&#
phone but
graver since you have the control you do when managing the systems.
-Original Message-
From: Chris Scharff [mailto:[EMAIL PROTECTED]]
Sent: 18. joulukuuta 2002 23:21
To: Exchange Discussions
Subject: Re: Blocking a newsletter
IANAL, but I do know that the legality of accessing mail
]] 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 n
--
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
t: Wednesday, December 18, 2002 3:37 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
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 vi
"Now come on Father, what would you say to a nice cup of tea?"
-Original Message-
From: Great Cthulhu Jones [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 8:28 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
If you don't like it, then do l
Of James Liddil
Sent: Wednesday, December 18, 2002 12:21 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
Management knows I run scanmail with emanager and have the filter to
catch profanity among other things. When a message meets the criteria
it is archived and I look at the message
2002 1:37 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
I disagree with you. As an Exchange Administrator, granted specific
permissions, I have that ability.
I for one, NEVER access users' mailboxes. Ever. Should there be such a
need the manager of the person requesting a
ECTED]] On Behalf Of James Liddil
Sent: Wednesday, December 18, 2002 2: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 s
AIL PROTECTED]]
Sent: Wednesday, December 18, 2002 3:02 PM
To: Exchange Discussions
Subject: RE: Blocking a newsletter
While I agree the mail belongs to the company and the company has the
right to review anyone's email, has that responsiblitiy been passed down
simply because I am an Exchange
If it isn't in writing, I don't go there. If there's a lawsuit, I have that
permission in writing.
-Original Message-
From: Dale Geoffrey Edwards [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 2:48 PM
To: Exchange Discussions
Subject: RE: Blocking a news
50 matches
Mail list logo
