Ticket #1342 (new defect)

Opened 11 years ago

Last modified 11 years ago

Mutt "record" option incorrect for Exchange users

Reported by: rakavan Owned by:
Priority: normal Milestone: Current Semester
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

Mutt's "record" option (where mutt stores "sent mail") is incorrect for those using Exchange. I will provide a patch in a few minutes. It should be set to '+Sent Items' rather than "+INBOX.sent-mail".

Attachments

mutt-config.diff Download (2.2 KB) - added by rakavan 11 years ago.
mutt-config2.diff Download (2.9 KB) - added by rakavan 11 years ago.
mutt-config3.diff Download (3.0 KB) - added by rakavan 11 years ago.
Updated patch to use a DNS lookup instead of chpobox

Change History

Changed 11 years ago by rakavan

comment:1 Changed 11 years ago by jdreed

  • Milestone changed from The Distant Future to Summer 2013

Yeah, Pine is wrong too. We need to fix all the mail clients.

comment:2 Changed 11 years ago by rakavan

Hmm, replying to tickets by email doesn't seem to update the ticket proper. Here's the reply:

On Fri, May 03, 2013 at 09:31:34PM -0400, Jonathan D Reed wrote:

Sure, fixing Drafts and other folders would be good.

I've centralized it all in one script, debathena-mutt-folders, which sets the
folder, postponed, record, and spoolfile options based on whether the user is
using Exchange or IMAP. See the attached patch.

Best wishes,
Ryan

Changed 11 years ago by rakavan

comment:3 follow-up: ↓ 4 Changed 11 years ago by geofft

chpobox does a query against Moira, which isn't high-availability or particularly a fan of automated traffic. It also doesn't account for users with mail split between Exchange and an external address. We can either look up what $user.mail.mit.edu resolves to, or do a Hesiod query for hesinfo $user pobox as e.g. /usr/bin/alpine.debathena does, and test to see if that contains the string "EXCHANGE". Do you want to update the patch to do one of those?

I haven't tested the patch or evaluated it other than this, because I don't use mutt. It looks basically reasonable, though.

For the alpine version of this problem, while alpine doesn't have an executable config file format, /etc/pine.conf and ~/.pinerc do interpolate environment variables, and we already use this by making sure $ATHENA_USER is appropriately set in the alpine wrapper script and then using that. We could make environment variables for the folder names in the wrapper script.

Do we care about the transition here, and that the sent mail directory in the UI (for alpine, at least) will show up empty after this config gets deployed? We could decide to attempt to only make this take effect for new users -- there's a good chance essentially no prefrosh have attempted to use alpine or mutt right yet, so changing it for new users only would be pretty useful right now.

comment:4 in reply to: ↑ 3 Changed 11 years ago by rakavan

Replying to geofft:

Do you want to update the patch to do one of those?

Sure, I'll try to get that done later on today.

Do we care about the transition here, and that the sent mail directory in the UI (for alpine, at least) will show up empty after this config gets deployed? We could decide to attempt to only make this take effect for new users -- there's a good chance essentially no prefrosh have attempted to use alpine or mutt right yet, so changing it for new users only would be pretty useful right now.

Unless a mutt user has customised the relevant settings in ~/.muttrc, the above patch should "just work": mutt doesn't have a menu option to select the "Sent Mail" folder. When users go to switch directories and view the list (keybinding "c?"), they'll see the old INBOX.sent-mail folders, and the new "Sent Items" folder. Whether or not they're made aware to look in "Sent Items" for sent mail is another question.

comment:5 Changed 11 years ago by geofft

Hm, I guess alpine also works the same way, in that the Fcc folder is just used when sending mail, and you manually navigate to the appropriate sent-mail folder. What about Thunderbird and Evolution, which we also configure? I vaguely feel like it's worth being consistent between the clients, although e.g. jdreed might have stronger opinions about this (he's on vacation at the moment unfortunately).

Changed 11 years ago by rakavan

Updated patch to use a DNS lookup instead of chpobox

Note: See TracTickets for help on using tickets.