IMAP: Mutt fails to save sent messages when drafted by a different IMAP client

Bug #444735 reported by lunch
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mutt (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: mutt

mutt:
  Installed: 1.5.17+20080114-1ubuntu1
  Candidate: 1.5.17+20080114-1ubuntu1
  Version table:
 *** 1.5.17+20080114-1ubuntu1 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Description: Ubuntu 8.04.3 LTS
Release: 8.04

For a given IMAP account, when a message is drafted by a client other than mutt, and then that same message is recalled by mutt, edited, and sent, the final message is not saved in the $record mailbox. It is silently lost. This happens even though $record is properly set and email drafted and sent with mutt exclusively is properly saved.

To reproduce:
1. Draft an email in an IMAP account with a client other mutt, e.g. thunderbird or webmail.
2. Save the draft in the drafts folder. This folder should be be the same as $postponed in muttrc
3. recall the drafted email using mutt
4. send the email
5. the email is silently lost and fails to be saved in $record

It is not uncommon to use multiple different clients with an IMAP account (e.g. webmail, mutt, thunderbird).

Revision history for this message
lunch (launch-mailinator-com) wrote :

One workaround for this would be to create a separate drafts folder that is specifically mutt's. But this breaks the client-neutral nature of IMAP. And RFC 2683 addresses such interoperability concerns stating that the name for special use folders such as 'drafts' or Sent mail' should be the same across clients if so desired.

"In addition, the client developer should provide a convenient way for
the user to select the names for any special-use mailboxes, allowing
the user to make these names the same in all clients used and to put
them where the user wants them."

(See ftp://ftp.rfc-editor.org/in-notes/rfc2683.txt)

Revision history for this message
Andrew McCarthy (andrewmccarthy) wrote :

I agree this is very unexpected, and undesirable, behaviour but the Mutt developers disagree: http://dev.mutt.org/trac/ticket/3323 . They say that $record is stored in the postponed folder, and if the other client doesn't save it there, mutt doesn't create one when you resume composing.

You might be able to make something up using send2_hook, but I haven't tried.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mutt (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.