WebMailPRO SMTP & POP3 Client Settings & Troubleshooting


Summary

WebMailPRO email can be accessed over POP3 and SMTP using most email clients.  We provide access to secure versions of these protocols, POP3S and SMTPS .  These are the settings you'll need to setup your client, and some simple troubleshooting steps to test your connection.

Applies To

WebMailPRO, SMTP, POP3

More Information

If your organization has a Firewall, you need to make sure ports 995 and 465 are open to 74.102.12.128/27 or 74.102.12.128 – 159.  See your network administrator to verify this.

To configure your mail client, you'll need these settings:

  • POP3 Server: pop3s.k12us.com
  • POP3 Port: 995
  • POP3 Username: The full email address on the account (for example, jdoe@example.com)
  • SMTP Server: smtps.k12us.com
  • SMTP Port: 465
  • SMTP Server requires authentication.  The username is the same as the email address on the account.

Some email clients (like Outlook 2003) have a separate check box to enable the use of SSL / encrypted connections.  You want to enable that option.

Some mail clients also have a check box for something like "Log on using Secure Password Authentication".  You do not want to enable this.

To test your connection to the server and verify your network is working correctly, you can perform these steps on a Windows PC.

  1. Go to "Start" -> "Run"
  2. In the dialog box, type "cmd" and click "Ok"
  3. In the command prompt, type "telnet pop3s.k12us.com 995", and press Enter.
  4. Wait around 40 seconds.  If you receive a time out error, then your firewall is blocking port 995, or your workstation cannot get to the Internet correctly.
  5. To run the next test, press and hold the "CTRL" key on your keyboard and press the "]" key, then type "quit" and press Enter.  You will now be back at a command prompt.
  6. Type "telnet smtps.k12us.com 465" and press Enter.
  7. Wait around 45 seconds.  If you receive a time out error, then your firewall is blocking port 465, or your workstation cannot get to the Internet correctly.

Note: If only a few users are having difficulties connecting, it's probably a personal firewall issue on those workstations.  Check the Firewall settings on the workstation itself.  Remember, a workstation may have multiple firewalls (for example, Windows Firewall, Symantec Endpoint Protection, etc).