I'm running James 2.1.3 on XP and recently found some slowness on my PC that made me investigate. I don't know if this one thign I found caused my slowness, but I definitely don't think its good.
I found 153 open connections to my ISP's POP3 server. I'm running POP3Fetcher to pull down my e-mail for my old address as I'm transitioning to my new address at my domain (Which James is set up for). Looking in my log for the pop3 fetcher, I saw lots of lines about null messages. Using my ISPs web mail interface, I saw roughly 200 messages in my inbox that were from some time ago (some a couple of months old, when I started using James). I suspect something in one of those messages is breaking the POP3Fetcher and leaving it in a state where its not closing the connection (and despite popular belief, a Windows OS can stay up for a very long time!) Anyone else experience this? I realize POP3Fetcher is experimental, but this may be worth fixing. Regards, Brian. -- Help free our mailboxes. Include http://wecanstopspam.org in your signature. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
