Re: [Mailman-Users] GPG Sig parse error

On Thu, 2018-11-01 at 16:48 -0600, Grant Taylor via Mailman-Users wrote: > On 11/01/2018 01:49 PM, Jim Popovitch via Mailman-Users wrote: > > Apologies Grant it this is too much discussion of you :-) I'm only > > trying  > > to get to the root of the issue. > > No problem. > > I'm using S/MIME,

Re: [Mailman-Users] GPG Sig parse error

On 11/01/2018 01:49 PM, Jim Popovitch via Mailman-Users wrote: Apologies Grant it this is too much discussion of you :-) I'm only trying to get to the root of the issue. No problem. I'm using S/MIME, not PGP (GPG). Let's see if this makes it through happier. -- Grant. . . . unix || die

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

On Thu, 2018-11-01 at 13:07 -0700, Mark Sapiro wrote: > On 11/1/18 12:43 PM, Jim Popovitch via Mailman-Users wrote: > > > > Here's what I see https://i.imgur.com/xLDnojI.png in Evolution.  I > > was wrong to assume it was a PGP parse error, it does however look > > to be a pkcs7 sig parse

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

On 11/1/18 12:43 PM, Jim Popovitch via Mailman-Users wrote: > > Here's what I see https://i.imgur.com/xLDnojI.png in Evolution. I was > wrong to assume it was a PGP parse error, it does however look to be a > pkcs7 sig parse error... and I'm clueless about how to investigate that. > :-) The

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

On Thu, 2018-11-01 at 15:43 -0400, Jim Popovitch via Mailman-Users wrote: > On Thu, 2018-11-01 at 12:30 -0700, Mark Sapiro wrote: > > On 11/1/18 12:11 PM, Jim Popovitch via Mailman-Users wrote: > > > On Thu, 2018-11-01 at 12:27 -0600, Grant Taylor via Mailman-Users > > > wrote: > > > >

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2018-11-01 at 12:30 -0700, Mark Sapiro wrote: > On 11/1/18 12:11 PM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2018-11-01 at 12:27 -0600, Grant Taylor via Mailman-Users > > wrote: > > > Error verifying signature: parse error > >

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

On 11/1/18 12:11 PM, Jim Popovitch via Mailman-Users wrote: > On Thu, 2018-11-01 at 12:27 -0600, Grant Taylor via Mailman-Users wrote: >> Error verifying signature: parse error > > Hello, > > I changed the subject and have GPG signed this message. I've done this > because I keep seeing GPG

Re: [Mailman-Users] mm-handler support

On 11/1/18 12:05 PM, Grant Taylor via Mailman-Users wrote: > On 10/31/2018 08:14 PM, Mark Sapiro wrote: > >> See > > Intriguing. > > My python is quite bad, but that looks like it reads from STDIN and > writes to STDOUT.  Which

[Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2018-11-01 at 12:27 -0600, Grant Taylor via Mailman-Users wrote: > Error verifying signature: parse error Hello, I changed the subject and have GPG signed this message. I've done this because I keep seeing GPG Sig parse errors for

Re: [Mailman-Users] mm-handler support

On 10/31/2018 08:14 PM, Mark Sapiro wrote: I think that would be good. ACK See my reply to Jim if you have opinions on how / when it's done. See Intriguing. My python is quite bad, but that looks like it reads from STDIN

Re: [Mailman-Users] mm-handler starting version

On 10/31/2018 08:41 AM, Jim Ziobro wrote: I am starting from the contrib directory file named:     mm-handler-2.1.10 inside is line:     $VERSION = '$Id: mm-handler 2.1.10 2008-04-14 00:00:00 $'; My goals:  * patch upper/lowercase issue solved a decade ago  * allow mail to