Closed
Bug 161902
Opened 24 years ago
Closed 24 years ago
Could not connect to server xxx.xxx.xx; the connection was refused
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 121926
People
(Reporter: daniel.neves, Assigned: naving)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
BuildID: 2002052918
When I try to get email messages, this message appears:
"Could not connect to server xxx.xxx.xx; the connection was refused"
Most probably, the connection was refused because it didn't ask me the password
for this account, and I can't manage to find where this "option" should be
chosen (in the general Preferences or the "Account preferences"...
What I find really confusing is that I have been working perfectly with this
version of Mozilla (1.0) in my notebook (running SuSE 7.2) and now that I am
configuring it on another machine (running SuSE 8.0), it doesn't work!
A colleage of mine (also running SuSE 8.0) has also had the same problem... and
the only thing that we have in common is SuSE 8.0 (?!?)
Reproducible: Always
Steps to Reproduce:
1. Create mail account (through wizard)
2. Try to fetch mail (get messages) - DOESN'T ASK PASSWORD!
3. After a while, message appears: "Could not connect to server xxx.xxx.xx; the
connection was refused"
Actual Results: 3. After a while, message appears: "Could not connect to server
xxx.xxx.xx; the connection was refused"
And. obviously, the mail isn't fetched :(
Expected Results: errr... I don't understand why it doesn't ask me for the
password.
I would really like to use Mozilla has my email client, so I would appreciate if
you could give me feedback on this.
Thanks for your attention, guys! ;-)
Keep on the good work :D
Best regards,
Daniel Neves
Comment 1•24 years ago
|
||
Do you use a (socks) proxy? Please add the mailservers name to
Preferences->Advanced->Proxies->No Proxy for.
Comment 2•24 years ago
|
||
This is actually a dup of bug 121926.
Reporter,
This problem has been fixed. You have to download a newer build to get rid of
this problem.
*** This bug has been marked as a duplicate of 121926 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•