Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: coding in some mails is wired
Date: Wed, 26 Jul 2023 10:19:48 +0100	[thread overview]
Message-ID: <87lef381xn.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87cz0foxi7.fsf@mat.ucm.es>

On Wednesday, 26 Jul 2023 at 11:03, Uwe Brauer wrote:
> Here it is 

Applying munpack (on Linux) to the contents of that file indicates there
is nothing to unpack.  Looking at the file contents, the only suspicious
line is the one with "boundary=" which has a single space at the start.
Deleting the single space fixes it and munpack finds three mime parts,
although the third one consists of a single character (line feed alone,
I think).

Why there is a space at the start of the boundary line is unclear and
whether this should be allowed or not is beyond my mime-fu.

HTH,
eric

-- 
Eric S Fraga via gnus (Emacs 30.0.50 2023-07-19) on Debian 12.0



  reply	other threads:[~2023-07-26  9:20 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 [this message]
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=87lef381xn.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).