[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [nmh-workers] mhshow: invalid BASE64 encoding in --
From: |
David Levine |
Subject: |
Re: [nmh-workers] mhshow: invalid BASE64 encoding in -- |
Date: |
Sun, 17 Mar 2019 09:28:53 -0400 |
Valdis wrote:
> that maybe if we're looking at base64, if we encounter a blank line we toss
> the
> rest of the body part.
That would work in this case, but the mailing list should be fixed. More
generally, what if a sender (improperly) had annotated an already encoded
message with, say, "DO NOT FORWARD THIS!"? Bad, yes, but could lead to
undesired results if that was dropped.
In other words, I'd like to see all of the content or an error message.
David
- [nmh-workers] mhshow: invalid BASE64 encoding in --, Anthony J. Bentley, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, Valdis Klētnieks, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --,
David Levine <=
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, lambda, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, Valdis Klētnieks, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, Ken Hornstein, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, Valdis Klētnieks, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, David Levine, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, Ken Hornstein, 2019/03/17
- Re: [nmh-workers] mhshow: invalid BASE64 encoding in --, David Levine, 2019/03/17