POP3 Proxy

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

POP3 Proxy

Postby mmakowski57 » Dec 08 03 8:55 pm

I have a customer who is using 5.2. They have Outlook installed on the Wingate machine and it is pointed to localhost so that Wingate will dial the connection and keep history for Outook sessions on the server. Since Outlook is pointed to localhost I had to insert the ISP server name and port number as Cascaded Proxy server on the Connections tab of the POP3 service. This works great on the server machine.

I am using NAT on other local workstations and am redirecting WGIC and ENS sessions through the POP3 proxy.

My problem is that that client machines are unable to connect to their corresponding POP3 servers because the Transaparent Redirection is forcing all clients to use the Cascaded Proxy Server that is set up for Outlook on the server. At least that is what appears to be the problem. When I switch the connection to "Directly" on the POP3 service the clients are able to connect to their POP3 providers. However, the server can no longer access it's POP3 provider through Wingate.

What is the suggested work around for this? Do I need to set up two POP3 proxies - one with TP on port 110 for the clients and another on port 8110 for the server?

Suggestions please.

Thank you.
mmakowski57
 
Posts: 16
Joined: Nov 07 03 7:43 pm
Location: Waco, TX

Postby pleye » Dec 12 03 6:15 am

I am also having a POP3 Proxy running on WinGate. On the WinGate machine itself, I am running a mail server (not WinGate's but an other software), which downloads it's mail from a 'Shared POP3' mailbox located on a remote mail server (like an ISP). In order to make sure that WinGate handles all the dialling, and also to see the traffic used by this local mail server, I direct the local POP3 download to the WinGate POP3 proxy. The port I am using here is 8110. This works fine, in the 'Connection' Tab of the POP3 proxy of WinGate, I leave the connection to 'Direct'.
You need to make sure that the software that runs on the WinGate machine, which needs to download POP3 mail, can specify where to get the mail, such as:
Server: localhost:8110
user: <username>#<remotePOP3server>

The local mail server also server mail via POP3 on the port 110.

When there are users on the LAN which need to download mail from a remote POP3 mail server, they could pass trough the WinGate's POP3 proxy as well. This will not work if these mail clients are Outlook Express, as that software cannot specify an other port (8110) and only works with 110. (At least the version that I use)
I found it easier to simply work with ENS and NAT. The go directly to the foreign POP3 server.

I hope this helps.
pleye
 
Posts: 2
Joined: Dec 12 03 6:00 am
Location: Dubai


Return to WinGate

Who is online

Users browsing this forum: No registered users and 5 guests

cron