Re: [sup-talk] PGP INLINE - can't make it work

From: Piotr Kempa <piotr.kempa@wp.eu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] PGP INLINE - can't make it work
Date: Wed, 10 Mar 2010 15:41:35 +0100	[thread overview]
Message-ID: <1268231546-sup-2256@pk-laptop> (raw)
In-Reply-To: <1268219571-sup-3316@midna.zekjur.net>

Excerpts from Michael Stapelberg's message of 2010-03-10 12:14:04 +0100:
> Hi Piotr,
> 
> Excerpts from Piotr Kempa's message of Mi Mär 10 11:53:00 +0100 2010:
> > Thank you. I just tried the patch and unfortunately sup crashes on me
> > now. I patched the 0.11 version and checked that the patches were
> > applied successfully (as far as I could at least). 
> Thanks for testing. Can you please see if the updated version works
> for you (attached to this mail)?
> 
> Best regards,
> Michael

Wow, this works!! Thank you so much Michael! This will make my job soooo much
easier, faster and more pleasant :) 

I have just two messages that give errors to sup-sync, but the remaining ones
(a hundred or more) just work beautifully.  The error is like this: 

   [2010-03-10 15:25:28 +0100] Error while running gpg: gpg: invalid armor header: 
	    gpg: malformed CRC
   gpg: encrypted_mdc packet with unknown version 255
   gpg: quoted printable character in armor - probably a buggy MTA has been used

   [2010-03-10 15:25:33 +0100] Error while running gpg: gpg: invalid armor
      header: gpg: CRC error; 9C0326 - DC39C0
   gpg: encrypted_mdc packet with unknown version 255
   gpg: quoted printable character in armor - probably a buggy MTA has been used

(two long lines with the timestamp broken by me)

But I guess this is what it says it is - an invalid message with CRC errors in
the GPG payload, so this should be nothing to worry about. 

Anyway, thanks a million Michael!
-- 
Piotr Kempa
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk