This dates back to the darpa protocol days.
Ports 0-1023 are what are referred to now as the "Well-known" ports and this is the design of the network layer and applications that are well thought out follow these standards. There is going to be no "conf" file or anywhere where it explicitly states what ports rcp portmapper could bind to. Basically, it assumes that the application is written well enough to know not to interfere with others and you as a sys admin have to be aware of your own port bindings. An application will call the rpc portmapper and tell it what port to listen on and thats about the jist of it. If your app tries to bind to a port that is already in use you will get an error.
This is to say that an email developer isnt going to try and use port 80 for pop3 because its not the standard but there is no conf file on your system that says that pop3 can't be on port 80.
Best I could find on this was
http://www.iana.org/assignments/serv...-numbers.xhtml
But again it just says that 0-1023 are system ports, its not defined anywhere else besides the standardization of applications that are written.