From noreply at snf.stanford.edu Fri Jan 18 05:17:45 2008 From: noreply at snf.stanford.edu (The Post Office) Date: Fri, 18 Jan 2008 17:17:45 +0400 Subject: Delivery failed Message-ID: [??????b????????????J\??Q?'(?5?g8-???wF?j?>c?8&i$???E?_?rC$UC?|?G??(?4?????)#b????0 ????PO?3G?}????s?{??uj????? W???h0? ??N???*?Pckt$"????W?G?f:?4?n?? n,??*?;?f?;p?F?y?????~?(S^$?up??Ie??a^?W????????????G?W?*T?~? From noreply at snf.stanford.edu Fri Jan 25 05:00:16 2008 From: noreply at snf.stanford.edu (Automatic Email Delivery Software) Date: Fri, 25 Jan 2008 17:00:16 +0400 Subject: Mail System Error - Returned Mail Message-ID: Dear user of snf.stanford.edu, We have found that your account was used to send a huge amount of unsolicited commercial email messages during the last week. Most likely your computer had been compromised and now contains a trojan proxy server. We recommend you to follow the instruction in order to keep your computer safe. Sincerely yours, The snf.stanford.edu support team. -------------- next part -------------- A non-text attachment was scrubbed... Name: document.zip Type: application/octet-stream Size: 29108 bytes Desc: not available URL: From noreply at snf.stanford.edu Thu Jan 31 05:29:10 2008 From: noreply at snf.stanford.edu (Mail Delivery Subsystem) Date: Thu, 31 Jan 2008 17:29:10 +0400 Subject: Returned mail: see transcript for details Message-ID: The original message was received at Thu, 31 Jan 2008 17:29:10 +0400 from [23.106.41.128] ----- The following addresses had permanent fatal errors ----- sem4160 at snf.stanford.edu ----- Transcript of session follows ----- ... while talking to host snf.stanford.edu.: 554 5.0.0 Service unavailable; [156.207.163.134] blocked using relays.osirusoft.com Session aborted, reason: lost connection -------------- next part -------------- A non-text attachment was scrubbed... Name: attachment.pif Type: application/octet-stream Size: 28864 bytes Desc: not available URL: