Ticket #129 (closed enhancement: fixed)
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:2 Changed 16 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 16 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.
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:
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:
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.