|
|
Translate outgoing destination ports
Would this solution work for email too? For example, my university only uses port 25 for email but my isp at home blocks port 25. Unfortunately I don't understand most of what was written but was wondering what sort of changes would have to be made.
Translate outgoing destination ports
The example given in the hint aligns two port numbers where neither client nor server can be altered. The firewall, ipfw, was used as the intermediary to solve this by sending traffic from local port 389 to remote port 712 and vice versa. The translation happens on the local machine, so the network carries traffic on port 712. In your case, the client software is largely irrelevant: you need to avoid port 25 on the network, but the remote machine is only listening on port 25. Note also that the hint would not have been necessary if the client software had the ability to alter the port it uses; and I can't think of an email program where you can't alter the SMTP port. If I were you, I'd make absolutely certain they don't offer an alternative port for SMTP. It seems strange they wouldn't. Have you tried port 587? That's the usual alternative. You might want to track down an actual technical person, too and ask them. Good luck!
Translate outgoing destination ports
The University of California should know better, but doesn't. At least at the Riverside campus, SMTP is _only_ available on port 25. Suck. Any given ISP will, however, un-block port 25 if you explain this to them. I've done it with both cable and phone ISPs. ---
Pell |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.23 seconds |
|