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

Hidden smtp server

Dec 18 03 8:11 am

I am running a old MDaemon mail server on the Wingate (version 5.22 with V4 license) gateway machine under NT4. Currently Mdaemon is not routed through wingate but I wish to use that configuration. However, when I set the smtp proxy I get a message saying the port is already in use by SMTP server. This server appears to be present in the registry but does not appear on the services gui. Deleting the reference from registry has no effect as it is regenerated on restarting wingate. The same appears to happen with Version 4 installed.

Any siggestions as to where to start would be appreciated! I don't have any data plugins (as far as I know) but this may be an extension of the 'known issues' problem

Re: Hidden smtp server

Dec 18 03 8:39 am

johnlow wrote:Any siggestions as to where to start would be appreciated! I don't have any data plugins (as far as I know) but this may be an extension of the 'known issues' problem


The SMTP server will not be visible if you're running with a version 4 license key. However, it should not be recreated or even started then. That sounds like a bit of a problem.

The easiest workaround I can suggest for now is to change the service port and service startup in the registry directly, then we'll look into this for the next release.

All the usual registry editing warnings apply (Backup, etc.) You will need to stop the engine before making these changes, then restart it once you've made the changes.

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Services\SMTP Server

Name: PortNumber
Value: 25 (Default) Change the 25 to an unused value.

Name: Startup
Value: ??? Change this to 0 to force it into a disabled state

Dec 18 03 10:15 am

doies the Mdaemon server start successfully?

It is possible that the warning you get on creation of the SMTP mapping can be safely ignored, as the SMTP server should not actually start, yet may still be configured on port 25 so the checking for conflicts (which I think doesn't take into account whether the service starts or not) will warn.

Adrien

Dec 18 03 10:30 pm

Thank you Pascal your response fixed the problem. I will probably upgrade to V5 in due course. Compliments of the season to all!

Dec 19 03 12:10 am

johnlow wrote:Thank you Pascal your response fixed the problem.


Good stuff, glad it worked. Compliments of the season to you too ...
Post a reply