Date:Fri, 17 May 2019 12:39:49 -0400
From:Ken Hornstein
Message-ID: <20190517163950.2d10e15b...@pb-smtp1.pobox.com>
| Sigh. You KNOW what I mean. I mean that if you want to run
| "pick -search hello" on encrypted email, you're going to have to decrypt
| it, wh
> | and that decoding may require some sort of user interaction,
>
>Doing almost anything with e-mail requires some sort of user interaction,
>that's what nmh is all about - the means of interacting. Parsing scan
>listings to decide what to do for something automated is entirely the
>wrong appro
On Thu, 16 May 2019 23:10:32 -0400, Ken Hornstein said:
> >Note that 'E' in the format is different to the alternate annotations
> >that can occur in the same position (and trump the E if more than one
> >applies) in that the others tell what I have done to the message
> >(that I have replied, or
Hi Ken,
I favour removing the test for %{encrypted} from the default formats,
without deprecation for a release since it's trivial for a user to add
back in, and only add %(encrypted) if and when it's got a useful
definition.
--
Cheers, Ralph.
--
nmh-workers
https://lists.nongnu.org/mailman/li
Date:Thu, 16 May 2019 23:10:32 -0400
From:Ken Hornstein
Message-ID: <20190517031033.54569150...@pb-smtp2.pobox.com>
I view the "original MH" as more like the HDTV ads - we can do it
(except they couldn't) so let's advertise... Not worth keeping.
| Second ... encr
>However I wonder at the rationale for including this info in the
>scan format at all. We don't print 'M' if the message is MIME
>encoded, and we don't print 'F' if there's a face header, and nor
>do we print 'A' if there are attachments - what's so special about
>encrypyted that warrants this sp
Date:Thu, 16 May 2019 20:56:28 -0400
From:Ken Hornstein
Message-ID: <20190517005629.c904f14f...@pb-smtp2.pobox.com>
| People with their own scan formats would see no change, except that they'd
| have to change at some point in the future when we supported encrypte
>Probably need to be a bit more ambitious than that, and MIME-compliant.
Well, here's my thinking.
The generic concept of encrypted email is always going to require some
special handling, since you have to unpack it to do things like search
in it or get the inner MIME structure. And there are se
On Thu, 16 May 2019 20:56:28 -0400, Ken Hornstein said:
> It occur to me that this might still be useful, but making this switch
> on a component is obviously wrong, and it should really be a function
> escape. So I propose we switch all of the default scan formats from
> using %{encrypted} to a
I suspect most people may not be aware, but all of the scan formats that
are shipped with nmh will output an 'E' in one column if the email is
encrypted (in theory).
What actually happens is ... well, obviously this doesn't work. I guess
there was prototype encrypted email system that was never s
10 matches
Mail list logo
