Ticket #129 (closed enhancement: fixed)

Opened 13 years ago

Last modified 12 years ago

Package debathena-mutt-config

Reported by: broder Owned by: price
Priority: normal Milestone:
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

It's a popular client. We should configure it for people.

Change History

comment:1 Changed 12 years ago by broder

Here's the information we've gathered so far, just so it's sitting with the ticket.

Note that pre-Gutsy there was only an /etc/Muttrc; Gutsy and later have /etc/Muttrc.d

It sounds like the bare-minimum configuration we need here is just to add the following:

set spoolfile="imap://$USER@`hesinfo $USER pobox | awk '{print $2}'`"

However, the sipb locker mutt sets a bunch more options (/mit/sipb/etc/Muttrc-1.5.12). Stripping out comments and blanks, we're left with:

ignore "from " received content- mime-version status x-status message-id
ignore sender references return-path lines
macro index \eb "<search>~b " "search in message bodies"
macro index,pager \cb "<pipe-message>urlview<Enter>" "call urlview to extract URLs out of a message"
macro generic,pager <F1> "<shell-escape>less /mit/sipb/arch/sun4x_510/lib/mutt-1.5.12/doc/mutt/manual.txt<Enter>" "show Mutt documentation"
macro index,pager y "<change-folder>?<toggle-mailboxes>" "show incoming mailboxes list"
bind browser y exit
attachments   +A */.*
attachments   -A text/x-vcard application/pgp.*
attachments   -A application/x-pkcs7-.*
attachments   +I text/plain
attachments   -A message/external-body
attachments   -I message/external-body
set folder="imap://$USER@`hesinfo $USER pobox | awk '{print $2}'`"
set imap_headers="X-Spam-Score"
set query_command = "athrun sipb mutt_ldap_query.pl %s"
set record=""
set sort=threads
set spoolfile="imap://$USER@`hesinfo $USER pobox | awk '{print $2}'`"
set use_domain=no
spam "X-Spam-Score:.(.*)" "%1"

I don't really know what all of these mean. Some of them look like they make sense, e.g. the X-Spam-Score settings. Some of them look like what amounts to personal preference.

comment:2 Changed 12 years ago by price

  • Status changed from new to assigned
  • Owner set to price

I'm a mutt user and can take this ticket.

Some of the lines there are things you really want in order to use mutt. (I'm imagining mutt with no "ignore received" -- ouch.) Thankfully there's no need to go pursue an upstream bug -- they're already in /etc/Muttrc.

I'll look at the rest and identify what this Muttrc adds and which of that we want.

comment:3 Changed 12 years ago by broder

  • Keywords proposed added
  • Component set to default

debathena-mutt-config is in -proposed, as is a new version of debathena-clients that recommends it.

I'm not really concerned about the fact that this might not work on Gutsy, because the worst case scenario is that we fail to change the current behavior.

As this is a "new feature", I'm going to keep it in -proposed for a week. I'll plan to move it to production on April 9, if there are no objections.

comment:4 Changed 12 years ago by broder

  • Keywords proposed removed
  • Resolution set to fixed
  • Status changed from assigned to closed
  • Component set to --

This was just moved into production.

Note: See TracTickets for help on using tickets.