diff options
| author | Karel Balej <balejk@matfyz.cz> | 2024-01-30 20:11:29 +0100 |
|---|---|---|
| committer | Robin Jarry <robin@jarry.cc> | 2024-02-12 23:05:53 +0100 |
| commit | 3aa8b6308482d2e3feea0fecb065190cf05c2468 (patch) | |
| tree | 99e9d3c9f9b6a65beb7c3a8c981e2dc795d8b845 /doc | |
| parent | e8a6e8316a4b6e923f75b1e9a2d06089033e480b (diff) | |
| download | aerc-3aa8b6308482d2e3feea0fecb065190cf05c2468.tar.gz | |
commands: add bounce
Add a command to allow for reintroduction of messages into the transport
system. This means taking a message and forwarding it to new recipients
as is including original headers. The fact that the message has been
bounced is indicated by the prepend of *Resent-* headers in accordance
with RFC 2822. The bounced message is not stored in the sent mailbox.
Also add an `-A` switch to allow for bouncing using different account
than the one currently selected.
Also add default keybind and documentation entry for this command.
The mentioned RFC also recognizes *Resent-Cc* and *Resent-Bcc* headers
which might be an interesting continuation of this -- currently all
recipients are specified in *Resent-To*. Also more control over the
*Resent-From* header value could be implemented.
This command is strongly inspired by (neo)mutt's `bounce`.
Implements: https://todo.sr.ht/~rjarry/aerc/115
Changelog-added: `:bounce` command to reintroduce messages into the
transport system.
Signed-off-by: Karel Balej <balejk@matfyz.cz>
Acked-by: Robin Jarry <robin@jarry.cc>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/aerc.1.scd | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/aerc.1.scd b/doc/aerc.1.scd index e3079090..e4a3305f 100644 --- a/doc/aerc.1.scd +++ b/doc/aerc.1.scd @@ -504,6 +504,22 @@ message list, the message in the message viewer, etc). _<body>_: The initial message body. +*:bounce* [*-A* _<account>_] _<address>_ [_<address>_...]++ +*:resend* [*-A* _<account>_] _<address>_ [_<address>_...] + Bounce the selected message or all marked messages to the specified addresses, + optionally using the specified account. This forwards the message while + preserving all the existing headers. The new sender (*From*), date (*Date*), + *Message-ID* and recipients (*To*) are prepended to the headers with the *Resent-* + prefix. For more information please refer to section 3.6.6 of RFC 2822. Note + that the bounced message is not copied over to the *sent* folder. + + Beware that at least the _msmtp_ sendmail implementation does not consider + the *Resent-From* header when invoked with _--read-envelope-from_. + + Also please note that some providers (notably for instance Microsoft's + O365) do not allow sending messages with the *From* header not matching + any of the account's identities (even if *Resent-From* matches some). + *:recover* [*-f*] [*-e*|*-E*] _<file>_ Resume composing a message that was not sent nor postponed. The file may not contain header data unless *[compose].edit-headers* was enabled when |