On Thu, 2001-11-29 at 15:33, Jeffrey Stedfast wrote:
THIS IS A BUG IN GPG!
gpg tells us everything went fine, so Evolution has no way of knowing
that it didn't encrypt to all the recipients we told it to encrypt to,
thus it's not our fault.
Yuck. There's actually several of these
On Thu, 2001-11-29 at 22:39, Thomas O'Dowd wrote:
Evolution currently has problems verifying inline PGP signed messages
from mailers when they are qp'd by a gateway along the way. Mutt doesn't
have that problem so I'm suggesting being liberal (as it is inline pgp
anyway) and unencode first
Jeffrey Stedfast wrote:
On Thu, 2001-11-29 at 05:25, Levente Farkas wrote:
hi,
and at last gpg simple unusable with evolution. when I try send an encripted
mail with evo (I have to go to the menu and click on a menu item, it
would be much simpler if I able to check it somewhere within
On Thu, 2001-11-29 at 05:25, Levente Farkas wrote:
hi,
and at last gpg simple unusable with evolution. when I try send an encripted
mail with evo (I have to go to the menu and click on a menu item, it
would be much simpler if I able to check it somewhere within the
composer window and I
The problem is that you guys don't fully understand the problem, to you
it sounds as simple as just pipe it to pgp or gpg and whallah but it's
not that simple. Well, not if you expect the other end to be able to
verify your signatures at least. Sure, I could just pipe to pgp/gpg, but
if the
On Thu, 2001-11-29 at 20:15, Thomas O'Dowd wrote:
It takes care of escaping the ^From for you so you don't have to
worry about it.
That's nice, but it doesn't take care of QP encoding it and I'm not too
sure that it CRLF encodes it either.
Jeff
--
Jeffrey Stedfast
Evolution Hacker -
On Thu, Nov 29, 2001 at 08:33:42PM -0500, Jeffrey Stedfast wrote:
On Thu, 2001-11-29 at 20:15, Thomas O'Dowd wrote:
It takes care of escaping the ^From for you so you don't have to
worry about it.
That's nice, but it doesn't take care of QP encoding it and I'm not too
sure that it CRLF
On Thu, 2001-11-29 at 21:27, Thomas O'Dowd wrote:
On Thu, Nov 29, 2001 at 08:33:42PM -0500, Jeffrey Stedfast wrote:
On Thu, 2001-11-29 at 20:15, Thomas O'Dowd wrote:
It takes care of escaping the ^From for you so you don't have to
worry about it.
That's nice, but it doesn't take
On Thu, 2001-11-29 at 21:27, Thomas O'Dowd wrote:
On Thu, Nov 29, 2001 at 08:33:42PM -0500, Jeffrey Stedfast wrote:
On Thu, 2001-11-29 at 20:15, Thomas O'Dowd wrote:
It takes care of escaping the ^From for you so you don't have to
worry about it.
That's nice, but it doesn't take
Jeffrey Stedfast wrote:
On Thu, 2001-11-29 at 05:25, Levente Farkas wrote:
hi,
and at last gpg simple unusable with evolution. when I try send an encripted
mail with evo (I have to go to the menu and click on a menu item, it
would be much simpler if I able to check it somewhere within
On Thu, 2001-11-29 at 05:25, Levente Farkas wrote:
hi,
and at last gpg simple unusable with evolution. when I try send an encripted
mail with evo (I have to go to the menu and click on a menu item, it
would be much simpler if I able to check it somewhere within the
composer window and I
The problem is that you guys don't fully understand the problem, to you
it sounds as simple as just pipe it to pgp or gpg and whallah but it's
not that simple. Well, not if you expect the other end to be able to
verify your signatures at least. Sure, I could just pipe to pgp/gpg, but
if the
On Thu, Nov 29, 2001 at 08:10:15PM -0500, Jeffrey Stedfast wrote:
On Thu, 2001-11-29 at 19:50, Thomas O'Dowd wrote:
On Thu, Nov 29, 2001 at 03:33:32PM -0500, Jeffrey Stedfast wrote:
In-line pgp mode is a broken way to do it - so many things can go
wrong. Should I first QP/Base64
...and if you're on DOS, piping it to pgp has text in the canonical
CRLF format, whereas in Unix it doesn't.
Also, if the text contains 8bit text, do we QP encode before or after we
sign it? If we QP encode before, will the other mailer know to feed the
encoded text to pgp? Or will it assume
14 matches
Mail list logo
