[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191014121212.GK16318@brightrain.aerifal.cx>
Date: Mon, 14 Oct 2019 08:12:12 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Re: [PATCH] Use open_memstream(3) for more efficient
asprintf
On Mon, Oct 14, 2019 at 02:56:36AM -0400, Alex Brachet-Mialot wrote:
> That's strange, I looked on the archives and it looks like my
> attachment was in a weird format, something my email client did
> perhaps. Here it is copied I'll also try again with .txt extension so
> my mail client is less confused hopefully. Sorry about that.
It came through ok -- the attachment was just marked as a binary file
rather than text. If your mailer can send text attachments without
mangling the content, it's preferable to send as text so that
archive/recipients' mail software will show them, but either is okay
and binary (application/octet-streaam) can be better if you're at all
worried that your mailer will mess things up, e.g. replacing tabs with
spaces.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
