Configure Outlook to Use SMTP Auth

Follow the steps below to configure Outlook 2003 to send email from off-Grounds with SMTP Auth:
  1. Start Outlook.
  2. From the Tools menu, choose E-Mail Accounts.
  3. In the Email section of the E-Mail Accounts window, select the View or change existing email accounts radio button.
  4. Click Next.
  5. Select the entry for your UVa account under the heading Name and then click Change….
  6. For Outgoing mail server (SMTP),…
    • …for a CMS account, type: cms.mail.virginia.edu
    • …for a unix.mail account, type: smtp.mail.virginia.edu
  7. Click More Settings.
  8. Click the Outgoing Server tab.
  9. Check the My outgoing server (SMTP) requires authentication box.
  10. Select the Log on using radio button.
  11. Type your computing ID (e.g., mst3k) in the Account name field.
  12. Leave the Remember password box unchecked.
  13. Click the Advanced tab.
  14. Under Outgoing mail (SMTP) check the This server requires a secure connection (SSL) box.
  15. Click OK.
  16. Click Next in the E-mail Accounts window.
  17. Click Finish.

If Port 25 Is Blocked

Port 25 is used by default to send email messages. However, to prevent spam from being routed through their email servers, your ISP may not allow the use of port 25. In this case, follow the steps below to change your sending email port designation:

  1. Start Outlook.
  2. From the Tools menu, choose E-Mail Accounts.
  3. In the Email section of the E-Mail Accounts window, select the View or change existing email accounts radio button.
  4. Click Next.
  5. Select the entry for your UVa account under the heading Name and then click Change….
  6. Click More Settings.
  7. Click the Advanced tab.
  8. Type 465 in the Outgoing server (SMTP) field.
  9. Click OK
  10. In the E-mail Accounts window, click Next.
  11. Click Finish.

© 2008 by the Rector and Visitors of the University of Virginia.

The information contained on the University of Virginia’s Department of Information Technology and Communication (ITC) website is provided as a public service with the understanding that ITC makes no representations or warranties, either expressed or implied, concerning the accuracy, completeness, reliability or suitability of the information, including warrantees of title, non-infringement of copyright or patent rights of others. These pages are expected to represent the University of Virginia community and the State of Virginia in a professional manner in accordance with the University of Virginia’s Computing Policies.