From: "Francesco Potortì" <pot@gnu.org>
To: Bob Rogers <rogers@rgrjr.com>
Cc: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>,
"Alfred M. Szmidt" <ams@gnu.org>
Subject: Re: rmail and mime encoded patches annoyance
Date: Sun, 21 May 2023 02:46:24 +0200 [thread overview]
Message-ID: <875y8mcxzz.fsf@tucano.isti.cnr.it> (raw)
In-Reply-To: <25703.43394.220788.296630@orion.rgrjr.com> (rogers@rgrjr.com)
> From: "Alfred M. Szmidt" <ams@gnu.org>
> Date: Fri, 19 May 2023 07:39:31 -0400
>
> A _very_ ugly solution.
>
> Edit the message in question, remove the MIME-Version: field, convert
> the sections you care about using base64-decode-region. Save. Rmail
> will complain slightly about the message not being a valid MIME
> message, but .. meh.
Bob Rogers:
>Seems to me that all you really need to do is to convert the
>content-transfer-encoding of the attachment from "base64" to (say)
>"8bit" to make it readable, in which case it would still be valid MIME.
I have routinely done something like that using macros for the last several years.
When I receive email with attached files that I need, I save the files where they belong, then I edit the email to remove the attachments and ubstitutte them with text placeholders containing the file names. Then I archive the email, which is now much smaller than the original. I have a macro which does this work for me in most common cases, and a couple of additional macros which care about converting base64 to utf-8 in some corner cases.
prev parent reply other threads:[~2023-05-21 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:11 rmail and mime encoded patches annoyance Alfred M. Szmidt
2023-05-19 6:45 ` Eli Zaretskii
2023-05-19 7:17 ` Alfred M. Szmidt
2023-05-19 10:51 ` Eli Zaretskii
2023-05-19 11:08 ` Alfred M. Szmidt
2023-05-19 11:25 ` Eli Zaretskii
2023-05-19 11:31 ` Alfred M. Szmidt
2023-05-19 11:38 ` Eli Zaretskii
2023-05-19 11:39 ` Alfred M. Szmidt
2023-05-19 16:53 ` Bob Rogers
2023-05-21 0:46 ` Francesco Potortì [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y8mcxzz.fsf@tucano.isti.cnr.it \
--to=pot@gnu.org \
--cc=ams@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rogers@rgrjr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.