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

cannot send mail out

Aug 04 04 11:32 pm

hi
i having a sending mail out problem. I already open the port 25 but still cant send my mail out.

I only manage to download my mail. The application that i using is Outlook

Aug 05 04 5:01 pm

Hi,

Which version of WinGate are you using? How have you configured your clients? Are you running WinGate's mail server, a third party mail server or connecting to an ISP for your email?

Thanks,

Matt

Aug 05 04 11:54 pm

i using version 6. I'm connection to an ISP for my email. I didnt use any mail server.

Boon

Aug 06 04 1:50 am

boon wrote:i using version 6. I'm connection to an ISP for my email. I didnt use any mail server.

Boon


Are you using the POP3 Proxy (recommended if you have AV plug-in) to download your mail from your ISP?

If you are your ISP's SMTP server may need Authentication, on the account properties in Outlook, press the More settings button, then select "Logon using" then use snter your account details your ISP requires for the account, (username and password). You can use "Use same settings as my incoming mail server" because those are the details needed for Wingate POP3 proxy.
Or the SMTP server might require you to authenticate with the POP3 server first, in that case use "logon to incoming mail server before sending mail".

Aug 06 04 5:09 am

I am having the same problem, but currently using version 5. I was using a router to access the internet, but some people were hogging up all the bandwidth and I decided to try this Wingate to find out who and take care of the problem.

However, I do not want to make changes to individual computers, and want them to continue checking their ISP email as usual. Since I installed Wingate, none of them can. I tried turning off SMTP and POP3 in the control panel with no luck. I changed one of them to SMTP to be the proxy server address with no luck. I tried setting up the domains in the email tab. I tried bindings, and local and gateway and a whole host of settings and nothing worked.

I just want them to be able to go about checking their email as usual. Can someone tell me how to set this up? You may have to be very specific, as I really feel like an idiot with this program. Browsing is working great by the way.

Thank you.

Aug 06 04 10:35 am

Hi,

I think a possible solution was posted already in this forum. It was suggested to install NAT on the Wingate server (is installed by default) and on the clients open the WGIC and add the e-mail program with Local Access. This disables the WGIC. In the Network settings of Windows on the client set the gateway to point to your Wingate server (e.g. 192.168.0.1).

This worked fine for me both for Pegasus Mail as WS_FTP.

Good luck.

Aug 06 04 11:37 am

WGIC? What is this?

I have all computers setup just like before with a router, except I took the router off and gave this computer the ip that the router had and installed wingate and internet works fine. I really want to avoid making any changes on client computers. They each are assigned an ip address and use this computer as a gateway and the isp dns settings.

I just want email to continue functioning normally with the isp as it always has without changing them. I don't have access to all computers all the time.

Aug 07 04 2:49 am

Hi,

WGIC is the Wingate Internet Client. You can use NAT without the WGIC (see the Wingate Help ) the way you describe your configuration.

Without the WGIC on your clients it should work without fail (See Help text on using NAT beneauth my text) . Sorry, I can't help you any further., you have a different setup.

Succes, Peter

Wingate Help:

Configuring Clients to use NAT

All that is needed for Clients to use NAT is:
The default gateway entry in the client machines network properties must be set to the private IP address of the WinGate server. This setting is part of TCP/IP properties and can be configured in several ways:
This can be done:

* Automatically with the WinGate DHCP server (recommended approach)
* Using another DHCP server running on your network, and setting the Gateway(Router), and DNS options to issue the private ip address of the WinGate Server (not recommended)
* Manually configure the network properties of the client machine.

Once the client has Gateway address set to point at the WinGate server, then they will be able to utilize NAT.
©2004 Qbik New Zealand Limited

Aug 07 04 8:48 pm

Hi

The most likely problem that causes issues when retrieving mail or delivering mail through WinGate to the Internet, is that connections may be intercepted by WinGate.

Normally this is what you want, but it can cause problems in some circumstances, for instance the POP3 Proxy can intercept connections, but cannot support the CAPA command, since it hasn't connected to a server to evaluate capabilities yet.

In such cases, if you are not using WinGate's POP3 proxy to scan incoming mail for viruses, we normally recommend simply not intercepting connections. This is controlled on the Sessions tab of the POP3 proxy server. Also check the POP3 server, as it has a similar capability.

For sending, check the SMTP server, whether it is intercepting connections or not as well.

If it is intercepting connections (normally much less of a problem than for POP3), then it will need to be configured to deliver mail.

Adrien
Post a reply