Incoming mail problem
Mar 11 08 2:04 am
Hi everyone!
I recently installed WinGate proxy in my office in substitution of WinProxy, and after installing and configuring WinGate, I am able to use all the services excepting the mail service. The problem is that I can send mail but can't receive incoming messages.
Reading the mail server configuration PDF, I saw that my office network matches scenario 2 (we have a 3rd party mail server called MailEnable) and followed the instructions step by step to make the mail server go through WinGate.
Testing how the mail service works, I found that:
-If I send a message (using Outlook) to any address outside our domain (i.e. gmail), it works (the message is sent).
-If I send a message from our domain to another address in our domain, it also works (the message is sent and received).
-If I send a message from the outside (i.e. gmail) to my domain, it doesn't work (the message is not received).
I really don't know what happens, because I think I have configured everything correctly. Any ideas? If you need more info, feel free to ask.
Thanks in advance!
I recently installed WinGate proxy in my office in substitution of WinProxy, and after installing and configuring WinGate, I am able to use all the services excepting the mail service. The problem is that I can send mail but can't receive incoming messages.
Reading the mail server configuration PDF, I saw that my office network matches scenario 2 (we have a 3rd party mail server called MailEnable) and followed the instructions step by step to make the mail server go through WinGate.
Testing how the mail service works, I found that:
-If I send a message (using Outlook) to any address outside our domain (i.e. gmail), it works (the message is sent).
-If I send a message from our domain to another address in our domain, it also works (the message is sent and received).
-If I send a message from the outside (i.e. gmail) to my domain, it doesn't work (the message is not received).
I really don't know what happens, because I think I have configured everything correctly. Any ideas? If you need more info, feel free to ask.
Thanks in advance!
Last edited by JaFer on Mar 14 08 11:02 pm, edited 1 time in total.
Mar 13 08 4:58 am
Sorry to hijack your post, but I am having the same issue.
Installed wingate on a SBS2003 server, using NAT, everything works fine I can send emails to the outside, but can't receive.
Sending and receiving from inside the domain also works fine.
Please help!
Installed wingate on a SBS2003 server, using NAT, everything works fine I can send emails to the outside, but can't receive.
Sending and receiving from inside the domain also works fine.
Please help!
Mar 13 08 4:12 pm
You're 99.9% of the way there JaFer.
When using Scenario 2 of the "Using WinGate 6 Email" white paper, the SMTP server is responsible for delivering any emails it receives for your domain name to your MailEnable server.
By default, WinGate will not be listening for SMTP Traffic from the Internet, so it will not be receiving any emails that it can forward on to your internal mail server. You will need to tell the SMTP Server in WinGate to start listening for SMTP traffic from the Internet so that it will start doing it's job.
To make the WinGate listen for incoming emails from the Internet, the SMTP Server must be bound to the External network adaptor of the WinGate computer. I have included a guide on how to do this below.
1. Gatekeeper -> System tab -> SMTP Server -> Bindings
2. Click 'Add' to create a new Binding Policy
3. Select 'Any External Adaptor', or if you have multiple external adaptors and only want to listen for emails on one, select that adaptor
4. Click OK to make the Binding Policy
5. Click Apply to finalise the change
6. Make sure the External network adaptor has been added to the list of bound adaptors.
When using Scenario 2 of the "Using WinGate 6 Email" white paper, the SMTP server is responsible for delivering any emails it receives for your domain name to your MailEnable server.
By default, WinGate will not be listening for SMTP Traffic from the Internet, so it will not be receiving any emails that it can forward on to your internal mail server. You will need to tell the SMTP Server in WinGate to start listening for SMTP traffic from the Internet so that it will start doing it's job.
To make the WinGate listen for incoming emails from the Internet, the SMTP Server must be bound to the External network adaptor of the WinGate computer. I have included a guide on how to do this below.
1. Gatekeeper -> System tab -> SMTP Server -> Bindings
2. Click 'Add' to create a new Binding Policy
3. Select 'Any External Adaptor', or if you have multiple external adaptors and only want to listen for emails on one, select that adaptor
4. Click OK to make the Binding Policy
5. Click Apply to finalise the change
6. Make sure the External network adaptor has been added to the list of bound adaptors.
Mar 14 08 11:23 pm
I forgot to say in my previous post (or didn't say it clearly) that I configured WinGate according to the second option in scenario 2, which is: "If it would be preferable to have the 3rd party mail server simply ‘pass through’ WinGate..." (at page 35 in the white paper).
Using that configuration, POP3 and SMTP servers are disabled, so there are no binding problems. And obiously, the "incoming mail" issue is still there. Any other ideas?
Sorry for not being clear in my previous post and thanks for your reply.
Using that configuration, POP3 and SMTP servers are disabled, so there are no binding problems. And obiously, the "incoming mail" issue is still there. Any other ideas?
Sorry for not being clear in my previous post and thanks for your reply.