Slashdot Mirror


E-Mail Snafu Sparks Spam Attack On Journalists

TFGeditor writes "According to an article at Editor & Publisher an e-mail mistake by the Casey Journalism Center at the University of Maryland wrongly invited hundreds of journalists nationwide to the university's prestigious 'Casey Medals' awards. The goof also launched a perpetual e-mail whirlwind as those who responded to the incorrect note unwittingly sent their feedback to everyone else on the recipient list. The e-mail was an electronic invitation to attend the organization's annual board meeting and awards lunch in Washington, D.C. on Aug, 8, according to Carrie Rowell, conference coordinator. She said it was meant only to reach the center's 11 board members, who are invited to the event where 18 journalists will be honored with the press-related awards. Rowell said she did not know how many people were affected, but did not dispute that it was likely hundreds."

1 of 153 comments (clear)

  1. Feature of Microsoft POP3 connector by pe1chl · · Score: 5, Informative

    There is an interesting feature in the Microsoft POP3 connector included with SBS 2003 that can also cause such a flurry of mails.

    When the original sender is stupid enough to include all addresses a mail is sent to in the To: header, and two or more readers of mail have their mailbox at an ISP and copy it to their Exchange server using the abovementioned Microsoft POP3 connector, mail can really start bouncing around.

    Why? Because of a bug in the Microsoft POP3 connector, mail that it retrieves from a POP3 box is sent to all addresses in the To: line. So the mailserver of every user of this crap will re-send a copy of the mail to all recepients, even those outside his or her own domain.
    When two or more users receive the message, they start sending more and more copies around.

    A while ago we received the same message from someone several thousand times. It took me a while to figure out what was really happening (we are not using those MS products ourselves), and the only way to kill it off was to reject all mail from the original sender.

    It seems that KB835734 offers a fix for this fatal bug, but MS does not consider it critical so I presume most admins have not applied it. Those SBS systems are a ticking bomb in the e-mail system.