I don't understand this comment, if K9 is the first interface with my
ISP server, the user name string tells K9 how to receive my mail?
Correct. What happens is that Netscape (or any mailer) fetches mail by
connecting to MAILSERVER on PORT and using the POP3 protocol to get your
mail. Using (e-mail address removed) as an example, Netscape would connect to
POP.BROADBAND.ROGERS.COM, and log in as "JOE" to get the mail. By default,
this all happens on TCP/IP port 110.
With K9 in place, Netscape never talks to POP.BROADBAND.ROGERS.COM directly.
Instead, it talks to K9, and K9 talks to the Rogers server. Other than
changing the server name, port, and username, Netscape sees no difference.
What you normally would have is
Netscape ---(110)---> POP.BROADBAND.ROGERS.COM ("Hi, I'm JOE, password XXX")
ROGERS --(Netscape)--> "Hi Joe, here's your mail"
With K9, you have
Netscape ---(9999)---> LOCALHOST ("Hi, I'm POP.BROADBAND.ROGERS.COM/110/JOE
password XXX")
K9 ---(110)----> POP.BROADBAND.ROGERS.COM ("Hi, I'm JOE, password XXX")
ROGERS --(K9)--> "Hi Joe, here's your mail"
K9 ---(Netscape)---> "Hi Joe, here's your mail; spam is marked with [spam]")
Since the POP3 protocol only allows for username and password, there has to
be a way to tell K9 which mail server and port to use. So Robin encodes it
into the username that you pass to K9, and K9 parses it.
I'm afraid that with respect to Netscape mail. But changing the server name
to just LOCALHOST and removing the port will help, but I don't know about
why you are limited in your field entry. Unfortunately, you are using
Netscape 4, which is fairly buggy, so it could well be that this is a bug
in the Netscape mailer.