<pre> "''All mail clients suck. This one just sucks less.''"<ref>http://www.mutt.org/</ref> </pre>
'''Mutt''' is a [[w:text user interface|text-based]] [[w:email client|email client]] for [[w:Unix-like|Unix-like]] systems. It was originally written by Michael Elkins in 1995 and released under the [[w:GNU General Public License|GPL]] version 2 or any later version.<ref>
https://en.wikipedia.org/wiki/Mutt_%28email_client%29</ref>
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 ==
This will cover basic mutt configuration files for connecting to VT webmailemail lives in Google GSuite (i. VT recommends using POP until the quota system e. gmail). Because GSuite is in place because POP deprecating "less secure devices/app-passwords",you will store local copies, but need to use IMAP still works. These settings will get mutt working and SMTP with VT's email servers, but there are other settings you probably want if you are unfamiliar with muttthe XOAUTH2 authentication method.
== IMAP ==Most mutt users use [[isync|isync/mbsync]] or [[offlineimap]] as imap reader tools. mbsync is better;Anything in all caps should offlineimap has longstanding bugs with conflicting message IDs that can cause messages to be replaced deleted, and it is much easier to configure mbsync with your information<pre>set imap_user = "PID@vt.edu"set imap_pass = "PASSWORD"set from = "PID@vt.edu"set folder = "imaps://multiple imap.vt.edu:993"accounts, however mbsync's auth pluginset spoolfile = "+Inbox"set hostname = vtsupport is fragile, while offlineimap has built-in XOAUTH2 support.eduset postponed = "+Drafts"set record = "+Sent"</pre>
If trash is compiled into Mutt has some [http://www.mutt you .org/doc/manual/#oauth internal] OAUTH support that can addbe used. Alternately,use an external tool like [https:<pre>set trash = "+Trash"</pre>/github.com/cscorley/send.py send.py] as your sendmail drop-in.
== POP ==The caveat of setting up [[OAUTH2]] is that Google has disabled trial credential creation in billedComing soonaccounts (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== SMTP ==be bypassed if you are the owner of the application. In short, you must create OAUTH credentials<pre>set smtp_url = "smtps://PIDwith a non-GSuite google account, add your @vt.edu@auth.smtp.vt.edu:465/"set smtp_pass = "PASSWORD</pre>If you are using GnuTLS in mutt and get an error saying account to the key is too small. GnuTLS supports 256 AESproject, but and then use it defaults to 128 when connectinglog in. For this you must add this:<pre>set ssl_min_dh_prime_bits = 500</pre>
== LUUGmail ==
Acidburn currently has functional postfix/dovecot. This is how to use it with mutt.
=== IMAP/SMTP for acidburn ===
This is a sample configuration for imap/smtp in mutt for acidburn, provided by [[User:echarlie|echarlie]]
would suggest setting your mutt editor, setting your encoding preference (UTF-8), and changing keybindings to preference.
'''NOTE: storing passwords in cleartext on acidburn is not recommended, nor is storing your pgp key on acidburn so you can decrypt it'''
<pre>
set header_cache=~/.cache/mutt #optional; header caching speeds things up
set my_pass= <your password here>
set my_user=wadsworth
</pre>
== References ==
[[Category:Howtos]]
[[Category:Software]]
[[Category:Mail clients]]
[[Category:Needs restoration]]