Simon, Thanks. I totally forgot to look at the headers for those fields. -----Original Message----- From: Simon Whale [mailto:s.whale@xxxxxxxxxxxxx] Sent: Monday, December 12, 2005 9:46 AM To: [ExchangeList] Subject: [exchangelist] RE: Incoming Email anomaly http://www.MSExchange.org/ Have a look at the headers was her email address in the BCC or the CC Simon ________________________________ From: Shawn Moua [mailto:smoua@xxxxxxxxxxxxxxx] Sent: 12 December 2005 17:44 To: [ExchangeList] Subject: [exchangelist] Incoming Email anomaly http://www.MSExchange.org/ What may be the problem besides an internal/external virus. The problem is with just this one particular user, she received two emails that were not directed to her but other coworkers. How is this possible...since the To... field does have the other coworkder's name? Any clues? Thanks, Shawn ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: s.whale@xxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to info@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: smoua@xxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to info@xxxxxxxxxxxxxx
