Hosted Email:Mutt - Revision history

Jab at 20:18, 14 January 2014

2014-01-14T20:18:51Z

← Older revision		Revision as of 14:18, 14 January 2014
Line 92:		Line 92:
	That should get you up and running with Mutt. Launch <tt>mutt(1)</tt> from the command line, and start working.		That should get you up and running with Mutt. Launch <tt>mutt(1)</tt> from the command line, and start working.

	[[Category:Client Email Configuration\|Zimbra\|Mutt]]		[[Category:Client Email Configuration\|Zimbra\|Mutt Linux]]
	[[Category:Zimbra\|Mutt]]		[[Category:Zimbra\|Mutt Linux]]

Jab at 20:09, 14 January 2014

2014-01-14T20:09:04Z

← Older revision		Revision as of 14:09, 14 January 2014
Line 91:		Line 91:

	That should get you up and running with Mutt. Launch <tt>mutt(1)</tt> from the command line, and start working.		That should get you up and running with Mutt. Launch <tt>mutt(1)</tt> from the command line, and start working.

			[[Category:Client Email Configuration\|Zimbra\|Mutt]]
			[[Category:Zimbra\|Mutt]]

Atoponce: Added some headers for a cleaner, easier-to-parse document, and added a paragrph describing the motivation for encrypting the IMAP and SMTP passwords

2012-01-15T16:46:30Z

Added some headers for a cleaner, easier-to-parse document, and added a paragrph describing the motivation for encrypting the IMAP and SMTP passwords

← Older revision		Revision as of 10:46, 15 January 2012
Line 1:		Line 1:
			== Introduction ==

	Setting up Mutt to work with our Zimbra server is actually quite painless. There are just a few things to know about how Mutt works Zimbra servers:		Setting up Mutt to work with our Zimbra server is actually quite painless. There are just a few things to know about how Mutt works Zimbra servers:

Line 8:		Line 10:
	* Lastly, this guide shows how to setup Mutt using encrypted passwords on disk using your GPG key, should you wish to run Mutt on a shared server.		* Lastly, this guide shows how to setup Mutt using encrypted passwords on disk using your GPG key, should you wish to run Mutt on a shared server.

	~~With that~~, ~~let's get started~~. ~~First~~, ~~let's~~ encrypt your IMAP and SMTP password with your GPG key. Create a plain text file as <tt>~/.mutt/passwords</tt> with the following contents:		== Configuration ==
			=== Encrypted passwords ===

			By default, Mutt stores its passwords on disk in the Muttrc in plain text. You should encrypt your passwords, and force Mutt to decrypt them as needed. You can use GnuPG, OpenSSL, your operating system keyring or crypto APIs to encrypt and decrypt the IMAP and SMTP passwords. The idea is to create a "master password" that will decrypt the necessary passwords, and place them in RAM for Mutt to take advantage of.

			This document describes encrypting your IMAP and SMTP password with your GPG key. Create a plain text file as <tt>~/.mutt/passwords</tt> with the following contents:

	<pre>set imap_pass="password"		<pre>set imap_pass="password"
Line 24:		Line 31:
	$ rm ~/.mutt/passwords</pre>		$ rm ~/.mutt/passwords</pre>

	This assumes that <tt>shred(1)</tt> is installed. If it is not installed, other utilities like <tt>srm(1)</tt> or <tt>wipe(1)</tt> might be installed to perform the same task, or you may need to install them. Removing the file securely is important, as just using <tt>rm(1)</tt> makes the inode pointing to the file available without actually scrubbing the bits on the filesystem. While difficult, it could be possible to restore the plain text file, and recover the passwords, should the file not be securely wiped.		This assumes that <tt>shred(1)</tt> is installed. If it is not installed, other utilities like <tt>srm(1)</tt> or <tt>wipe(1)</tt> might be installed to perform the same task, or you may need to install them. Removing the file securely is important, as just using <tt>rm(1)</tt> makes the inode pointing to the file available without actually scrubbing the bits on the filesystem. While difficult, it could be possible to restore the plain text file, and recover the passwords, should the file not be securely wiped. The only thing left to do at this point is decrypt the file in your <tt>~/.mutt/muttrc</tt>.

	~~The only thing left to do at this point is decrypt the file in your <tt>~/.mutt/muttrc</tt>, which is pasted here:~~		=== Required configuration ===

	<pre>set copy="yes" # Save sent mail on Zimbra		<pre>set copy="yes" # Save sent mail on Zimbra
Line 48:		Line 55:

	Note that the last line is decrypting your encrypted passwords and is piping the result to Mutt. It is critical that "\|" terminates the string, or Mutt will not parse the output, and you will not be able to login. When launching Mutt, you will be asked for your GPG passphrase, then your IMAP and SMTP passwords will be stored in RAM in plain text, so Mutt can use them for logging in. If you also use GPG for signing, verifying, encrypting and decrypting mail, then you may want to use the <tt>gpg-agent(1)</tt> and <tt>gpg2(1)</tt> to cache your GPG passphrase in RAM.		Note that the last line is decrypting your encrypted passwords and is piping the result to Mutt. It is critical that "\|" terminates the string, or Mutt will not parse the output, and you will not be able to login. When launching Mutt, you will be asked for your GPG passphrase, then your IMAP and SMTP passwords will be stored in RAM in plain text, so Mutt can use them for logging in. If you also use GPG for signing, verifying, encrypting and decrypting mail, then you may want to use the <tt>gpg-agent(1)</tt> and <tt>gpg2(1)</tt> to cache your GPG passphrase in RAM.

			=== Additonal configuration ===

	You may wish to add some additional variables to your Muttrc. Here are some sane defaults that I have set:		You may wish to add some additional variables to your Muttrc. Here are some sane defaults that I have set:

Secretions: A space for formatting

2012-01-14T17:16:33Z

A space for formatting

← Older revision		Revision as of 11:16, 14 January 2012
Line 29:		Line 29:

	<pre>set copy="yes" # Save sent mail on Zimbra		<pre>set copy="yes" # Save sent mail on Zimbra
	set from="username@domain.com" # Your XMission email		set from="username@domain.com" # Your XMission email
	set folder="imaps://zimbra.xmission.com" # The remote Zimbra IMAP URI		set folder="imaps://zimbra.xmission.com" # The remote Zimbra IMAP URI
	set imap_idle="yes" # Use IMAP IDLE for pushing mail		set imap_idle="yes" # Use IMAP IDLE for pushing mail

Secretions: Also forgot to delete the old editor line

2012-01-14T17:15:42Z

Also forgot to delete the old editor line

← Older revision		Revision as of 11:15, 14 January 2012
Line 56:		Line 56:
	set certificate_file="~/.mutt/certs" # SASL2 certificate location		set certificate_file="~/.mutt/certs" # SASL2 certificate location
	set edit_headers="yes" # Edit the headers when composing a message		set edit_headers="yes" # Edit the headers when composing a message
	~~set editor="/usr/bin/vim" # Use Vim as your editor for composing mail~~
	set envelope_from="yes" # Use quoted-printable encoded message when "From " is at the beginning of a line		set envelope_from="yes" # Use quoted-printable encoded message when "From " is at the beginning of a line
	set header_cache="~/.mutt/cache/headers" # Location to save cached mail headers		set header_cache="~/.mutt/cache/headers" # Location to save cached mail headers

Secretions: Missed that that was already there

2012-01-14T17:14:23Z

Missed that that was already there

← Older revision		Revision as of 11:14, 14 January 2012
Line 69:		Line 69:
	set sort_aux="last-date-received" # Sort threads by date received		set sort_aux="last-date-received" # Sort threads by date received
	set use_from # Allow me to switch email addresses in my editor		set use_from # Allow me to switch email addresses in my editor
	~~set header_cache=~/.mutt_cache # Cache message headers, reducing imap requests and improving performance~~

	# Set editor with automatic line wrapping at 75 characters.		# Set editor with automatic line wrapping at 75 characters.

Secretions at 17:11, 14 January 2012

2012-01-14T17:11:13Z

← Older revision		Revision as of 11:11, 14 January 2012
Line 69:		Line 69:
	set sort_aux="last-date-received" # Sort threads by date received		set sort_aux="last-date-received" # Sort threads by date received
	set use_from # Allow me to switch email addresses in my editor		set use_from # Allow me to switch email addresses in my editor
			set header_cache=~/.mutt_cache # Cache message headers, reducing imap requests and improving performance

			# Set editor with automatic line wrapping at 75 characters.
			set editor="vim '+set textwidth=75 wrap'"

	ignore * # Draconian header weed		ignore * # Draconian header weed

Secretions: Example "from" address is @xmission.com, which is unlikely for hosted email.

2012-01-14T16:45:37Z

Example "from" address is @xmission.com, which is unlikely for hosted email.

← Older revision		Revision as of 10:45, 14 January 2012
Line 29:		Line 29:

	<pre>set copy="yes" # Save sent mail on Zimbra		<pre>set copy="yes" # Save sent mail on Zimbra
	set from="username@~~xmission~~.com" # Your XMission email		set from="username@domain.com" # Your XMission email
	set folder="imaps://zimbra.xmission.com" # The remote Zimbra IMAP URI		set folder="imaps://zimbra.xmission.com" # The remote Zimbra IMAP URI
	set imap_idle="yes" # Use IMAP IDLE for pushing mail		set imap_idle="yes" # Use IMAP IDLE for pushing mail

Atoponce: Added bullet about folder subscriptions and did some small formatting cleanup

2012-01-14T14:46:09Z

Added bullet about folder subscriptions and did some small formatting cleanup

Atoponce: Change comment from snark in my personal ~/.mutt/muttrc to something more appropriate for a public facing document.

2012-01-14T14:28:53Z

Change comment from snark in my personal ~/.mutt/muttrc to something more appropriate for a public facing document.

← Older revision		Revision as of 08:28, 14 January 2012
Line 55:		Line 55:
	set certificate_file="~/.mutt/certs" # SASL2 certificate location		set certificate_file="~/.mutt/certs" # SASL2 certificate location
	set edit_headers="yes" # Edit the headers when composing a message		set edit_headers="yes" # Edit the headers when composing a message
	set editor="/usr/bin/vim" # ~~Anything else is an abomination.~~		set editor="/usr/bin/vim" # Use Vim as your editor for composing mail
	set envelope_from="yes" # Use quoted-printable encoded message when "From " is at the beginning of a line		set envelope_from="yes" # Use quoted-printable encoded message when "From " is at the beginning of a line
	set header_cache="~/.mutt/cache/headers" # Location to save cached mail headers		set header_cache="~/.mutt/cache/headers" # Location to save cached mail headers

← Older revision		Revision as of 08:46, 14 January 2012
Line 1:		Line 1:
	Setting up Mutt to work with our Zimbra server is actually quite painless. There are just a few things to know about how Mutt works Zimbra servers:		Setting up Mutt to work with our Zimbra server is actually quite painless. There are just a few things to know about how Mutt works Zimbra servers:

	* Mutt doesn't automatically sync changes to your mailbox. You must either sync manually with ~~'''~~$~~'''~~, change mailboxes, change accounts, or logout then back in. This is to prevent Mutt from automatically deleting mail, should you accidentally press the ~~'''~~d~~'''~~ key on your keyboard, or other accidents.		* Mutt doesn't automatically sync changes to your mailbox. You must either sync manually with "$", change mailboxes, change accounts, or logout then back in. This is to prevent Mutt from automatically deleting mail, should you accidentally press the "d" key on your keyboard, or other accidents.
	* Mutt, as of 1.5.11, supports IMAP IDLE, which our Zimbra server supports. However, the default push of new mail is once every 29 minutes. You may want to decrease this time by using the ~~'''~~mail_check~~'''~~ variable, and setting to something like 60 seconds.		* Mutt, as of 1.5.11, supports IMAP IDLE, which our Zimbra server supports. However, the default push of new mail is once every 29 minutes. You may want to decrease this time by using the <tt>mail_check</tt> variable, and setting to something like 60 seconds.
	* When sending mail in Mutt using Gmail, your sent messages are automatically stored in "[Gmail]/Sent Mail", whether you like it or not. Zimbra doesn't do this. You must actually tell Mutt to save a copy of every message you send, or it will not be saved in the "/Sent" folder on the Zimbra server.		* When sending mail in Mutt using Gmail, your sent messages are automatically stored in "[Gmail]/Sent Mail", whether you like it or not. Zimbra doesn't do this. You must actually tell Mutt to save a copy of every message you send, or it will not be saved in the "/Sent" folder on the Zimbra server.
	* Mutt does support a vast array of address book options. The "default" is to use a plain text aliases file, and save aliases to it as you interact with contacts via email. You could also hook into a Perl or Python script for querying the Zimbra address book on the server, although that isn't covered here.		* Mutt does support a vast array of address book options. The "default" is to use a plain text aliases file, and save aliases to it as you interact with contacts via email. You could also hook into a Perl or Python script for querying the Zimbra address book on the server, although that isn't covered here.
			* Mutt can subscribe to Zimbra folders in the "Directory" view. Press "c?" to get to the directory view, then press "s" to subscribe to the necessary folder.
	* Lastly, this guide shows how to setup Mutt using encrypted passwords on disk using your GPG key, should you wish to run Mutt on a shared server.		* Lastly, this guide shows how to setup Mutt using encrypted passwords on disk using your GPG key, should you wish to run Mutt on a shared server.

	With that, let's get started. First, let's encrypt your IMAP and SMTP password with your GPG key. Create a plain text file as ~/.mutt/passwords with the following contents:		With that, let's get started. First, let's encrypt your IMAP and SMTP password with your GPG key. Create a plain text file as <tt>~/.mutt/passwords</tt> with the following contents:

	<pre>set imap_pass="password"		<pre>set imap_pass="password"
Line 25:		Line 26:
	This assumes that <tt>shred(1)</tt> is installed. If it is not installed, other utilities like <tt>srm(1)</tt> or <tt>wipe(1)</tt> might be installed to perform the same task, or you may need to install them. Removing the file securely is important, as just using <tt>rm(1)</tt> makes the inode pointing to the file available without actually scrubbing the bits on the filesystem. While difficult, it could be possible to restore the plain text file, and recover the passwords, should the file not be securely wiped.		This assumes that <tt>shred(1)</tt> is installed. If it is not installed, other utilities like <tt>srm(1)</tt> or <tt>wipe(1)</tt> might be installed to perform the same task, or you may need to install them. Removing the file securely is important, as just using <tt>rm(1)</tt> makes the inode pointing to the file available without actually scrubbing the bits on the filesystem. While difficult, it could be possible to restore the plain text file, and recover the passwords, should the file not be securely wiped.

	The only thing left to do at this point is decrypt the file in your ~/.mutt/muttrc, which is pasted here:		The only thing left to do at this point is decrypt the file in your <tt>~/.mutt/muttrc</tt>, which is pasted here:

	<pre>set copy="yes" # Save sent mail on Zimbra		<pre>set copy="yes" # Save sent mail on Zimbra