cage47
09-13-2002, 12:28 AM
(Whoops, posted this in Hardware first)
Has anyone else seen this? I was (highlight the word "WAS") using Mozilla 1.0 in Debian Woody to get my e-mail and also the newsreader to view the newsgroups. However there is a glitch, or more a conflicting feature. The outgoing smtp server setup requests the port for the outgoing mail. Now the port for mail on my prodigy is 110 and the port for news is 119. In Mozilla 0.9.7 in Mandrake there was just the smtp.prodigy.net entry that was needed. Since it was together with the incoming server setup. But now it has an entry of it's own. But before it wasn't necessary to enter the port. So now if I leave the port empty it sends my mail fine but newsgroup posts don't go out (receiving is perfectly fine). But if I put the 119 in the port box newsgroup posts go out but e-mails don't. I've since loaded knode and am getting my newsgroups through it (actually it looks better anyhow) but has anyone else experienced this? Is this something I should take up with mozilla's developers or has it been addressed already? Doesn't really bother me since I've worked around it.
Has anyone else seen this? I was (highlight the word "WAS") using Mozilla 1.0 in Debian Woody to get my e-mail and also the newsreader to view the newsgroups. However there is a glitch, or more a conflicting feature. The outgoing smtp server setup requests the port for the outgoing mail. Now the port for mail on my prodigy is 110 and the port for news is 119. In Mozilla 0.9.7 in Mandrake there was just the smtp.prodigy.net entry that was needed. Since it was together with the incoming server setup. But now it has an entry of it's own. But before it wasn't necessary to enter the port. So now if I leave the port empty it sends my mail fine but newsgroup posts don't go out (receiving is perfectly fine). But if I put the 119 in the port box newsgroup posts go out but e-mails don't. I've since loaded knode and am getting my newsgroups through it (actually it looks better anyhow) but has anyone else experienced this? Is this something I should take up with mozilla's developers or has it been addressed already? Doesn't really bother me since I've worked around it.