The TCP mapping service needn't run on port 25, it only needs to intercept port 25. So you can still run e.g. another mail server on port 25 without conflicting, the only connections that will be intercepted are ones that would be through WinGate to the net, not connections to the WinGate machine itself on port 25.
I suppose this concerns also Natted connections.
If you leave all the mappings blank and default mapping blank, then the TCP mapping proxy will connect to the originally intercepted destination IP:port, so the client will connect through to where they were originally trying to connect to, but you get policy control, and can do things like make the connection out a specified gateway etc
Good, this should work as I need.
The aim of this configuration is to prevent the remote eventuality that a "massmailer infected pc" can communicate with the internet and have the public IP blacklisted (Desktops are usually clean: SAV Antivirus on eachone + Kav on Wingate it's safe enough but many external Laptops are often connected to lan . . . . . . ). I'll try to test blocking with a OES2 virtual machine with a test Groupwise 8.0 installed on it that will perform the "bad guy" character.
Felice pasqua!
Studying italian ? ;-)
Bye
Nicola