Hello Stephen! Sorry for the late reply..
Stephen Isard wrote in <[email protected]>: |On Sat, 5 Oct 2024, Steffen Nurpmeso steffen-at-sdaoden.eu |s-nail| wrote: |... |>|the lines in |>|the newly detached version of abc.txt are separated in Microsoft style |>|with \r\n. Is there a reason for that and is there some variable I can |>|set to prevent it happening? |> |> I cannot reproduce this with v14.9.25. |... | |Aha. The problem occurs when I send the attachment with alpine, but not |when I send with s-nail. If I send the message with alpine and read and |detach in alpine, there are no extra \r characters. If I read with |s-nail and detach by piping the file through the venerable munpack |program, there are no extra \r's. But if I read with s-nail and detach |with |w /dev/null (Btw for s-nail you can leave away /dev/null, an empty input on any question of `write` should go to /dev/null. (Meaning it really goes there until v15, when we hopefully simply can do nothing, then.)) |the extra \r's appear. | |I am sending this message with alpine and have attached a file |containing just the word "test" followed by a newline character for you |to try. Hm, if i `Show` that and only copy the base64 to a file, that: $ base64 -d <.B64|cat -vet test^M$ So either the file uses DOS/network line terminators, or Alpine "brings it into RFC 5322 Internet Message Format format before it applies base64 encoding", which would be a bug. (Hard to believe given how many people use it, no commit there for almost five months, .. maybe an Alpine configuration thing??) (Having said that, at least our codebase is notoriously dumb regarding that, and always has been. It is the Unix \n, and the SMTP module takes care for "the real thing" "on the front line".) --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
