14
edits
Changes
Mutt
,→References
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. == IMAP Mutt VT/Google Mail Setup ==Anything VT email lives in all caps should be replaced Google GSuite (i.e. gmail). Because GSuite is deprecating "less secure devices/app-passwords",you will need to use IMAP and SMTP with your informationthe XOAUTH2 authentication method.<pre>set imap_user = "PID@vtMost mutt users use [[isync|isync/mbsync]] or [[offlineimap]] as imap reader tools.edu"mbsync is better;offlineimap has longstanding bugs with conflicting message IDs that can cause messages to be deleted, set imap_pass = "PASSWORD"and it is much easier to configure mbsync with multiple imap accounts, however mbsync's auth pluginset from = "PID@vtsupport is fragile, while offlineimap has built-in XOAUTH2 support.edu"set folder = "imapsMutt has some [http://imapwww.mutt.vtorg/doc/manual/#oauth internal] OAUTH support that can be used.eduAlternately,use an external tool like [https:993"//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 billedaccounts (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 onlyset spoolfile = "+Inbox"be bypassed if you are the owner of the application. In short, you must create OAUTH credentialsset hostname = with a non-GSuite google account, add your @vt.eduaccount to the project, and then use it tolog in.set postponed == LUUGmail = "+Drafts"set record = "+Sent"</pre>
== POP = IMAP/SMTP for acidburn ===Coming soon...
<pre>
set realname = 'Wadsworth Luugbot' #your display name hereset imap_user=wadsworth #this should be your LDAP account nameset imap_pass=$my_luug_pass #whatever Whatever your LUUG password is. Here we used a personal variable.
set ssl_force_tls=yes
set ssl_starttls=yes
set imap_check_subscribed
set pgp_sign_as = "wadsworth@vtluug.org" # If you like pgp-signing things
set from = "wadsworth@vtluug.org" #### THIS IS IMPORTANT ####
set use_from = yes
set smtp_url=smtp://$imap_user:$imap_pass@acidburn.vtluug.org:587
account-hook $folder "set imap_user=$imap_user imap_pass=$imap_pass ssl_verify_dates=no ssl_verify_host=no"
</pre>
This section assumes you are using mutt with multiple accounts. For that, we reccomend putting the following into <code>.muttrc/vtluug</code> or something similar, and having this in your <code>.mutt/muttrc</code> :
<pre>
source "~/.mutt/vtluug"
folder-hook $folder 'source ~/.mutt/vtluug'
</pre>
== Local Mail on acidburn ==
This is how one would read and send local mail on acidburn. This is a fully functional <code>.muttrc</code>, however we
would suggest setting your mutt editor, setting your encoding preference (UTF-8), and changing keybindings to preference.
<pre>
set mbox_type=Maildir #acidburn uses maildirs
set folder=$HOME/Maildir
set spoolfile=+/
set header_cache=~/.cache/mutt #optional; header caching speeds things up
set my_user=wadsworth
set realname = "Wadsworth Luugbot"
set from = wadsworth@vtluug.org
set use_from = yes
# This is needed if you want to send from another ldapified server
#set smtp_url=smtps://$my_user:$my_pass@acidburn.vtluug.org:587
#set ssl_force_tls = yes
</pre>
== References ==
[[Category:Howtos]]
[[Category:Software]]
[[Category:Mail clients]]
[[Category:Needs restoration]]