NEW YORK, 4:21 PM, THU MAY 22 | 56 POSTS IN THE LAST 24 HOURS | tips@gawker.com | SUBMIT A TIP | RSS

Ironic PR Disaster Strikes PR Magazine

PRWissue.jpegPRWeek spends a lot of time telling publicists how to do their jobs. Embarrassing, then, that last week the magazine bombarded thousands in their database with unwanted emails. Bonus feature: the message included the names and passwords of other people! All that time the staff spends writing features about crisis communications is coming in handy now. After the jump, PRWeek editor Julia Hood's apology to readers who are, in the words of a tipster, "piiiissed." [Disclosure: I formerly worked at PRW][PRWeek]

From the desk of Julia Hood, Editor-in-Chief of PRWeek

Date: February 4, 2008

I am writing to personally apologize for the error that caused your PRWeekjobs.com user name and password information to be distributed externally. I am also sorry if you received our job site email multiple times and that your email address was cc'd to other respondents.

I want to provide you with background on how this happened; what we have been doing to fix the situation; and what action you may be able to take to limit the extent of this inconvenience. The error originated with our vendor, Adicio, via a technical error, during their work on our behalf with an automated software migration package. When this problem was discovered, just minutes after the project began, Adicio immediately took mitigating action ceasing the transmission and disabling all user names and passwords. This problem impacted a limited portion of registrants to a PRWeek service. Adicio's explanation and apology is currently on our website:
http://www.prweekus.com/Adicio -issues-formal-apology-regardi ng-PRWeek-e-mail-problem /article/104713/

Unfortunately, I know that some of you may still be receiving emails. If that is the case, it is likely that these emails are being bottlenecked at your ISP. Please refer to the list below for obtaining advice on how to stop this from happening in your individual system.

- Contact your ISP and request they remove the spam emails
awaiting delivery from you (the top ISP contact details
are included below). PRWeek is also alerting ISPs of this
problem
- If your company owns an email server, contact your Systems
Administrator and request that they block the specific
email address in its Spam filter
- Block the senders email address on your system
- For peace of mind, change the passwords for other online
services you use for which you have been using the same
password

I know you have been inconvenienced and, even more importantly, are concerned about the privacy of your information. This error may have also shaken your confidence in working and engaging with PRWeek. Again, I offer my sincere apology, as well as my promise to you that we will do everything possible to ensure that this never happens again. I realize it will take time for us to earn your trust again, but we value our dialogue with you and hope it will continue and that we can move past this very unfortunate occurrence.

Please feel free to contact me directly with further questions and concerns. My information is at the bottom of this email.

3:55 PM on Mon Feb 4 2008
By Hamilton Nolan
2,285 views
14 comments

Comments

  • "I am sorry if you received our...email multiple times. Now here's another email." What a mess.

  • Shit. I was hoping it would tell me where I could get some cheap Hoodia.

  • Too bad it was Julia Hood and not Julia Allison.

  • Image of Sarcastro Sarcastro at 04:14 PM on 02/04/08 *

    See what happens when Puerto Ricans get their own periodical.

  • "My information is at the bottom of this email."

    And your information is now in the inbox of 10,000 strangers.

  • In plainspeak:

    Date: February 4, 2008

    Just wanted to say sorry about that massive fuckup. you know what happened; no need to go through that shit again.

    Here's what went down, what we're doing to fix it, and a brief "how-to" on to fix the fuckup that we did in the first place.

    Actually, it wasn't us: it was the IT nerds we hired to do this shit. They fucked up, BADLY as it turns out, but won't be fired. They have kids to feed! Besides, they did something to make it all better. Don't worry about this part - it's all good.

    Except for some loose emails. Just delete them, hmmmkay? Or get your IT guy to fix it for you. Trust us - he'll love the extra work.

    We know this shit ain't right. And, like you know how you won't stick your fingers into a payphone coin return slot because someone might have stuck a dirty needle in there to give you AIDS? You probably trust us just as much now. Look, here's two dollars, get yourself a copy of PR Week at Hotalings, and stop crying. Or I'm gonna have my friend Tony do the beatdown on yo' ass.

    Capiche? Don't call me.

  • There's something strangely cheering about this story, especially for people who didn't get the emails.

  • I think it's nice that Puerto Ricans finally have their own weekly paper.

  • The editor in chief; does not know how to use; semi-colons correctly.

  • Rule one is that PR and comm people have no idea how to communicate with other comm people.

    My workplace being example #1.

  • From the desk of the Editor-in-Chief of Cat Fancy,

    I am writing to personally apologize for the error that caused your beloved pet to ingest toxic residues from our sample of eau de toilet bowl cat perfume. I am also sorry if your treasured and companion died and excruciating, protracted and leaky death as a result. I realize it will take time for us to earn your trust again, but we value our dialogue with you and hope it will continue and that we can move past this very unfortunate occurrence.

  • Why does the; editor-in-chief of a magazine; use semi-colons incorrectly?

  • This makes so much sense. The account usually reserved for passwords for smut sites and online subscriptions has recently exploded with press releases.

  • ...and I thought they just really, really, REALLY wanted me to take that job. Shoot!

Start a discussion:

Reply by Email

Login with your username and password below. Or comment on this post via email.