On Sun, Apr 26, 2020 at 01:15:26PM -0500, David Engel wrote:
Thanks for the tip. Mutt still doesn't recognize the PGP block,
however. :( That's not surprising. It probably doesn't check the
processed output because no sane person would wrap a PGP block in
HTML!
Yes, sorry that's right. Mutt
On Sun, Apr 26, 2020 at 11:59:43AM +0200, Jens John wrote:
> On Sat, Apr 25, 2020 at 09:46:48PM -0500, David Engel wrote:
> > IT guy refuses to install any Outlook plugin for them to properly
> > handle encypted emails.
>
> Outlook has pretty comprehensive, native support for encrypting and
> sign
On Sun, Apr 26, 2020 at 09:13:59AM +0100, Dave Woodfall wrote:
> On 2020-04-26 08:04,
> Dave Woodfall put forth the proposition:
> > On 2020-04-25 21:46,
> > David Engel put forth the proposition:
> > > Hi,
> > >
> >
> > Elinks[1] has an option to `compress-empty-lines'. Other than that
> > perh
On Sat, Apr 25, 2020 at 09:46:48PM -0500, David Engel wrote:
> IT guy refuses to install any Outlook plugin for them to properly
> handle encypted emails.
Outlook has pretty comprehensive, native support for encrypting and
signing with S/MIME. Perhaps your IT guy would be more open to just
using a
On 2020-04-26 08:04,
Dave Woodfall put forth the proposition:
> On 2020-04-25 21:46,
> David Engel put forth the proposition:
> > Hi,
> >
>
> 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.
On 2020-04-25 21:46,
David Engel 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 emai
