On 2020-04-25 21:46, David Engel <[email protected]> put forth the proposition: > Hi, > > My company uses PGP/GPG when sending sensitive material through email. > Unfortunately (for them and me), most people use Outlook and our IT > guy refuses to install any Outlook plugin for them to properly handle > encypted emails. Consequently, I receive such sensitive material as > traditional, PGP which the Outlook users have copied and pasted the > output from PGP into the email. They have to copy and paste the other > direction through PGP when they receive encrypted email. > > When the traditional PGP is sent to me as text/plain, Mutt handles it > just fine automatically and I silently laugh at the hoops the Outlook > users have to jump through to send and receive encrypted email. > However, after a recent Outlook upgrade/reinstall, I now frequently > receive the traditional PGP as text/html. Mutt doesn't recognize the > traditioinal PGP after after the entire html part gets sent through > w3m as directed by my .mailcap. I've given up politely asking people > to remember to send email as either both text/html and text/plain or > just text/plain when sending to me. It's a losing battle. :( > > Anyway, I'd hoped the unrecognition of the traditional PGP in HTML was > due to the formatting done by w3m. Outlook adorns the pssted in text > with additional <p> and <span> tags that cause w3m to double-space the > output making it look like the following. Links2 does the same thing.
Elinks[1] has an option to `compress-empty-lines'. Other than that perhaps piping the -dumped text through cat -s or --squeeze-blank might work - e.g. `w3m -dump | cat -d ...' [1] http://elinks.or.cz/index.html
