When I press S
in mutt, it saves the mail to a mail folder format (cur/ tmp/ new/
), but I want a single file to be saved, just like how attachments are saved.
Is that configurable?
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.
Sign up to join this communityThe s
command saves to a mailbox, which for you is in maildir format. Unfortunately, there is no save-to-file command, perhaps because in the historical mbox format, a mailbox that contains a single mail is just a file containing that mail.
The mutt
command pipe-message (default shortcut |
) can be used for this. It opens a command line and you write cat > DESIRED-FILE-PATH
.
The "pipe-decode" option controls what happens to headers and mime parts when you save a message this way.
One could probably write a macro for this functionality.
set pipe_decode=yes
to my muttrc was what Kai von Fintel was writing about.
May 1, 2015 at 13:36
=
doing this.
Aug 23, 2019 at 11:18
The actual message shows up as an attachment as well, so you can save it from the attachment list. From either the index or the message itself, hit v to open the attachments and s to save
h
to show them, first...
h
just shows all the headers. Either way, the headers aren't saved.
|
key and use a linux command to store the mail, as described in the answer of Kai von Fintel. Also setting the set pipe_decode=yes
should not be omitted in the .muttrc
If you touch
a file and then try to save or copy a message to it mutt will use it as a mbox.
Also you might want to use copy instead of save. Mutt assumes that a mail should only exist in one copy and saving a message to another mailbox will delete it from the first one, while copying will do a proper copy.
Kai von Fintel's answer works perfectly, but I just thought I'd share a macro to streamline this process.
Firstly, in muttrc
:
macro index,pager S "| ~/.local/bin/file_email /tmp<enter>"
This pipes the full email (including headers and attachments) to the following script. Create an executable file at ~/.local/bin/file_email
.
#!/usr/bin/env bash
# Save piped email to "$1/YYMMDD SUBJECT.eml"
# Don't overwrite existing file
set -o noclobber
message=$(cat)
mail_date=$(<<<"$message" grep -oPm 1 '^Date: ?\K.*')
formatted_date=$(date -d"$mail_date" +%y%m%d)
# Get the first line of the subject, and change / to ∕ so it's not a subdirectory
subject=$(<<<"$message" grep -oPm 1 '^Subject: ?\K.*' | sed 's,/,∕,g')
if [[ $formatted_date == '' ]]; then
echo Error: no date parsed
exit 1
elif [[ $subject == '' ]]; then
echo Warning: no subject found
fi
echo "${message}" > "$1/$formatted_date $subject.eml" && echo Email saved to "$1/$formatted_date $subject.eml"
This script saves the file to the first argument (i.e. in the muttrc
example above, the email will save to /tmp
). The format of the file name is YYMMDD SUBJECT.eml
. It also converts /
to ∕
to prevent creating subdirectories.
formail
, so I had a read. However, I'm not entirely sure which part of my script you were referring to? Using formail
to extract subject and date? If so, probably a nice idea. I'd urge you to write an answer; I'd definitely upvote it.
I have tried all the suggested answers but could not get the raw, multipart (text/plain + text/html) e-mail to be saved to a file, including it's headers and everything. I needed this to feed my spam-filter with the e-mail to teach it, that a specific mail is spam or not...
The solution I came up with is pressing e
(i.e. "edit message") on the open message, which opens the raw message in your editor of choice. Raw here means, that you get the message exactly as it arrived in mutt, so you have all the headers and all the bytes that comprise the message.
After hitting e
, I just write the buffer (I set editor to vim) to a file with :w <path_to_file>/<file_name>
and that's it.
P.S: I would have added this as comment but you need a certain level of reputation to do this. Also, I know the question is very old but as neomutt is still used by many people, I thought this might help someone.
Update: I overlooked the pipe-decode
option that Kai was talking about. With that option set correctly it would have worked via |
, too. Still my solution is working, too ;-)
set pipe_decode=yes
in your .muttrc however.