Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

KAV & WG6 & POP3 Proxying

Jul 31 04 3:31 pm

Hi,

I have just upgraded to WG6 and am using the POP3 Collection facility instead of each client downloading their own mail from our ISP's via the POP3 Proxy Service.

Are mail messages retrieved using the collection facility scanned by the KAV plugin?

Also in the General page of the POP3 Server properties page there is the option to allow pop3 proxying. Does this mean that when internal clients retrieve their mail from the Wingate POP3 Server that their messages are scanned by the KAV plugin in the POP3 Proxy Service even through they connect directly to the POP3 Server port?

Many thanks,

Mark Nixon

Jul 31 04 4:43 pm

Mail retrieved by POP3 collection in WinGate 6 go into the general delivery queue, which is scanned by anything you have set to scan the SMTP server mail.

The "allow POP3 proxy" option means that the server will accept (or intercept) a connection, if it is determined that the client wants to connect to another server (i.e. it was intercepted, or the client sends a user command of the form user#server), then if this option is selected, the POP3 server will hand over the session to the POP3 proxy server. This means you need to have a POP3 proxy set up as well. We normally have this run on a different port.

Now that you can specify intercepts to work on different ports, it is even easier to have through traffic scanned by the POP3 proxy, yet still use the POP3 server. Simply get the POP3 proxy to intercept connections on port 110, this will only intercept "through" connections, so the connections your clients make to WinGate's POP3 server will still be accepted by that server.

Hope this makes some sense!

Adrien

Jul 31 04 5:32 pm

Hi Adrian,

Thanks for the reply.

With regard to pop3 proxying. Can you please briefly explain the use of the Transparent Proxy section of the POP3 Server properties Sessions Window with respect to the use of same section in the POP3 Proxy server properties?

What I have done is to "Allow POP3 Proxying" on the POP3 server; remove the check against Transparent Proxy in the Sessions Window of the POP3 Server and add transparent redirect for port 110 in the Sessions window of the POP3 Proxy Server. Will this allow internal clients wanting to access an external POP3 server (on Port 110) to connect via the POP3 Proxy service?


Many thanks,

Mark Nixon
Post a reply