Mailing List Archive

> has anybody got experiences with different email
> clients for X?
>
> the trouble is that i found different clients
> supporting pgp but i can't make them work (even if
> i use gpgpgp) with gpg.
>
> any suggestions?

I generally stay away from GUI mail user agents. Of the text mode
MUAs, mutt supports gpg out of the box. Pine can use gpg too, I think.

On Tue, 25 Jul 2000, Lars Hecking wrote:

>
> > has anybody got experiences with different email
> > clients for X?
> >
> > the trouble is that i found different clients
> > supporting pgp but i can't make them work (even if
> > i use gpgpgp) with gpg.
> >
> > any suggestions?
>
> I generally stay away from GUI mail user agents. Of the text mode
> MUAs, mutt supports gpg out of the box. Pine can use gpg too, I think.
>
>

just get pgp4pine from linuxberg or directly from the homesite
(http://pgp4pine.flatline.de). It's easy to configure and works with both
PGP and GPG. And pine is (in my humble opinion) still the best UNIX mail
client.

Stefan

I have used several different Tcl/Tk mailers that have pgp/gpg
builtin. This message is being sent by tkrat. I have not been
using it lately, as I mainly stick with the command line. I like
tkrat because it has imap capability. Another mailer, postilion,
is based from tkrat, and has more colorful buttons. I have also
enjoyed using exmh in the past. I enjoy some of the capabilities
of mh based mailers.

-walter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 25-Jul-2000 Robert Lillack wrote:
> has anybody got experiences with different email
> clients for X?
>
>
XFmail works well

Regards

Brian

- --
- ----------------------------------------------------
Brian Galbraith
Default Key 0x63EBA765 (DH/DSA)
http://seattle.keyserver.net:11371/pks/lookup?op=get&search=0x63EBA765
ICQ 79205734
- ----------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: Digital Signatures Verify Author and Unaltered Content

iD8DBQE5fcyUEPpEmWPrp2URAv37AKD9uQCZ7vPQawUAryMGQw9K/e8xggCdFbae
1UCPut/dPP2GnQOnS93SYzA=
=fDZ8
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 25 Jul 2000, Stefan Suurmeijer wrote:

> Date: Tue, 25 Jul 2000 18:37:00 +0200 (CEST)
> From: Stefan Suurmeijer <stefan@symbolica.nl>
> To: Lars Hecking <lhecking@nmrc.ie>
> Cc: gnupg-users@gnupg.org
> Subject: Re: GnuPG: what email client should i use?
> Resent-Date: Tue, 25 Jul 2000 18:39:35 +0200
> Resent-From: gnupg-users@gnupg.org
>
> On Tue, 25 Jul 2000, Lars Hecking wrote:
>
> >
> > > has anybody got experiences with different email
> > > clients for X?
> > >
> > > the trouble is that i found different clients
> > > supporting pgp but i can't make them work (even if
> > > i use gpgpgp) with gpg.
> > >
> > > any suggestions?
> >
> > I generally stay away from GUI mail user agents. Of the text mode
> > MUAs, mutt supports gpg out of the box. Pine can use gpg too, I think.
> >
> >
>
> just get pgp4pine from linuxberg or directly from the homesite
> (http://pgp4pine.flatline.de). It's easy to configure and works with both
> PGP and GPG. And pine is (in my humble opinion) still the best UNIX mail
> client.

http://pgpenvelope.sourceforge.net

is also quite nice..
I thought it was much easier to set up than pgp4pine,
and has a more powerful interface.

- --
"The Funk, the whole Funk, and nothing but the Funk."
Billy Donahue <mailto:billy@dadadada.net>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: pgpenvelope 2.8.11 - http://pgpenvelope.sourceforge.net/

iD8DBQE5fc5B+2VvpwIZdF0RAtd7AJ9ITqBJS21SoNH5YsEZisyhLtqCFQCdFx0E
ndGLb23LAFtrk5es2YB9NBs=
=D355
-----END PGP SIGNATURE-----

I would appreciate not to be Cc'd on list email, thank you.

Billy Donahue writes:
[...]
> http://pgpenvelope.sourceforge.net
>
> is also quite nice..
> I thought it was much easier to set up than pgp4pine,
> and has a more powerful interface.

--
Better dead than mellow.

On 25 Jul, Walter Truitt wrote:
> I have used several different Tcl/Tk mailers that have pgp/gpg
> builtin. This message is being sent by tkrat. I have not been
> using it lately, as I mainly stick with the command line. I like
> tkrat because it has imap capability. Another mailer, postilion,
> is based from tkrat, and has more colorful buttons. I have also
> enjoyed using exmh in the past. I enjoy some of the capabilities
> of mh based mailers.
>
> -walter

Hmmm,

There is apparently a bug in tkrat, where it creates a bad signature if
I have a return on the last line. I had just sent a test message to
myself before writing to the list, and was sure it would work. Now I
know what the problem is anyways.

-walter

Lars Hecking, at 18:30 +0100 on Tue, 25 Jul 2000, wrote:

> I would appreciate not to be Cc'd on list email, thank you.

There are two solutions you can use to avoid this problem; procmail using
formail's duplicate detection (man procmailex(5)) or nodupmail,
http://nodupmail.sourceforge.net/

--
Frank Tobin http://www.uiuc.edu/~ftobin/

Frank Tobin writes:
> Lars Hecking, at 18:30 +0100 on Tue, 25 Jul 2000, wrote:
>
> > I would appreciate not to be Cc'd on list email, thank you.
>
> There are two solutions you can use to avoid this problem; procmail using
> formail's duplicate detection (man procmailex(5)) or nodupmail,
> http://nodupmail.sourceforge.net/

That's not the issue. I've had such a filter in place for years now.

Cc'ing list members is unnecessary in the first place. Mailing list
members receive all mail sent to the list, that's the whole point
of a mailing list.

Robert Lillack <rob@lillack.de> writes:

> has anybody got experiences with different email
> clients for X?
>
> the trouble is that i found different clients
> supporting pgp but i can't make them work (even if
> i use gpgpgp) with gpg.
>
> any suggestions?

gnu emacs and mailcrypt.el.

thi

On 25 Jul, Walter Truitt wrote:

> There is apparently a bug in tkrat, where it creates a bad signature if
> I have a return on the last line. I had just sent a test message to
> myself before writing to the list, and was sure it would work. Now I
> know what the problem is anyways.
>
> -walter

Hmmm,

I spent a considerable amount of time trying to solve the error.
Everytime, I was getting the false impression that I solved the error. I
would send a test message to myself and it would work. It turns out,
there was a problem in the program where after the first body has been
printed to a file, it would create an extra carriage return/line feed at
the beginning of following bodies. I am not sure where this extra line
gets removed at a later time, but I have corrected my own version and
sent a bug report to the author (as well as my own patch). If someone
is interested in using tkrat, I can email them the patch to get it
working correctly.

Something else I found in the code is a difference in the
multipart/signed header where it states the micalg=pgp-sha1 (or what it
had set to pgp-md5). I am guessing that gnupg defaults to sha1, and
therefore set it to print this instead. I would also suppose that gpg
can handle both, and it is not necessary to pass a flag to specify the
algorithm. I will likely pass this to the tkrat author as well.

Now that I have it working, I highly recommend it as it has IMAP,
threading, and a handy watcher that can be used in place of xbiff. This
watcher is more like tkbiff in that it gives you the author and subject
of the mail rather than just the beep and flag raise.

-walter

On Wed, 26 Jul 2000, Walter Truitt wrote:

> Something else I found in the code is a difference in the
> multipart/signed header where it states the micalg=pgp-sha1 (or what it
> had set to pgp-md5). I am guessing that gnupg defaults to sha1, and
> therefore set it to print this instead. I would also suppose that gpg

SHA-1 is the hash algorithm required by DSS and tehrefore GnuPG
normally uses this. Using MD5 together with a DSA key is not
possible. GnupG has no need for the micalg parameter but according to
the standard it should be tehrer. There is a new --status-fd output
which tells you the micalg used:

SIG_CREATED <type> <pubkey algo> <hash algo> <class> <timestamp> <key fpr>
A signature has been created using these parameters.
type: 'D' = detached
'C' = cleartext
'S' = standard
(only the first character should be checked)
class: 2 hex digits with the signature class


Werner

--
Werner Koch OpenPGP key 621CC013
OpenIT GmbH http://www.OpenIT.de