From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: how to forward a message that contains attachment
Date: Mon, 06 Apr 2020 13:36:53 +0200 [thread overview]
Message-ID: <87tv1wzvze.fsf@mat.ucm.es> (raw)
In-Reply-To: <87ftdhx29r.fsf@tullinup.koldfront.dk>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
>>> "AS" == Adam Sjøgren <asjo@koldfront.dk> writes:
> Uwe writes:
>> I have the feeling the forward function worked better some years ago.
>> Not sure what happened.
> For anyone to help you figure out the problem, I suggest you create a
> recipe that shows the problem, so other people can try to reproduce the
> problem.
I just compiled GNU emacs from today master.
Then simple gnus-summary-mail-forward (with no arguments) behaves as
expected, while the version from august does not.
However this version from today cannot display smime signed messages
correctly.
Well I have to pin this down.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2020-04-06 11:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 14:33 Uwe Brauer
2020-04-04 14:54 ` Eric S Fraga
2020-04-04 18:57 ` Uwe Brauer
2020-04-05 2:00 ` Bob Newell
2020-04-05 6:07 ` Uwe Brauer
2020-04-05 19:31 ` Bob Newell
2020-04-05 13:18 ` Eric S Fraga
2020-04-05 17:11 ` Uwe Brauer
2020-04-05 17:37 ` Adam Sjøgren
2020-04-05 21:25 ` dick.r.chiang
2020-04-06 10:19 ` gmail setup (was: how to forward a message that contains attachment) Alberto Luaces
2020-04-07 16:42 ` gmail setup dick.r.chiang
2020-04-07 17:46 ` Alberto Luaces
2020-04-07 18:19 ` dick.r.chiang
2020-04-07 18:35 ` Alberto Luaces
2020-04-08 1:53 ` Bob Newell
2020-04-10 16:56 ` Alberto Luaces
2020-04-06 10:19 ` how to forward a message that contains attachment Uwe Brauer
2020-04-06 10:26 ` Uwe Brauer
2020-04-07 17:03 ` Adam Sjøgren
2020-04-06 11:36 ` Uwe Brauer [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=87tv1wzvze.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).