User had issue (reported via email) where \n getting replaced in message body broke S/MIME. --no-data-fixup helped, but then other stuff had to be massaged (specifically the line-endings had to be explicitly fixed).
Maybe --no-data-fixup could take an option of things not to touch. For instance trailing-dot, line-endings, tokens, etc. In this use case the use could have just run with --no-data-fixup tokens (\n is seen as a token internally) and been happy. all would induce the current behavior, and the default arg for --no-data-fixup would be all.
User had issue (reported via email) where \n getting replaced in message body broke S/MIME. --no-data-fixup helped, but then other stuff had to be massaged (specifically the line-endings had to be explicitly fixed).
Maybe --no-data-fixup could take an option of things not to touch. For instance trailing-dot, line-endings, tokens, etc. In this use case the use could have just run with
--no-data-fixup tokens(\n is seen as a token internally) and been happy.allwould induce the current behavior, and the default arg for --no-data-fixup would be all.