[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Sending Binary Attachments
From: |
Ken Hornstein |
Subject: |
Re: [Nmh-workers] Sending Binary Attachments |
Date: |
Fri, 13 May 2016 10:21:09 -0400 |
>First of all, *thanks* for the note about the 998 max. I've
>updated my .mh_profile.
Just so we're clear ... I hope you either removed it completely, or
upgraded to 1.6 and changed it to 998. Also, I think that there's
mostly no reason you should worry about sending stuff out that is
encoded quoted-printable. I mean, you were able to reply to my message
that was encoded as quoted-printable and the world did not end.
Although you might want to consider upgrading to 1.6, as the message you
sent out was actually not MIME-compliant and 1.6 would have fixed that.
For reasons I cannot explain, my message contained a NO-BREAK space in
it, but it looks like the mailing list software helpfully re-encoded
your reply to it as quoted-printable. (Huh, I guess the answer is I get
a no-break space if I hold down the "Option" key when I hit the space
bar).
--Ken
- Re: [Nmh-workers] Sending Binary Attachments, (continued)
Re: [Nmh-workers] Sending Binary Attachments, Ken Hornstein, 2016/05/12
- Re: [Nmh-workers] Sending Binary Attachments, Martin McCormick, 2016/05/12
- Re: [Nmh-workers] Sending Binary Attachments, Bob Carragher, 2016/05/12
- Re: [Nmh-workers] Sending Binary Attachments, Ken Hornstein, 2016/05/12
- Re: [Nmh-workers] Sending Binary Attachments, Bob Carragher, 2016/05/13
- Re: [Nmh-workers] Sending Binary Attachments,
Ken Hornstein <=
- Re: [Nmh-workers] Sending Binary Attachments, Bob Carragher, 2016/05/13
- Re: [Nmh-workers] Sending Binary Attachments, Ralph Corderoy, 2016/05/14