Closed Bug 140847 Opened 23 years ago Closed 23 years ago

Socks proxy causes POP3 and SMTP mail to fail

Categories

(SeaMonkey :: Download & File Handling, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: leshik__, Assigned: bugzilla)

Details

Could not connect to server ...;the connectionwas refused. For download mail and news I'm look this message look on 0.99;1.0rc relise if prefrences->advanced->Proxies set as "manual proxy configuration" ... if set as "Direct connectin" - Ok In the 0.97 - not this bug
Summary: Could not connect to server ...;the connectionwas refused. → Could not connect to server ...; the connection was refused
for me this problem occured since 0.9.9 so I stayed with 0.9.8 (where all works fine) since now where I find this problem report and a nicer solution than disabling all proxy support. I'm behind a masquerading server that works as a proxy based on squid (but I'm not sure wether all proxies are activated). When the Sock-proxy is activated, mozilla is'nt able to connect to the pop3 server nor is he able to connect to the SMTP server. The failing pop3 connection gives the mentioned error message but the SMTP connection has to manually canceled (waited for mor than a minute). Leaving the Socks line _and_ the port blank enables connection to pop3 and smtp again. If server address and/or port have some value (real address and real port) the connections failed. Hope this helps in examining the problem.
I was running 0.9.7, it worked fine, but when I tried RC1 it showed up for the first time, and it's the same with 1.0 when I enter an IP (e.g. 192.168.10.1) as the pop3 server name, it says "Could not connect to server ...;the connectionwas refused." this only occours when I use manual proxy settings, it works fine with direct connection workaround: define the IP as a host in your hosts-file, and enter the hostname as the pop3 server
I am having the same problem with version 1.1. Starting Mozilla does not start my Win XP Dial Up connection, and I still get the refusal to connect after starting the connection manuually and connecting to the internet. I also get failure to connect messages int he e-mail client, but the mail is downloaded anyway.
Same problem here.. Removing the socks entry for the proxy resolved it. Mozilla ver 1.0.1 OS: Red Hat linux 7.3
Hi there, Well I had this same problem, but I managed to get thinks working, finally ;-) (I was unable to download my POP3 e-mail, because it didn't ask me the password) I saw in previous sugestions that it was proposed to set "Direct Connection" in the Proxy configuration, but unfortunatly, I HAVE TO use a proxy connection to the internet. So, I left the proxy information and added my mailserver's address to the "No proxy for:" field in the Preferences->Advanced->Proxies and it worked just fine :D I was asked for my password and my email was downloaded. Hope I could help somebody with this. Best regards, Daniel Neves
QA Contact: sairuh → petersen
This bug is sort of hard to understand, though comment 1 helps. I would suggest that: 0) This bug is five or ten different bugs. It needs to be just one bug. The main one sounds like a SOCKS problem, so go with that. 1) Everybody look at bug 160629 to make sure that your problem isn't the same. 2) There have been some SOCKS fixes recently -- try downloading a recent nightly build and see if the problem still happens. 3) Could one of the commenters (or the reporter) please read the Bug Writing Guidelines at <http://www.mozilla.org/quality/bug-writing-guidelines.html> and then try using the guided form to report this bug again in a more clear fashion. The guided entry form can be found at <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided> Thanks for all of your help in testing Mozilla! -M
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Summary: Could not connect to server ...; the connection was refused → Socks proxy causes POP3 and SMTP mail to fail
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.