OK, I've read the threads about ports 25 and using a workaround using port 26 and port 587. Well, let me throw you a curve. Cox blocks port 110. Can I work around it by using 587 for the pop setting. Is this possible in exim?
Depending on your OS Distribution and your firewall you can create custom firewall rules so that you accept a different port (perhaps 1110?) and map it to port 110 on your server.
If Cox really blocks port 110 then they're severely restricting your ability use your Internet connection and you should probably cancel their service. I know I wouldn't use service that blocks important ports.
It isn't me, I can always work aroound it. It's several of my clients here in NE Kansas who use Cox for their broadband connectons. I was using dreamhost out of LA when they started doing this. They (the techs at dreamhost) came up with using 587 (I think).
Anyway, after posting my lack of Linux speak was glaringly appearant. The modifications I need may not be in the Exim file, but rather in some other config file somewhere. Do you know where that may be?
I have not done this much command line work since college,and i graduated in 1985, when everything was commandline.
Port 587 is reserved for authenticated senders to replace port 25. You can probably set the POP daemon to listen to a different port but then that would affect everyone; no one could use 110 anymore.
I don't know of the pop daemon can listen to multiple ports, hence I recommended using a firewall solution instead.
I have it all finished, thanks, for the tips. My old Red Hat Linux book and a Sam's manual got me through. It's been so long since i was in college, my only remaining job skill is now reading.