From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: coding in some mails is wired
Date: Wed, 26 Jul 2023 14:16:10 +0200 [thread overview]
Message-ID: <877cqmq35h.fsf@mat.ucm.es> (raw)
In-Reply-To: <87cz0fj898.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1527 bytes --]
>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Wed, 26 Jul 2023 10:19:48 +0100, Eric S Fraga <e.fraga@ucl.ac.uk> said:
Eric> On Wednesday, 26 Jul 2023 at 11:03, Uwe Brauer wrote:
>>> Here it is
Eric> Applying munpack (on Linux) to the contents of that file indicates there
Eric> is nothing to unpack. Looking at the file contents, the only suspicious
Eric> line is the one with "boundary=" which has a single space at the start.
Eric> Deleting the single space fixes it and munpack finds three mime parts,
Eric> although the third one consists of a single character (line feed alone,
Eric> I think).
I am confused, I tried to follow Roberts instructions:
,----
|
| gnus-default-article-saver is a variable defined in ‘gnus-art.el’.
|
| Its value is ‘gnus-summary-save-in-mail’
| Original value was
| ‘gnus-summary-save-in-rmail’
`----
So I saved that message in file, put that file in a new subdirectory,
tarred and gziped that directory. What else should I have done?
Here are the screenshots of the this message together with a third
screenshot after applying command gnus-summary-repair-multipart
--
Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the NATO membership of the Ukraine.
I support the EU membership of the Ukraine.
https://addons.thunderbird.net/en-US/thunderbird/addon/gmail-conversation-view/
[-- Attachment #1.2: coding-correct.png --]
[-- Type: image/png, Size: 242438 bytes --]
[-- Attachment #1.3: coding2.png --]
[-- Type: image/png, Size: 346480 bytes --]
[-- Attachment #1.4: coding1.png --]
[-- Type: image/png, Size: 305804 bytes --]
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2023-07-26 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 7:49 Uwe Brauer
2023-07-25 9:57 ` Robert Pluim
2023-07-25 12:28 ` Uwe Brauer
2023-07-25 13:24 ` Robert Pluim
2023-07-25 17:46 ` Uwe Brauer
2023-07-25 20:49 ` Robert Pluim
2023-07-26 9:03 ` Uwe Brauer
2023-07-26 9:19 ` Eric S Fraga
2023-07-26 10:07 ` Robert Pluim
2023-07-26 10:21 ` Eric S Fraga
2023-07-26 12:16 ` Uwe Brauer [this message]
2023-07-26 12:58 ` Robert Pluim
2023-07-26 16:59 ` Uwe Brauer
2023-07-27 7:15 ` Robert Pluim
2023-07-29 5:55 ` Uwe Brauer
2023-07-25 16:21 ` Andreas Schwab
2023-07-25 17:46 ` Uwe Brauer
2023-07-25 17:50 ` 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=877cqmq35h.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).