From ArchWiki
Revision as of 21:08, 3 October 2016 by Pineman13 (talk | contribs) (Added →‎Secure Environment: talk)
Jump to navigation Jump to search

Using mixmaster in Mutt

I once installed mutt with mixmaster, after upgrading it, mixmaster is not installed by default with mutt. -- Pickfire(talk) 15:25, 5 July 2015‎ (UTC)


set folder=$HOME/mail

Does the folder need a trailing slash? like

set folder=$HOME/mail/

Napterk (talk) 06:45, 4 April 2016 (UTC)

Deleted section in Display recipient instead of sender in "Sent" folder view

This section was originally under `Display recipient instead of sender in "Sent" folder view`

I removed it because there's a much simpler way, but this might be useful for some edge cases, so feel free to put it back (with a caveat that it's sub-optimal). The deleted section follows:

The "columns" of the index can be configured through the index_format variable. Its syntax is documented in the muttrc man page. The values of our concern are %t (recipient) and %F (sender).

To change the columns according to the current folder, we need to use a hook:

folder-hook   .*[sS]ent.* 'set index_format="%2C | %Z [%d] %-30.30t (%-4.4c) %?M?<%M> ?%s"'
folder-hook ! .*[sS]ent.* 'set index_format="%2C | %Z [%d] %-30.30F (%-4.4c) %?M?<%M> ?%s"'

The exclamation mark means everything that does not match the following regex. Of course you can change the index_format following your taste, and the regular expression if the folder does not have Sent nor sent in its name.

Let us centralize the settings, it will simplify future tweaking.

set my_index_format_pre='set index_format="%2C | %Z [%d] %-30.30'
set my_index_format_post=' (%-4.4c) %?M?<%M> ?%s"'

folder-hook .*[sS]ent.* "$my_index_format_pre"t"$my_index_format_post"
folder-hook ! .*[sS]ent.* "$my_index_format_pre"F"$my_index_format_post"

Secure Environment

I believe that local openvpn article was describing secure environment as a mere /root/ folder, since no one can access it besides local root(or whoever is authorized as such). Another far more concrete, yet comparatively more resource hungry approach, would be to call some kind of a chroot jail and perform necessary operations in it. This however, for an apparent reason, would not be fitting for all cases, such as a VPS, where space and resources are already fairly limited -- Pineman13 (talk) 21:06, 3 October 2016 (UTC)