Mutt: Difference between revisions
imported>Pew No edit summary |
|||
| Line 8: | Line 8: | ||
== Mutt VT/Google Mail Setup == | == Mutt VT/Google Mail Setup == | ||
VT email lives in Google GSuite (i.e. gmail). Because GSuite is deprecating "less secure devices/app-passwords", | |||
you will need to use IMAP and SMTP with the XOAUTH2 authentication method. | |||
Most mutt users use [[isync|isync/mbsync]] or [[offlineimap]] as imap reader tools. mbsync is better; | |||
offlineimap has longstanding bugs with conflicting message IDs that can cause messages to be deleted, | |||
and it is much easier to configure mbsync with multiple imap accounts, however mbsync's auth plugin | |||
support is fragile, while offlineimap has built-in XOAUTH2 support. | |||
Mutt has some [http://www.mutt.org/doc/manual/#oauth internal] OAUTH support that can be used. Alternately, | |||
use an external tool like [https://github.com/cscorley/send.py send.py] as your sendmail drop-in. | |||
The caveat of setting up [[OAUTH2]] is that Google has disabled trial credential creation in billed | |||
accounts (i.e. GSuite), so you *cannot* use your VT account to create them. Further, to reduce abuse, | |||
Google must approve all public apps; a warning pops up if it is not approved, which can only | |||
be bypassed if you are the owner of the application. In short, you must create OAUTH credentials | |||
with a non-GSuite google account, add your @vt.edu account to the project, and then use it to | |||
log in. | |||
== LUUGmail == | == LUUGmail == | ||