Gonna be a long day.

[toxico.livejournal.com]

Mail server backup failed last night. RAID array failed as well. Exchange log files are gone. There is no other backup.

...wait, what? Oh, you say the backup has never worked? And we couldn't be arsed to fix this slight conundrum.

I should point out that this isn't another entity; this is this company.

We have become the lusers I hate. As long as we don't try to shove the blame elsewhere I guess I can keep my mouth shut but the urge to tell the appropriate parties how fucking stupid they are is rising swiftly.

Sometimes it's not even the users it's the co-workers

[zhent.livejournal.com]

I'm a Tech Support desk team lead, so I get all of the odd-ball calls escalated to me every day. That and the stuff the agents don't know how to resolve or answer themselves...

Clueless end user calls us and reached a clueless phone agent:

Clueless user: Hi, I'm trying to email people outside of our organization and I'm getting bounce backs that the email can't be delivered, fix it.
Clueless agent: Let me put you on hold

Clueless agent comes and talks to me, where I explain how this works and that we need to know what else the bounce back message says. This is not enough information... If the recipient is not with our company, then I need to know which server is rejecting the message and why. Is it us, is it the other end? Do we know?

The agent then IM's me the error message:

Clueless agent: A configuration error in the recipient's e-mail system prevented delivery of this message. Two recipients are configured with the same e-mail address. Contact your administrator.
Me: Is the recipient a part of our company?
Clueless agent: He's a director
Me: Is the recipient a part of our company?
Clueless agent: different organizations
Me: So not a part of our company?
Clueless agent: No, company B
Me: all we can do from our end is report the issue up, the problem is not on our side however, so we can't actually fix it
Me: This problem is on the other end

And this guy works for me...