This is an old revision of the document!
Table of Contents
Mail Readers
We do not recommend any particular mail reader. Many are available on our computer systems, including Alpine, Mutt, and Thunderbird.
Stop Forwarding First
By default we forward your CS mail to username@uchicago.edu. If you would like to use the CS mail server directly please send us an email to stop the forwarding.
IMAP Client Configuration
@cs.uchicago.edu
Email Address | user@cs.uchicago.edu |
Mail Server Type | IMAP |
Username | <cnetid> |
Password | <cnetid password> |
Incoming Mail Server | imap.cs.uchicago.edu |
Security | START/TLS |
Port | 993 |
Authentication Method | Normal Password |
Outgoing Mail Server | smtp.cs.uchicago.edu |
Security | START/TLS |
Port | 587 |
Authentication Method | Normal Password |
@uchicago.edu (O365)
Email Address | user@uchicago.edu |
Mail Server Type | IMAP |
Username | <cnetid>@uchicago.edu |
Password | <cnetid password> |
Incoming Mail Server | outlook.office365.com |
Security | START/TLS |
Port | 143 |
Authentication Method | OAuth2 |
Outgoing Mail Server | outlook.office365.com |
Security | START/TLS |
Port | 587 |
Authentication Method | OAuth2 |
Mutt Support
We have mutt 2.0.0+ working (that is a requirement). Inside their github you'll see the mutt_oauth2.py stuff under the contrib/ dir https://github.com/muttmua/mutt/tree/master/contrib. The README is good.
Another requirement is a working gpg-agent rig.
In my muttrc, I have these:
set imap_user = "bartonp@uchicago.edu" set imap_authenticators = "xoauth2" set imap_oauth_refresh_command = "~/.mutt/mutt_oauth2/mutt_oauth2-uchicago.edu.py ~/.mutt/tmp/${imap_user}.tokens" set smtp_url = "smtp://${imap_user}@smtp.office365.com:587/" set smtp_authenticators = ${imap_authenticators} set smtp_oauth_refresh_command = ${imap_oauth_refresh_command}
The client-id is 695da824-3d11-464b-98cc-83c714d21cf8
. There is a client_secret 1Frt-83W.-vg579wht-f2m9Tt2D1s.n7_2
however in the registrations{}
section in mutt_oauth2.py
, I have client_secret as blank. IIRC setting it was causing issues.
'microsoft': { 'authorize_endpoint': 'https://login.microsoftonline.com/common/oauth2/v2.0/authorize', 'devicecode_endpoint': 'https://login.microsoftonline.com/common/oauth2/v2.0/devicecode', 'token_endpoint': 'https://login.microsoftonline.com/common/oauth2/v2.0/token', 'redirect_uri': 'https://login.microsoftonline.com/common/oauth2/nativeclient', 'tenant': 'common', 'imap_endpoint': 'outlook.office365.com', 'pop_endpoint': 'outlook.office365.com', 'smtp_endpoint': 'smtp.office365.com', 'sasl_method': 'XOAUTH2', 'scope': ('offline_access https://outlook.office.com/IMAP.AccessAsUser.All ' 'https://outlook.office.com/POP.AccessAsUser.All ' 'https://outlook.office.com/SMTP.Send'), 'client_id': '695da824-3d11-464b-98cc-83c714d21cf8', 'client_secret': '', },