Hello Thorsten, On Sunday, April 14, 2002 at 1:12:18 PM +0200, Thorsten Haude wrote:
> I cannot verify the following IDs (only checked April): > Message-ID: <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> Strange: I can verify OK those 2 mails, but can't verify 4 others (gpg: BAD signature from ...) on the 325 PGP signed mails from April. Their IDs are: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Note the last one is by David too. Don't know what's happening? ...taking more time to study the 4 mails... Last minute before sending: Well, I found what's happening, at least for "my" 4 bad sigs. The 4 mails have, in their raw quoted-printable encoded form, lines beginning by dots. And I use a &#@&@# broken deliver process not removing the dot added in this case by SMTP. So I have too many dots in my mailbox, GnuPG considers these mails changed, and moans. Once these dots removed with editor, the 4 messages verify OK. What's strange is that Mutt's smart QP encoding process should have encoded the first dot of a line as =2E while sending, to avoid this exact problem... And in fact he has done it, in one case: the first line of David's mail is raw "=2E..and then Rob Reid said..." (3 dots at the beginning, with the 1st encoded). But in other cases, he has not done it. In the last 3 mails (the first mail is not QP encoded, so it's normal) some dots *not* beginning a line were rejected at beginning of next one, because of QP soft cutting long lines... And Mutt didn't notice it should have encoded it. I guess it's a bug. Or an only half working feature... ;-) Sample taken from last ID (I quoted with "| "): | % For many people that would be tricky but fortunately for you it's just "l." unencoded text was longer than the QP 76 chars limit, so before sending Mutt's QP encoder inserted a soft line break "=\n" as: | % For many people that would be tricky but fortunately for you it's just "l= | ." resulting in a misplaced dot. It should have better done so: | % For many people that would be tricky but fortunately for you it's just "l= | =2E" or even better in this case, but difficult to generalize, it could have decided to insert it's line cut one char before: | % For many people that would be tricky but fortunately for you it's just "= | l." Bye! Alain.
