Sir, you are anti-joy.

[toxico.livejournal.com]

I just had a call from a customer using the content filtering feature of an SMTP scanner we produce to block emoticons.

He literally has rules in place to delete any messages that contain :-), :), :-*, ^.^, and so forth.

What a horrible and honestly worthless policy. To him I say this: t('.'t)

Comments

[inahandbasket]

wow, kirby giving the finger.
That's going in my personal collection. ^_^

[bamatone.livejournal.com]

Maaan, I so didn't get that before. Thanks for pointing it out, heh.

[aylinn.livejournal.com]

*blinks*

*stares at emoticon as the light dawns*

and here I was trying to parse it.

[prushrush.livejournal.com]

Wow. I can understand that on a professional level, since in my belief emoticons in professional emails are inappropriate, but personal email...wow.

[toxico.livejournal.com]

Unless his employees write all their emails like "OGM I AM LIEK TOTALLY IN DA MATRIX LAWLS :P ^_^ :)" and are unable to keep that shit out of professional emails, I can't see this having any utility.

I don't mean that certain character combinations are being stripped out - I mean the entire message goes away. No quarantined-for-later-retrieval, no banned content alert, nothing. Outbound AND inbound.

He wondered why he wasn't getting emails from us that we keep swearing we are sending him, and why replies won't reach us. Reason: Our support emails start with {[Case 012345]}; the replies will start with RE: {[Case 012345]};

He was blocking : { because it's a fucking frownie. DIE.

(comment replaced with more accurate details, sorry)

[bekscilla.livejournal.com]

Good luck to someone sending him a list of points, listed as 1), 2) up to 8) as well

[enik.livejournal.com]

At least he didn't put the @ in there. I actually had a customer do that and call be because all their email was being blocked. Course he felt REALLY stupid when I pointed out the problem.