From 1367fd4246716e3f693f8a1d70630c438489ce03 Mon Sep 17 00:00:00 2001 From: Robin Jarry Date: Wed, 25 Jan 2023 01:11:52 +0100 Subject: compose: allow sending format=flowed messages Allow composing and sending messages with: Content-Type: text/plain; Format=Flowed This requires additional configuration in the text editor to actually produce the required trailing spaces at the end of lines that are part of the same paragraph. For example, with vim: "~/.vim/ftplugin/mail.vim setlocal textwidth=72 setlocal formatoptions=1jnwtcql setlocal comments+=nb:> Link: https://www.rfc-editor.org/rfc/rfc3676.html Signed-off-by: Robin Jarry Tested-by: Moritz Poldrack --- doc/aerc-config.5.scd | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'doc') diff --git a/doc/aerc-config.5.scd b/doc/aerc-config.5.scd index 22c3a40a..74481b10 100644 --- a/doc/aerc-config.5.scd +++ b/doc/aerc-config.5.scd @@ -563,6 +563,15 @@ These options are configured in the *[compose]* section of _aerc.conf_. Example: *no-attachment-warning* = _^[^>]\*attach(ed|ment)_ +*format-flowed* = _true_|_false_ + When set, aerc will generate _Format=Flowed_ bodies with a content type + of _"text/plain; Format=Flowed"_ as described in RFC3676. This format is + easier to handle for some mailing software, and generally just looks + like ordinary text. To actually make use of this format's features, + you'll need support in your editor. + + Default: _false_ + # MULTIPART CONVERTERS Converters allow generating _multipart/alternative_ messages by converting the -- cgit