Re: fcc and external attachments

[David Bremner <david@tethera.net>]

Alfredo Finelli <alf@computationes.de> writes:

> Since notmuch version 0.35 the emacs interface is not respecting this
> configuration variable setting any more:
>
>   (setq message-fcc-externalize-attachments t)
>
> With earlier versions I used to get fcc copies in my sent folder where
> each attachment was replaced by a reference to the external file that was
> attached (Content-Type: message/external-body, etc.).  After upgrading to
> 0.35, without changing the configuration, the fcc copies of sent messages
> include instead the complete attachments.
>
> I am not sure if this is a bug or if my configuration is not supported any
> more.

It seems likely this is an unintended consequence of
da302e1cbaaab89b2bbb32c0f59e1aa6ee708455.

Since notmuch-emacs does it's own Fcc processing, it's a bit
hit-and-miss whether a given message-fcc-* variable is respected. I'll
have a look at how hard it is to fix, but first I need a reliable recipe
for triggering the externalization in message-mode (i.e. without
involving notmuch).  I tried in emacs -q, customize
message-fcc-externalize-attachments, and running M-x compose-mail, but
that still saved the whole attachments. Maybe it was the type of
attachement or something, I don't understand it yet.

d