In My travels I’ve now twice encountered Wi-fi Networks that block port 25: the default port to send emails. So for the last week, I hadn’t been able to send emails from Outlook.
If you or your email users have established Outlook settings using port 26 for POP email, you will experience email errors when moving to the VPS, as port 26 is not enabled by default. Since some users’ ISPs do not allow port 25, you may want to enable port 26:
1. In your WHM go to Service Configuration > Service Manager
2. Scroll to the bottom where you will see: Exim on another port
3. Check both boxes (Enable and Monitor) and fill in the box for port 26
4. Save configuration, and you’re done.
Now, port 26 is also frequently block (it is where I’m staying now, for example). So, you can choose some other random port to send your emails.
Then what you have to do in outlook is go to tools-> accounts. Then select the account, and the Advanced tab. Then change the Outgoing mail (SMTP) Port to match.
Hope that makes sense. It worked for me and now I can send email again from outlook.
2 Responses to “Block Port 25 on Wifi? Here’s The Work Around to Send email”
Dude… as black hat as you are, do you really want your emails, along with usernames and passwords, going cleartext on some silly wifi connection? Switch to an encrypted port, say… 465 for outgoing, 995 for incoming… so that people like who like to experiment with capturing wifi packets don’t compromise your emails, usernames and passwords (ditto FTP). Not that I’d do that, but I have been know to experiment with different network tools.
It seems that many hosts are actually set up to handle these ports using SSL (in my experience) and more importantly I’ve never been blocked on a wifi connection or even a wired connection for that matter.
Leave a Reply
You must be logged in to post a comment.
When I was a kid we used to use Putty to drill an SSL tunnel to our computer back at home to do stuff like this. Our skrewl had blocked ICQ you see, and that was intolerable.