this app will, eventually, not be gui but will be a daemon. I'm jsut using a gui right now because I'm struggling to get the app to work as a daemon for different reasons:

when I develop windows services, because debugging them is a pain in the arse, its easier to just make a dummy gui that does nothing but embodies the service code. essentially rather than using the SCM to launch the app and call start() (and then struggle to attacha debugger to it) it is easier to open a blank window and start its message loop then have a button on the window call start().

same goes here, I'm doing a service/daemon, but I'm using the gui aspect first so that the phone shows me something i can interact with so I know its working/have a text panel to send debug messages to. eventually the app will not have a gui and will probably be configured using the browser

i think, therefore, it may be wiser to just run a high port number in the future; it doesnt really matter - the clients of this app (smtp capable programs) can always change the port number to match the app, and it may be more sensible from an exploit point of view not to have the program running as root..

thanks to all!