SMTP Bindings MIssing

[sudleyplace]

I just upgraded to 6.0.1 (from 5.2.3) and find that I can't sent email. That is, a client (192.168.0.4) on the LAN attempts to send email to the server (192.168.0.1) and is told that the SMTP server is unavailable or is refusing connections.

When I check the bindings in the "SMTP Proxy Server" service, I find that there are no bindings whereas there should be bindings to 192.168.0.1:25 as well as 127.0.0.1:25.

This works correctly with 5.2.3. What should happen is that WG should receive SMTP connection on one of the two above-mentioned IP:ports and then send it on to MDaemon on 127.0.0.1:8025 which processes the outbound email and queues it for later delivery (to 127.0.0.1:9025). This is supported by setting the General tab in this service to have outbound mail sent to 127.0.0.1:9025 and inbound mail via 127.0.0.1:8025.

Oddly enough, both "SMTP Proxy Server" and "SMTP Connection-specific Proxy" services have the same Binding Policy ("Bind to any IP address on any internal adapter" and "Bind only to 127.0.0.1 ..."). The former Service has no bindings listed in the Adapter/IP Address/... window (incorrect) and the latter has both 127.0.0.1 and 192.168.0.1 (correct).

Any help would be greatly appreciated.

[Pascal]

If I understand this setup correctly, you have two services listening on all available internal adapters on port 25 ?

Both services cannot bind to the same adapter on the same port. You'll need to alter the policies so only one service is listening on a specific adapter+port combination.

[sudleyplace]

If I understand this setup correctly, you have two services listening on all available internal adapters on port 25 ?

Both services cannot bind to the same adapter on the same port. You'll need to alter the policies so only one service is listening on a specific adapter+port combination.

No, the "SMTP Proxy Server" listens on port 25, and the "SMTP Connection-specific Server" listens on port 9025.

[Pascal]

Is anything else on the machine listening on port 25 ?

[adrien]

Hi

Have you checked in both the SMTP server and SMTP proxy? sounds like you were previously using the SMTP proxy (rather than the SMTP server). However if WinGate messed up the upgrade, and missed that the SMTP server was disabled etc, it may have them both on port 25. If you disable the SMTP Server (on the system tab in GateKeeper), and then restart the SMTP proxy in the proxies tab, do they show up then?

Adrien

[sudleyplace]

Hi

Have you checked in both the SMTP server and SMTP proxy? sounds like you were previously using the SMTP proxy (rather than the SMTP server). However if WinGate messed up the upgrade, and missed that the SMTP server was disabled etc, it may have them both on port 25. If you disable the SMTP Server (on the system tab in GateKeeper), and then restart the SMTP proxy in the proxies tab, do they show up then?

Adrien

Sorry, but I had to revert to 5.2.3 with which everything works as expected. I can't live without the ability to send email. I made no changes to the configuration after downgrading to 5.2.3; similarly, I made no changes to the configuration when upgrading from 5.2.3 to 6.0.1 which is why I continue to believe this is a problem with 6.0.1.

I expect to be able to re-install 6.0.1 on Tuesday at which time I'll answer the questions you folks raised.

[Ghost]

Hi.
Found the same trouble with the SMTP proxy.
See - SMTP server is switched off.
SMPT proxy is at the port 25. Bindings tab. Top window: empty. Bottom window: (standart)
Bind only to 127.0.0.1 on MS TCP Loopback... (checked)
Bind to any IP address on Local Area... blah-blah (checked)
:)
of course - it can't work - it doesn't work :)
5.2.3 was more clear - had no troubles with it. (not so good English, but idea is clear, I hope)
Regards.

PS - I don't need a smart solution - just started SMTP server instead of the proxy. It works.
PPS - don't understand a reason to make the help system more knotty... just IMHO.

[Pascal]

Working from the assumption that you are running a NT based system:

Open a command prompt and run "netstat -ano". This will give you the process ID of each application that is listening on a given port. Check which application is listening on port 25 (You will need to reference the PID column with the value in TaskManager)

If anything else (Or WinGate) is listening on port 25, you will not see any bindings (Including local-host). If that is the case, then the second service (Or first if it's not WinGate) attempting to bind with it will fail.

If you do see something listening on port 25 and it's WinGate then we'll need to check your setup to find out what it is.

[Ghost]

Hi Pascal.
(supposing that your message was addressed to me :)
yeah, Win2K Pro, SP4, WG 6.0.1 (955), 3 users, bought a couple of day ago at your site.
25 port is free - Active Ports, netstat -an - the same results :) was a predictable result - 'cos WG's SMTP server works well at 25 port (and has bindings, of course). now I'm switching it off. Services -> New->SMTP mapping... no bindings :)
it isn't a critical problem for me - your SMTP server works well. And mail sending it's only I need - and there is no big difference for me - SMTP server or SMTP mapping... Just was a bit curious. And thought this tiny moment will be interesting for u.
Regards.

[sudleyplace]

Hi

Have you checked in both the SMTP server and SMTP proxy? sounds like you were previously using the SMTP proxy (rather than the SMTP server). However if WinGate messed up the upgrade, and missed that the SMTP server was disabled etc, it may have them both on port 25. If you disable the SMTP Server (on the system tab in GateKeeper), and then restart the SMTP proxy in the proxies tab, do they show up then?

Adrien

I was using the SMTP Proxy Server only, never the SMTP Server which has always been off.

Under 5.2.3, netstat -an shows

TCP 0.0.0.0:25 0.0.0.0:0 LISTENING

I reinstalled 6.0.1 with the following results:

The same command has no entry with ":25" in it.

The Bindings window under "SMTP Proxy Server" is empty.

The "SMTP Server" is stopped. Curiously, under both the "SMTP Server" and the "SMTP Proxy Server", the Binding Policy window has two duplicate entries of

Bind to any IP address on any internal adapter

as well as one for 127.0.0.1.

[sudleyplace]

Is there anything more on this topic? I would like to upgrade to version 6 in the fond hope that it fixes the "Fatal Application Exit" error dialog box which occurs whenever I bring up Gatekeeper.

[labull]

6.0.2 was released today.

Check to see if it fixes the problem.

Larry

[sudleyplace]

6.0.2 was released today.

Check to see if it fixes the problem.

Larry

I already did that and there was no change. The bindings are still missing.

[adrien]

OK, if the policy says "bind to any internal adapter", but previously you used to see (in version 5.2.3) an entry on 0.0.0.0:25, then that means in version 5 config, you had it set to accept connections on any interface.

To achieve the same in WinGate, you change the binding policy (the bottom part of the bindings tab) to "accept on any adapter" rather than any internal adapter.

Anyway, if you have no adapters showing as "internal" in the Network tab, that would explain why there are no bindings.

Otherwise, if your adapter was indeed marked as internal, and yet WinGate still doesn't bind to the adapters try the following.

1. Delete all binding policies from the SMTP server
2. Delete all binding policies from the SMTP proxy
3. Save settings
4. Restart WinGate
5. Add binding policies to the SMTP proxy = accept connections on any adapter.
6. Hit the apply button in the SMTP proxy. You should see the binding pop up.

Adrien

[sudleyplace]

OK, if the policy says "bind to any internal adapter", but previously you used to see (in version 5.2.3) an entry on 0.0.0.0:25, then that means in version 5 config, you had it set to accept connections on any interface.

To achieve the same in WinGate, you change the binding policy (the bottom part of the bindings tab) to "accept on any adapter" rather than any internal adapter.

Anyway, if you have no adapters showing as "internal" in the Network tab, that would explain why there are no bindings.

Otherwise, if your adapter was indeed marked as internal, and yet WinGate still doesn't bind to the adapters try the following.

1. Delete all binding policies from the SMTP server
2. Delete all binding policies from the SMTP proxy
3. Save settings
4. Restart WinGate
5. Add binding policies to the SMTP proxy = accept connections on any adapter.
6. Hit the apply button in the SMTP proxy. You should see the binding pop up.

Adrien

There are two adapters, one marked as internal, the other external.

Following these directions did indeed cause the bindings to change for the SMTP Proxy Server and I can now send email. Congratulations! Good work.