Industry


Ads by TechWords

See your link here


Sharky's picture
Sharky

Shark Tank

Shark Tank: Say, that might work!

This pilot fish is a third-tier support tech for a big retailer in the U.K. "I received a call in my queue asking me to blacklist an e-mail address," says fish. "Reason: The e-mailer was a former employee who was mailing his former colleagues with abusive material."

Fish ponders the request, then calls the HR department staffer who sent the request.

 I could block e-mail from that address, fish says. But the abusing e-mail is being sent through Hotmail. If fish bans that address, the former employee can just get a new one.

If that continued, fish could end up banning all Hotmail accounts.

And then the abusive e-mailer could do the same thing at Gmail, and then Yahoo, and then every other free e-mail provider.

Reports fish, "I said to the HR person, 'Why don't you just write to him telling him to stop mailing the staff and that if he didn't stop you'd take action?'

"He thought for a moment, and then said, 'That's an idea.'

"I closed the call, citing 'nontechnical solution implemented.'"

Submit your own true tales of IT life to sharky@computerworld.com. If Sharky uses it, you'll snag a snazzy Shark Tank shirt! You can also add comments by using the form at the bottom of this page.

See more Shark Tank stories at the Sharkives.

Join Shark Bait

Now you can post your own stories of IT ridiculousness. Join Shark Bait today and vent your IT frustrations to people who've been there.
Go to the
Shark Bait homepage
or
Post a story now

What People Are Saying

Shamus - you probably mean

Shamus - you probably mean "morale"

Joe: We almost become

Joe: We almost become overzealous in our attempts to mock the standard user community...This HR staffer (who it would seem has the correct authority to make this request) had a simple request.

--------------------------------------------

Yes it is a simple request, but even simple requests take time. This one would have been repeated not only for the current former employee but any future employees with a like mind. Then it would become expected for anyone any user did not want e-mail from ie: spammers, etc.

We had the same situation

We had the same situation here, an ex-employee sending abusive e-mail to current staff, but HR didn't ask us to block the sender's e-mail. They asked us to capture it, because he kept sending it after being asked to stop. It was potential evidence if legal action ensued. We diverted all e-mail from the abuser's address to a separate mailbox, not the original recipients. He could have gotten himself a different sending address, but he didn't. The evidence kept piling up.

I agree with loadster, an

I agree with loadster, an email rule should have been created so that the emails went to the Legal dept for review and possible litigation/prosecution. The former employee has a problem and HR should have seeked legal counsel first, then HR and Legal could come to IT to assist.

FWIW, loadster's solution

FWIW, loadster's solution would not work in California. Note the case of Intel v Hamidi in which the CA Supreme court overturned a lower court decision and essentially said that since Intel's email was open to the Internet Hamidi's emails did not trespass nor did they any property.
In California at least, you'd need a technical solution as there is no legal remedy.

bad lawyers on intel's part.

bad lawyers on intel's part. They shouldn't have tried to prove damage or trespass. They should have found a telecom law about harassment or profanity they could prove. Just because the lawyers blew it in Never-Never land of the singular state of California, doesn't mean the rest of the country is brain-damaged in courts. Except in Texas.

I agree with Mike. The

I agree with Mike. The majority of change requests coming in the user is attempting to specify the technical solution to the problem, not stating what they really need.

While a technical solution would have worked, it wouldn't have solved the problem of abuse from a former employee. The HR person wanted to stop the abuse, not necessarily add a blacklist rule.

Wow, talk about missing the

Wow, talk about missing the point. These blogs are becoming a cross between flame-mail and myspace.

The point was that an issue that was thought to be IT wasn't really, because of the scope of the actual request. It is very easy for a user to believe that any information transmitted across IT must therefore be within IT's domain, however it usually isn't. Like if your new car broke down you call DOT or NHTSB to get it fixed. NOT, call your dealer!

I feel that my job isn't so

I feel that my job isn't so much as to just fix the problem, but to also educate the user community. In this case, isn't it a matter of educating a user about SPAM and free e-mail accounts?

Poor Joe, should of stuck

Poor Joe, should of stuck with just hating comments!