From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: how to forward a message that contains attachment
Date: Sun, 05 Apr 2020 08:07:34 +0200 [thread overview]
Message-ID: <87eet2qxcp.fsf@mat.ucm.es> (raw)
In-Reply-To: <CADoYgq-tgQJVRA=jJxXhkF7YaFuqwJqaep7px1Atdt-hQB76wQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]
>>> "BN" == Bob Newell <bobnewell@bobnewell.net> writes:
>> The message is forwarded, the attachments not
> So this is how I do it, not completely ideal but working for me, your
> mileage will vary.
> ;;; There is no forward key in the article buffer, so make one.
> ;;; Oddly gnus-summary-mail-forward seems to work correctly.
> (define-key gnus-article-mode-map "\C-c\C-f" 'gnus-summary-mail-forward)
> ;;; Make summary forwarding behave a little better. This also makes
> ;;; message forwarding and summary forwarding consistent. But note that
> ;;; if you wish to forward an attachment you must use M-2\C-c\C-f.
> (setq message-forward-as-mime nil)
> (setq message-forward-show-mml nil)
> (setq message-forward-included-headers "^Date\\|^From\\|^To\\|^Subject:")
> M-2\C-c\C-f unfortunately makes the whole message multipart (not just
> the attachments). I have to yet to figure out how to put the message
> inline and make the attachments a MIME part.
Hi
I found your webpage a couple of days ago and tried it out. Surprise:
it does not work in the following sense.
1. When opening the message with the latest seamonkey (which is
basically firefox+thunderbird), the message is *not* displayed
and no attachment is seen
2. In the web interface of gmail it is even worse:
I see stuff like this
Uwe Brauer <oub@mat.ucm.es>
8:02 AM (2 minutes ago)

to Uwe

RGVsaXZlcmVkLVRvOiBvdWJAbWF0LnVjbS5lcwpSZWNlaXZlZDogYnkgMjAwMjphMTc6OTA2Ojdm
OTI6MDowOjA6MCB3aXRoIFNNVFAgaWQgZjE4Y3NwNzE5NTAyZWpyOyBGcmksIDMKIEFwciAyMDIw
IDA5OjU2OjUzIC0wNzAwIChQRFQpClgtUmVjZWl2ZWQ6IGJ5IDIwMDI6YTFjOmRjNTU6OiB3aXRo
IFNNVFAgaWQgdDgybXI5NDU5ODM4d21nLjYuMTU4NTkzMjk5Njg4OTsKIEZyaSwgMDMgQXByIDIw
MjAgMDk6NTY6MzYgLTA3MDAgKFBEVCkKQVJDLVNlYWw6IGk9MTsgYT1yc2Etc2hhMjU2OyB0PTE1
ODU5MzI5OTY7IGN2PW5vbmU7IGQ9Z29vZ2xlLmNvbTsKIHM9YXJjLTIwMTYwODE2OwogYj1CbGZG
Which looks like base64 encoding.
In gnus, the message is displayed
[[S/MIME Signed Part:Good signature from 285DB563F3701BD406D4FD057AA02D6E9200635A /CN=BRAUER UWE RICHARD OTTO - X2064123B/C=ES/SN=BRAUER/GN=UWE RICHARD OTTO/SerialNumber=IDCES-X2064123B (trust full)]]
[[End of S/MIME Signed Part]]
So something is very odd here.
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-04-05 6:08 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 [this message]
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
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=87eet2qxcp.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).