Should wingate be behind firewall or use it's own

[bench]

I would like to give the mail function of wingate another try before looking for an alternative. During testing and actual implementation of the proxy, it was done while being behind a firewall(watchguard). I thought that maybe wingate should not be behind a firewall since it has one built in and I wanted to know how this firewall rates.

I would like to have the proxy server connected directly to the net with it's own IP and running the wingate firewall but I've never really been a big fan of software firewall's.

If anybody has setup wingate as a stand alone application like stated above, I would like to hear what your experience was. Did your proxy server get infected with viruses, bombarded with spam or did the wingate firewall and plugin antivirus work just right?

I would like to know how to properly implement wingate because there seems to be no definitive answer and the mail scenarios don't cover all the possible scenarios where things could go wrong. My main concern is why wingate rejects certain e-mails from users behind the proxy and won't deliver to hotmail, aol and other domains in mexico.

I would really appreciate anybody's input on this and I would very much appreciate it if you could mail me your configuration, if possible.

You can reach me at glujan@ddsvc.net.

Thanks.

[genie]

Wingate has its own firewall so you do not need to have Wingate machine behind 3rd party firewall.

[MattP]

Hi Bench,

We use only the WinGate firewall for our network protection here, and we've never had a break-in through it. Our forums were hacked a while ago but this was as a result of us not updating the phpBB, it had nothing to do with the WinGate firewall.

Regarding your mail problems, my last couple of responses to your forum posts have asked for your SMTP debug logs, do you have those? The SMTP log is usually pretty good at explaining why an email can't be delivered.

If you don't want to post them publicly you're welcome to create a support ticket and we can deal with this through the helpdesk.

Regards

Matt

[bench]

I will create a support ticket and send you the logs. I switched my client back to argosoft for now until I figure out how properly implement wingate.

[kgoodknecht]

I would like to give the mail function of wingate another try before looking for an alternative. During testing and actual implementation of the proxy, it was done while being behind a firewall(watchguard). I thought that maybe wingate should not be behind a firewall since it has one built in and I wanted to know how this firewall rates.

I would like to have the proxy server connected directly to the net with it's own IP and running the wingate firewall but I've never really been a big fan of software firewall's.

If anybody has setup wingate as a stand alone application like stated above, I would like to hear what your experience was. Did your proxy server get infected with viruses, bombarded with spam or did the wingate firewall and plugin antivirus work just right?

I would like to know how to properly implement wingate because there seems to be no definitive answer and the mail scenarios don't cover all the possible scenarios where things could go wrong. My main concern is why wingate rejects certain e-mails from users behind the proxy and won't deliver to hotmail, aol and other domains in mexico.

I would really appreciate anybody's input on this and I would very much appreciate it if you could mail me your configuration, if possible.

You can reach me at glujan@ddsvc.net.

Thanks.

All firewalls are software firewalls, it take software to make even a "hardware" firewall work.
It won't hurt to be behind two firewalls, if hackers get through one, they hit another, because of the first firewall the second is next to impossible to hack.

If your mail is being rejected by AOL and Hotmail it is likely to be any one or all of the following:
No PTR or mismatching PTR.
Either no SPF record or mail server is not connecting out on the same IP listed in the MX record for your domain.
Your Wingate's SMTP HELO name does not match the host name listed in the MX and PTR.
Your IP address is listed on a blacklist.

If the email address you gave is the domain Wingate sends/receives for it is as I say. You have no MX record, no PTR record, and no SPF record. You need these to send and receive email.