On Tuesday 17 November 2015 18:33:04 Lisi Reisz wrote:
> On Tuesday 17 November 2015 23:18:01 Gene Heskett wrote:
> > On Tuesday 17 November 2015 13:40:06 Bob Bernstein wrote:
> > > On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
> > > > Anyway,.. I don't think that anything is wrong with the
On Tuesday 17 November 2015 23:18:01 Gene Heskett wrote:
> On Tuesday 17 November 2015 13:40:06 Bob Bernstein wrote:
> > On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
> > > Anyway,.. I don't think that anything is wrong with the S/MIME
> > > that Evolution applies, in fact, as you could read
On Tuesday 17 November 2015 13:40:06 Bob Bernstein wrote:
> On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
> > Anyway,.. I don't think that anything is wrong with the S/MIME
> > that Evolution applies, in fact, as you could read, other
> > people could verify it.
>
> Aha. Did evolution verif
On Tuesday 17 November 2015 17:31:06 Bob Bernstein wrote:
> I believe the poster is trying to sign his messages with
> smime. My fairly recent version of alpine 2.20 tells me that his
> messages bear a "cryptographic signature," but that those
> signatures cannot be "verified."
>
> Please allow me
On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
..your cert has expired on 2015-03-12.
That's helpful, thank you.
It explains why the message's sig cannot even be verified by the
running instance of alpine that created it (if I look at said
message in my sent messages file).
I think
On Tue, 2015-11-17 at 13:40 -0500, Bob Bernstein wrote:
> Aha. Did evolution verify my smime sig in the message I just
> sent to the list?
Nope, your cert has expired on 2015-03-12.
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Hi,
> other people could verify it.
Urm, not in my case. It's just that alpine can stand it.
The error message when opening
Message-ID: <1447719799.6941.4.ca...@scientia.net>
is
Couldn't verify S/MIME signature: certificate verify error
The header
Content-Type: multipart/signed; micalg="
tomas writes:
> Sure, I would expect Gmail to do nearly anything, but KMail falling
> flat on its face due to mangled input coming from somewhere out there
> is in my eyes a bug (or worse).
Yes, I said it was a bug in Kmail. I was pointing out that it may be
one that is only triggered when a part
On Tue, 17 Nov 2015, Christoph Anton Mitterer wrote:
Anyway,.. I don't think that anything is wrong with the S/MIME
that Evolution applies, in fact, as you could read, other
people could verify it.
Aha. Did evolution verify my smime sig in the message I just
sent to the list?
If the Debian
On Tue, 2015-11-17 at 14:18 +, Lisi Reisz wrote:
> I can live without being able to read emails form one individual
> ever.
Gosh... I never got so much meta-answers around one of my mails
itself...
In any case, if your MUA crashes based on whichever mail it reads,...
than it's likely a bug, a
I believe the poster is trying to sign his messages with
smime. My fairly recent version of alpine 2.20 tells me that his
messages bear a "cryptographic signature," but that those
signatures cannot be "verified."
Please allow me to do the samd, i.e. sign with smime.
--
Bob Bernstein
smime.p7
On Tuesday 17 November 2015 13:42:54 Markus Schc3b6nhaber wrote:
> Am 17.11.2015 um 01:42 schrieb Lisi Reisz:
> > My email client chokes on your signature. If I make any attempt to
> > reply, my email client freezes.
>
> Then your mail client is broken.
>
> > So I have deleted both your emails.
>
Am 17.11.2015 um 01:42 schrieb Lisi Reisz:
> My email client chokes on your signature. If I make any attempt to reply, my
> email client freezes.
Then your mail client is broken.
> So I have deleted both your emails.
>
> Try: sorting out your signature (I don't know what is wrong with it),
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Nov 17, 2015 at 07:08:18AM -0600, John Hasler wrote:
> Chris Bannister writes:
> > Perhaps a bug in KMail?
>
> Or Gmail buggering up the OpenSSL signature in such a way as to tickle a
> bug in Kmail. I would expect Gmail to mangle cryptograph
Chris Bannister writes:
> Perhaps a bug in KMail?
Or Gmail buggering up the OpenSSL signature in such a way as to tickle a
bug in Kmail. I would expect Gmail to mangle cryptographic signatures.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Nov 17, 2015 at 12:42:55AM +, Lisi Reisz wrote:
> My email client chokes on your signature. If I make any attempt to reply, my
> email client freezes.
>
> So I have deleted both your emails.
>
> Try: sorting out your signature (I don't
Hi,
Lisi Reisz wrote:
> My email client chokes on your signature.
My alpine mail client showed a warning about MIME signature,
probably because of:
Content-Type: multipart/signed; micalg="sha-512";
protocol="application/x-pkcs7-signature";
boundary="=-q9gdJ6oE7VoDos3CeFlt"
> As he do
On Tue, Nov 17, 2015 at 12:42:55AM +, Lisi Reisz wrote:
> My email client chokes on your signature. If I make any attempt to reply, my
> email client freezes.
>
> So I have deleted both your emails.
>
> Try: sorting out your signature (I don't know what is wrong with it), or
> omitting you
Lisi writes:
> My email client chokes on your signature. If I make any attempt to reply, my
> email client freezes.
As he does not use a proper delimiter he doesn't really have a
signature. His messages end with
Cheers,
Chris.
That's not correct, but it is no excuse for Gmail to freeze up.
--
On Tue, 2015-11-17 at 00:42 +, Lisi Reisz wrote:
> My email client chokes on your signature. If I make any attempt to
> reply, my
> email client freezes.
Well... than it's very likely a bug in your MUA.
> Try: sorting out your signature (I don't know what is wrong with it),
> or
> omitting
My email client chokes on your signature. If I make any attempt to reply, my
email client freezes.
So I have deleted both your emails.
Try: sorting out your signature (I don't know what is wrong with it), or
omitting your signature.
I may not be the only one having problems.
Lisi
21 matches
Mail list logo
