jstedfast / MimeKit

0%

master: 94%

LAST BUILD ON BRANCH binary-quoted-printable-decoder

branch: binary-quoted-printable-decoder

CHANGE BRANCH

x

Reset

• binary-quoted-printable-decoder
• HEAD
• bouncycastle2.0
• core
• crypto-abstractions
• dependabot/nuget/System.Memory-4.5.5
• dependabot/nuget/nunit-4.0.0
• hwaccel-base64
• issue682
• master
• mime-compliance
• mime-compliance-violations
• mime-compliance2
• mimereader
• mimereader-span
• mimereader-span2
• nullable-api
• nullable-api2
• parser-options-create
• refs/pull/1072/merge
• refs/pull/1162/merge
• refs/pull/1163/merge
• refs/pull/1176/merge
• refs/pull/1205/merge
• refs/tags/2.12.0
• refs/tags/3.3.0
• refs/tags/3.4.1
• refs/tags/3.4.3
• rfc2047-perf
• rfc2047-tokens
• smime-revocation-checks
• stream-spans
• unix2dos-indexof
• unsafe-scancontent
• vnext

Build # 4.13.0.1735

Build Type

push

coveralls.net

Committed by jstedfast

Commit Message

Added BinaryQuotedPrintableDecoder

Some mail software will attach pdf files using the quoted-printable
encoding.

On Linux/macOS, because MimeKit saves messages with the Unix line endings,
decoding these pdfs can produce corrupted output when the pdf contains
\r's of significance. These same pdfs typically decode correctly on Windows
because it just so happens that unencoded \r's aren't stripped on that
platform.

BinaryQuotedPrintableDecoder re-inserts the \r's as needed during the
decoding process to overcome this problem.

Note: The current unit test does not properly test this scenario and so
needs some work. Unfortunately, none of the pdfs that I have received that
illustrate this problem can be made public.

Run Details

0 of 0 relevant lines covered (NaN%)

0.0 hits per line