OK, I follow you. As far as #1, don't worry -- I'm well aware of these comical "patches" that people expect me to believe are from Microsoft. One of the probelsm I was having with fetchPOP was that these messages were getting stuck in my POP3 box. At ~150kb each, the 100 or so I get a day would eat up 15MB of space on my ISP account very quickly! I needed them t be dopwnloaded just to free up that space. But I would certainly not open one of these.
#2, perhaps I will turn on the higher-detail logging to see what this is. I'm not at all surprised that these bastards are using not just bogus addresses, but malformed ones. But I'd still rather something happen with these rather than staying in my ISP (See #1 above). I'm just not sure I'm willing to say "delete" them until I'm confident that no legitmate e-mail that I'd actually want to receive would have such a malformed address. #3, Thank you for clearing that up! Regards, Brian. -----Original Message----- From: Steve Brewin [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2003 4:56 AM To: 'James Users List' Subject: RE: Spoke too soon? Fetchmail problem Brian J. Sayatovic wrote: > This is the message I'm gettign in fetchmail. Perhaps this is what > was a bit uglier in fetchPOP? > > 25/09/03 23:09:42 ERROR fetchmail.one.net: one.net Message could not > be processed due to an error parsing the addresses. Subject: Newest > Net Security Patch From: Microsoft Corporation Internet Security > Section <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] A few things to note. 1) This mail is almost certainly a Trojan Horse as Microsoft do not send out patches by email. See http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/ policy/swdist.asp. I would recommend you DO NOT open it. 2) The parse error occurs when any of the addresses in the mail are malformed. You could set the logging level to debug so that the ParseException is recorded. If your ISP supports browsing mail (WebMail), you could examine the mail's headers to confirm that it is in error. 3) fetchmail will have assigned this mail a status of undeliverable and processed message according to the settings of the <undeliverable> tag in the config. It was NOT delivered. > 25/09/03 23:09:42 INFO fetchmail.one.net: Attempting delivery of > message with id. <[EMAIL PROTECTED]> > 25/09/03 23:09:42 INFO fetchmail.one.net: Ignoring recipient > header. Using > configured recipient as new envelope recipient - [EMAIL PROTECTED] These are related to the next fetched message, which was delivered correctly. > Obviously, I don't care that the recipient parsing is failign since > I've configured a recipient to be used regardless. As explained above, mail will be treated as undeliverable if any of the addresses fail to parse. The value of ignorercpt-header= does not affect this. > Should I be worried for any reason? About fetchmail no, about the contents of the failing mail, yes. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
