From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: coding in some mails is wired
Date: Tue, 25 Jul 2023 11:57:34 +0200 [thread overview]
Message-ID: <87tttsjott.fsf@gmail.com> (raw)
In-Reply-To: <875y682zy2.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 25 Jul 2023 09:49:25 +0200")
>>>>> On Tue, 25 Jul 2023 09:49:25 +0200, Uwe Brauer <oub@mat.ucm.es> said:
Uwe> Hi
Uwe> Since a couple of weeks I receive some mails how look like this
Uwe> ,----
Uwe> |
Uwe> | From: user <XXX@mathworks.com>
Uwe> | Subject: RE: the filling patch and its problems
Uwe> | To: Uwe Brauer <oub@mat.ucm.es>
Uwe> | CC: Matlab-emacs-discuss <matlab-emacs-discuss@lists.sourceforge.net>
Uwe> | Date: Mon, 24 Jul 2023 19:08:34 +0000 (12 hours, 32 minutes, 22 seconds ago)
Uwe> |
Uwe> |
Uwe> | --_004_mn2pr05mb65581320f9aede6160120580af02amn2pr05mb6558namp_
Uwe> | Content-type: multipart/alternative; boundary="_000_mn2pr05mb65581320f9aede6160120580af02amn2pr05mb6558namp_"
Uwe> |
Uwe> |
Uwe> | --_000_mn2pr05mb65581320f9aede6160120580af02amn2pr05mb6558namp_
Uwe> | Content-type: text/plain; charset="utf-8"
Uwe> | Content-transfer-encoding: base64
Uwe> |
Uwe> | SGkgVXdlLA0KDQpIZXJl4oCZcyBhIHJldmlzZWQgcGF0Y2ggdGhhdCBkb2VzIGEgYmV0dGVyIGpv
Uwe> | YiBmaWxsaW5nIGNvbW1lbnRzLCBhbmQgYWxzbyBmaXhlcyB0aGUgaW5kZW50IHJlZ2lvbiBpc3N1
Uwe> | ZSB5b3UgZm91bmQuDQoNCkhvcGUgdGhlc2Ugd29yayBmb3IgeW91Lg0KRXJpYw0KDQpGcm9tOiBV
Uwe> `----
Uwe> This mail is perfectly displayed for example in the gmail webinterface.
Uwe> I did not change anything in my gnus configuration.
Uwe> Any idea how to deal with these sort of emails?
Uwe> It is mainly email from mathwork but also from other providers and the
Uwe> number is increasing
Uwe> So any help would be highly appreciated.
Which version of emacs/gnus? Would you have a complete example
including headers? Itʼs possible gnusʼ multipart decoding has a bug,
but weʼd need a complete message to confirm.
Robert
--
next prev parent reply other threads:[~2023-07-25 9:58 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 [this message]
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
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=87tttsjott.fsf@gmail.com \
--to=rpluim@gmail.com \
--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).