Re: private key not more available (newbie)

Holger von Rauch wrote:
> Hi again,
> 
> apparently, enigmail does not like GPG4win 1.1.0.

I would say it has *nothing* to do with Enigmail. From what I've seen on this
list, the web forum, and the GnuPG-Users list, the problem lies in the GnuPG
build shipping with GPG4woe 1.1.0. The gpg binary does not appear to properly
handle command input in that build.

> I downgraded now back to GPG4win 1.0.8 and my problem was solved.

That or stick with the GnuPG installer, which has, so far, always worked correctly.

--

-- 
John P. Clizbe                      Inet:   John (a) Mozilla-Enigmail.org
You can't spell fiasco without SCO. PGP/GPG KeyID: 0x608D2A10/0x18BB373A
"what's the key to success?"        / "two words: good decisions."
"what's the key to good decisions?" /  "one word: experience."
"how do i get experience?"          / "two words: bad decisions."

"Just how do the residents of Haiku, Hawai'i hold conversations?"

_______________________________________________
Enigmail mailing list
Enigmail <at> mozdev.org
http://mozdev.org/mailman/listinfo/enigmail

Re: private key not more available (newbie)

Hi John,

>> apparently, enigmail does not like GPG4win 1.1.0.
> 
> I would say it has *nothing* to do with Enigmail. From what I've seen on this
> list, the web forum, and the GnuPG-Users list, the problem lies in the GnuPG
> build shipping with GPG4woe 1.1.0. The gpg binary does not appear to properly
> handle command input in that build.
> 
>> I downgraded now back to GPG4win 1.0.8 and my problem was solved.
> 
> That or stick with the GnuPG installer, which has, so far, always worked correctly.

Thank you very much for your feedback.

I think, I will wait now for a couple of months before upgrading next
time GnuPG ...

I appreciate your work and kindness.

Holger

Re: Enigmail doesn't recognize signature from mutt

> Thanks for your answer, I'll contact mutt developer then..

I wrote a bug request:

http://dev.mutt.org/trac/ticket/2901

Greets
Alex

--

-- 
***** http://www.lespocky.de *******************************************
Gott verdammt, wir haben zu viele Termine, dabei sind wir noch Kinder..
                                              /Eric Cartman (Southpark)/

Re: Avoid blank first row

Armando wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Armando wrote:
>> How can I avoid Enigmail adding a blank first row to every message?
>>
> 
> If not clear this is what I mean.

It doesn't happen if I choose PGP/MIME. I think what I'm talking
about is a wrong behavior of inline signatures and should be fixed IMHO.

Regards.

_______________________________________________
Enigmail mailing list
Enigmail <at> mozdev.org
http://mozdev.org/mailman/listinfo/enigmail

Re: Avoid blank first row

Armando wrote:
> Armando wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Armando wrote:
>>> How can I avoid Enigmail adding a blank first row to every message?
>>>
>> 
>> If not clear this is what I mean.
> 
> It doesn't happen if I choose PGP/MIME. I think what I'm talking
> about is a wrong behavior of inline signatures and should be fixed IMHO.

IMNSHO, The only thing requiring fixing is your understanding of RFC 2440 which
governs the behavior you cite:
http://www.ietf.org/internet-drafts/draft-ietf-openpgp-rfc2440bis-22.txt

Please see Section 7 - Cleartext signature framework (pages 55-56):

    The cleartext signed message consists of:

      - The cleartext header '-----BEGIN PGP SIGNED MESSAGE-----' on a
        single line,

      - One or more "Hash" Armor Headers,

      - Exactly one empty line not included into the message digest,
     *^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^*
      - The dash-escaped cleartext that is included into the message

Re: Avoid blank first row

John Clizbe wrote:
> Armando wrote:
>> Armando wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Armando wrote:
>>>> How can I avoid Enigmail adding a blank first row to every message?
>>>>
>>> If not clear this is what I mean.
>> It doesn't happen if I choose PGP/MIME. I think what I'm talking
>> about is a wrong behavior of inline signatures and should be fixed IMHO.
> 
> IMNSHO, The only thing requiring fixing is your understanding of RFC 2440 which
> governs the behavior you cite:
> http://www.ietf.org/internet-drafts/draft-ietf-openpgp-rfc2440bis-22.txt

[CUT]

I don't want to eliminate the blank line from the source of the message.
I'd like it not being displayed (if Enigmail is installed). Enigmail
could eliminate (= not display) it the same way it already eliminates
"-----BEGIN PGP SIGNED MESSAGE-----" and the others.

Regards.

Re: Avoid blank first row

Armando wrote:
> John Clizbe wrote:
>> Armando wrote:
>>> Armando wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Armando wrote:
>>>>> How can I avoid Enigmail adding a blank first row to every message?
>>>>>
>>>> If not clear this is what I mean.
>>> It doesn't happen if I choose PGP/MIME. I think what I'm talking
>>> about is a wrong behavior of inline signatures and should be fixed IMHO.
>> IMNSHO, The only thing requiring fixing is your understanding of RFC 2440 which
>> governs the behavior you cite:
>> http://www.ietf.org/internet-drafts/draft-ietf-openpgp-rfc2440bis-22.txt
> 
> [CUT]
> 
> I don't want to eliminate the blank line from the source of the message.
> I'd like it not being displayed (if Enigmail is installed). Enigmail
> could eliminate (= not display) it the same way it already eliminates
> "-----BEGIN PGP SIGNED MESSAGE-----" and the others.

Unfortunately, it's not possible to do that. It's one of the many issues
with integration of inline PGP into Thunderbird.

-Patrick

Re: Avoid blank first row

Patrick Brunschwig wrote:

> Unfortunately, it's not possible to do that. It's one of the many issues
> with integration of inline PGP into Thunderbird.
> 
> -Patrick

I hope Thunderbird will modify their source to allow a better Enigmail
integration or better still integrate it at all (but the last seems
quite improbable at the moment).

Thanks for the reply and for your work.

Regards.

_______________________________________________
Enigmail mailing list
Enigmail <at> mozdev.org
http://mozdev.org/mailman/listinfo/enigmail

Re: Avoid blank first row

Armando wrote:
> Patrick Brunschwig wrote:
> 
>> Unfortunately, it's not possible to do that. It's one of the many issues
>> with integration of inline PGP into Thunderbird.

> I hope Thunderbird will modify their source to allow a better Enigmail
> integration or better still integrate it at all (but the last seems
> quite improbable at the moment).

OK, I have now read everything completely.  Here is My understanding of
the 'problem' and if it's totally incorrect; so be it. :(

For Enigmail to 'function' properly, Plaintext *must* be utilized since
that is what Encryption 'plays well with' so I suggest going into
Settings and selecting Plaintext with a line-wrap of 72 within T-Bird
'Account Settings' and then setting Enigmail to line-wrap to '70'.  Then
whenever You desire to use HTML; click on 'Write' with the SHIFT Key
depressed and use PGP/MIME for _those_ Emails.  :-\

JOHN ;)
Timestamp: Monday 04 Jun 2007, 19:14  --400 (Eastern Daylight Time)

Flowed text

Hello everybody, is the "allow flowed text" option disappeared on
Enigmail 0.95.0, or do I miss anything?

Yours sincerely

--

-- 
                Marco Alberoni