Welcome, Guest
Username Password: Remember me

SSL to gmail = socket error 10049
(1 viewing) (1) Guest
  • Page:
  • 1

TOPIC: SSL to gmail = socket error 10049

SSL to gmail = socket error 10049 1 year, 5 months ago #1397

  • Tordan
  • OFFLINE
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
I just installed the latest version of Pop Collector and am trying to download mail from a gmail account

when i use pop.gmail.com with SSL at port 995 i get :
Socket error: 10049 (Address is not available from the local machine)

Thanks!

Re:SSL to gmail = socket error 10049 1 year, 5 months ago #1398

  • Tordan
  • OFFLINE
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
I should add that this is a Windows 2003 SBS server with Service Pack 2

Re:SSL to gmail = socket error 10049 1 year, 5 months ago #1399

Could you enable debug logging and send me the log of this please?

POP Collector uses STunnel for SSL. It starts STunnel, and then connects to this via the localhost (i.e. 127.0.0.1) - STunnel then makes the connection to GMail and handles the encryption. That error seems to imply that connecting to 127.0.0.1 is for some reason blocked.

Another thing that may be worth checking is the port that is listed under the STunnel config, and that it doesn't conflict with any others locally.

Re:SSL to gmail = socket error 10049 1 year, 5 months ago #1400

  • Tordan
  • OFFLINE
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
hmmmm that would probably explain it. Being that this is an 2003 SBS server it is USING port 995 for it's own SSL service.

I might need to run this connector on a different machine.

Re:SSL to gmail = socket error 10049 1 year, 5 months ago #1401

It shouldn't matter if port 995 is being used. There is another setting just for STunnel. Port 995 is what is being connected to (i.e. at Google), but the source port used by STunnel can be anything, and is configurable from the POP Collector UI. By default it should be a high number, you could try changing this.

Re:SSL to gmail = socket error 10049 1 year, 5 months ago #1402

  • Tordan
  • OFFLINE
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
hmmmmm, ok so i uninstalled it from my server and put it on a Windows 7 workstation, I installed rktools bits and turned off the firewall and told my servers smtp server to allow relay from this machine now when i run it with SSL it opens the socket and just does nothing...

I should also mention that i have this connector working nicely at a different site, but they don't use gmail and don't need ssl...

20/08/2010 14:03:35 POP Collector 1.4.3 initialising
20/08/2010 14:03:35 Checking for POPCollector service
20/08/2010 14:03:35 Sending STOP to POPCollector service
20/08/2010 14:03:35 Creating user interface
20/08/2010 14:03:35 Init common controls
20/08/2010 14:03:35 Settings file being used is: C:\ProgramData\POP Collector\POPTransfer.ini
20/08/2010 14:03:35 Windows 2000 or above detected - service configuration enabled.
20/08/2010 14:03:35 POP Collector 1.4.3 started
20/08/2010 14:03:39 POP: ethan@foo.bar starting SSL, using local port 0
20/08/2010 14:03:39 POP: ethan@foo.bar opening connection to pop.gmail.com
20/08/2010 14:03:39 Winsock->Connect: Connecting to 127.0.0.1
20/08/2010 14:03:45 Startup delay finished... POP collection starting
20/08/2010 14:07:10 POP: patric@foo.bar starting SSL, using local port 0
20/08/2010 14:07:10 POP: patric@foo.bar opening connection to pop.gmail.com

Re:SSL to gmail = socket error 10049 1 year, 5 months ago #1403

  • Tordan
  • OFFLINE
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
ok, i have it working now. I had to download and install the latest version of STunnel, and it seems that after changing the STunnel port in Pop Collector, you have to restart the program. It is merrilly downloading now. Thanks!

Re:SSL to gmail = socket error 10049 1 year, 5 months ago #1404

Thanks for posting your method of getting it working.

From what I can see, the port was wrong in the logs - port 0 would not have worked, so that should have been changed. 0 should also not have been the default, so I will check and see what happens on a clean install. I think it was most likely the port number that fixed the issue, rather than the install of STunnel, but I will look into this too.
  • Page:
  • 1
Time to create page: 0.32 seconds
Copyright © 2009 www.cedit.biz. All rights reserved.