Github messages for mblaze
 help / color / mirror / Atom feed
From: ashiire <ashiire@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: improve named part/attachment detection
Date: Sun, 12 Feb 2023 11:38:59 +0100	[thread overview]
Message-ID: <20230212103859.MEQ5oKS1KZBl2fX9_41CkUayoumLY1M-1PNgnx2T8mc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-232@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]

New comment by ashiire on mblaze repository

https://github.com/leahneukirchen/mblaze/pull/232#issuecomment-1426997809

Comment:
Fabricated example of the behavior in question.

```
$ ls mail_s_poezii.txt | mshow -t
mail_s_poezii.txt
  1: multipart/mixed size=825
    2: text/plain size=30
    3: text/plain size=53 name="kocka_leze_dirou.txt"
    4: text/plain size=98
$ ls mail_s_poezii.txt | mshow-patched -t
mail_s_poezii.txt
  1: multipart/mixed size=825
    2: text/plain size=30
    3: text/plain size=53 name="kocka_leze_dirou.txt"
    4: text/plain size=98 name="za_pravdu_je_ruzna_sazba.txt"
```

file contents:
```
From: Petr Klic <p.klic@example.com>
To: <umeni@example.com>
Subject: Poezie
Date: Wed, 14 Oct 2020 12:18:08 +0200
Message-ID: <setrise3750@example.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="----=_NextPart_000_00DE_01D6A2E8.A7446C80"
Content-Language: cs

This is a multipart message in MIME format.

------=_NextPart_000_00DE_01D6A2E8.A7446C80
Content-Type: text/plain;
        charset="UTF-8"
Content-Transfer-Encoding: 8bit


Dobry den,

posilam poezii.


------=_NextPart_000_00DE_01D6A2E8.A7446C80
Content-Type: text/plain;
        charset="UTF-8";
        name="kocka_leze_dirou.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
        filename="kocka_leze_dirou.txt"

kocka leze dirou
pes oknem
nebude-li prset
nezmoknem

------=_NextPart_000_00DE_01D6A2E8.A7446C80
Content-Type: text/plain;
        charset="UTF-8";
        name="za_pravdu_je_ruzna_sazba.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment

za pravdu je ruzna sazba
nekdy pomnik
jindy vazba
kdo ji rika driv nez vcas
tomu pravda
zlame vaz

------=_NextPart_000_00DE_01D6A2E8.A7446C80--
```

       reply	other threads:[~2023-02-12 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-232@inbox.vuxu.org>
2023-02-12 10:38 ` ashiire [this message]
2023-08-11 11:37 ` ashiire
2023-08-11 13:31 ` leahneukirchen
2023-08-16 11:09 ` [PR PATCH] [Updated] " ashiire
2023-08-16 14:46 ` ashiire

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=20230212103859.MEQ5oKS1KZBl2fX9_41CkUayoumLY1M-1PNgnx2T8mc@z \
    --to=ashiire@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).