mms4741: Your prefs-modifying technique is good. It seems there is some task on your machine that adjusts your POP server settings, probably every time you boot up. I'm not acquainted with such a problem, so I can't give you any specific pointers. It looks like you've stumped Fulvio as well. You may get more traction on a Windows support forum, since this misbehaviour affects Netscape, but doesn't seem to be caused by Netscape. Me, I know Mozilla browsers, but I'm only a third class Windows wizard.
mms4741 wrote:Here's a question: the server1.hostname is "127.0.0.1" regardless of the values in realhostname and realuserName. Is this normal?
127.0.0.1 is a special, reserved IP address that stands for the machine itself. With Netscape configured to look to this address for mail, Netscape will try to connect to a POP server on your machine.
This is a common way for third party software to insert itself between the Netscape mail client and your actual mail server. The third party software configures itself as a POP server, and sets Netscape to talk to it, rather than talking directly to your real mail server, Yahoo. Normally, that local server will transparently forward all traffic to your Yahoo POP server, and you wouldn't necessarily notice its interposition. The point of this exercise is to give this third party software a chance to have its way with your mail before you ever see it, before your mail client ever sees it. Hopefully it's doing something benign.
That's why I said earlier that this is a hallmark of spam filtering software. Clumsy filtering software that is a little too insistent about itself. I'm still suspicious of your security software McAfee. You say you haven't configured McAfee to filter your email, but it's possible that one component of McAfee continues to force Netscape server settings to refer to another McAfee component, a local McAfee spam filtering POP server, unaware that this POP server is inactive. You said this problem began suddenly without installing any new software. Is it possible that Netscape has been using 127.0.0.1 for a long time, and only recently has some local spam filter been inactivated?
I'd be inclined to check your Windows System Events Log for something suspicious at startup. Some application that sounds like a spam filter unable to get itself started, perhaps. Then I'd try making the prefs.js file read-only, and check that Events Log to see if that visibly upset whatever is modifying it. I'd try configuring McAfee to do nothing without asking, and see if that clears up the problem. (And that's the way I'd leave it, because I know people whose machines have been
hosed by automated McAfee security,
more than once.) Heck I'm just thrashing, here.
The possibility of malware can't be ignored. I know there are spyware applications that modify Explorer settings so that it uses their services when you browse. Adware that pointed to your own machine would be kind of dumb, but not all malware is written by geniuses. I recommend visiting a Windows support forum, a spyware removal forum, and McAfee technical support. I'm afraid I can't be any more specific.
Could I create a user.js file with lines specifying realhostname and realuserName, with the correct Yahoo settings? Would they override whatever settings are in prefs.js?
Exit Netscape, and make a copy of prefs.js named user.js. In user.js, delete everything but the troublesome line(s) (POP hostname and username, wasn't it?). Settings in user.js will override settings in prefs.js, so that will effectively freeze your server settings (and nothing else), and should override a gremlin that modifies only prefs.js. You could also make user.js read-only, if necessary. Obviously though, that doesn't solve the root of the problem.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20060305 Firefox/1.5