Mutt: Difference between revisions
imported>Echarlie No edit summary |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 6: | Line 6: | ||
Mutt was originally designed as a [[w:Mail User Agent|Mail User Agent]] (MUA) and relied on locally accessible mailbox and [[w:sendmail|sendmail]] infrastructure. According to the Mutt homepage "though written from scratch, Mutt's initial interface was based largely on the [[w:Elm (email client)|ELM mail client]]". New to Mutt were message scoring and threading capabilities. Support for fetching and sending email via various protocols such as [[w:POP3|POP3]], [[w:IMAP|IMAP]] and [[w:Simple Mail Transfer Protocol|SMTP]] was added later. Mutt relies on external tools for composing and filtering messages. | Mutt was originally designed as a [[w:Mail User Agent|Mail User Agent]] (MUA) and relied on locally accessible mailbox and [[w:sendmail|sendmail]] infrastructure. According to the Mutt homepage "though written from scratch, Mutt's initial interface was based largely on the [[w:Elm (email client)|ELM mail client]]". New to Mutt were message scoring and threading capabilities. Support for fetching and sending email via various protocols such as [[w:POP3|POP3]], [[w:IMAP|IMAP]] and [[w:Simple Mail Transfer Protocol|SMTP]] was added later. Mutt relies on external tools for composing and filtering messages. | ||
= 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 == | ||
Acidburn currently has functional postfix/dovecot. This is how to use it with mutt. | Acidburn currently has functional postfix/dovecot. This is how to use it with mutt. | ||
== IMAP/SMTP for acidburn == | === IMAP/SMTP for acidburn === | ||
This is a sample configuration for imap/smtp in mutt for acidburn, provided by [[User:echarlie|echarlie]] | This is a sample configuration for imap/smtp in mutt for acidburn, provided by [[User:echarlie|echarlie]] | ||
| Line 84: | Line 69: | ||
would suggest setting your mutt editor, setting your encoding preference (UTF-8), and changing keybindings to preference. | would suggest setting your mutt editor, setting your encoding preference (UTF-8), and changing keybindings to preference. | ||
<pre> | <pre> | ||
| Line 92: | Line 76: | ||
set header_cache=~/.cache/mutt #optional; header caching speeds things up | set header_cache=~/.cache/mutt #optional; header caching speeds things up | ||
set my_user=wadsworth | set my_user=wadsworth | ||
| Line 104: | Line 87: | ||
</pre> | </pre> | ||
= References = | == References == | ||
[[Category:Howtos]] | [[Category:Howtos]] | ||
[[Category:Software]] | |||
[[Category:Mail clients]] | [[Category:Mail clients]] | ||
[[Category:Needs restoration]] | |||