Hi!
> > > Verdict: elinks is introducing the 3 blanks.
Forgive me for maybe being silly due to ignorance of Nmh internals, but
'elinks -dump' introducing leading whitespace might perhaps be remedied by
> elinks -eval 'set document.browse.margin_width = 0' -dump [...]
- ? Just a humble tho
> > > > elinks -eval 'set document.browse.margin_width = 0' -dump [...]
> >
> > That works too. And is probably a better solution, as it fixes *this*
> > issue without introducing a bunch of sed or awk that might paper over
> > an actual issue later down the road...
Less is more, I suppose.
> Right now a user can sit down, compose a message that happens to contain
> 8-bit characters, and send it out ... and nmh will happily blast it out,
> with no MIME headers at all. This is super-wrong. And it's not a
> theoretical problem either:
>
> http://lists.nongnu.org/archive/html/nmh-wo
Hi!
> You know of the workaround where you alter your initial drafts to have
> hard-coded
>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 8bit
>
> headers, altered to suit?
Maybe I was half aware of the possibility of such a workaround,
