Anders Eriksson | 3 Jun 21:16 2008

[Nmh-workers] nmh 1.3 has been released (fwd)


------- Forwarded Message

To: nmh-workers <at> nongnu.org
From: pmaydell <at> chiark.greenend.org.uk

We're pleased to announce the release of nmh 1.3. You can find it in
the savannah download area:

  http://download.savannah.nongnu.org/releases/nmh/nmh-1.3.tar.gz

It's been over two years since the 1.2 release; but the changes here
are mostly minor; largely bugfixes.

You should note that we have changed the default configuration to
allow all supported forms of address masquerading. For more details
please see the --enable-masquerade option to configure, and the
mh-tailor and post man pages.

For more detailed information you can look at the ChangeLog
since 1.2:

http://cvs.savannah.gnu.org/viewvc/nmh/ChangeLog?root=nmh&r1=1.215&r2=1.254.2.13

Please report problems in the bug tracker on savannah
(https://savannah.nongnu.org/projects/nmh/), or on the
nmh-workers <at> nongnu.org mailing list. Thanks!

The nmh project website is: http://www.nongnu.org/nmh/

(Continue reading)

Julian Stacey | 5 Jun 01:58 2008

Enabling GPG Crypt & Key lookup on EXMH 2.7.2

Hi exmh-users <at> redhat.com
I cant get EXMH to integrate with GPG,
( I'm a long term EXMH user, but new to GPG & this list )
EXMH wont recognise & click to decrypt,
I also can't encrypt from within EXMH
But EXMH works fine apart from that, & GPG works fine driven manually.

I have EXMH 2.7.2 & gnupg-1.4.5_1 on FreeBSD-6.2 
(& EXMH 2.7.2 & gnupg-1.4.7_1 gnupg-2.0.4 on FreeBSD-7.0 )
I just installed quintuple-agent-1.0.4_1 & changed paths below to
match /usr/local/bin/q-client in case needed 

If someone has gpg working with exmh I'd much appreciate a copy of your 
exmh-defaults, & whatever else you might think appropriate,
& I append mine below for comparison, 

Ive also done 
sh
q-agent &
AGENT_SOCKET=/usra/home/jhs/tmp/quintuple-agent-200.0/agent-socket
export AGENT_SOCKET
q-client get "Julian H. Stacey"
	secret available, but I won't print it on a tty
exmh

& am now getting:
-----
wrong # args: should be "Edit_Done act ?msg? argu"
    while executing
"Edit_Done send 9"
(Continue reading)

Klaus Elsbernd | 6 Jun 08:18 2008
X-Face
Picon
Picon

Enabling GPG Crypt & Key lookup on EXMH 2.7.2

Hello,

"Julian Stacey" <jhs <at> berklix.org>:
>I cant get EXMH to integrate with GPG,
>( I'm a long term EXMH user, but new to GPG & this list )
Pleas ensure, that the calling environment of gpg is english, because exmh 
checks for the english messages. Usage of gpg with language set to other won't 
work. Here my workaround, when the default (login) language is other. 
Especially look at the difference between the environment variable LANG and 
LANGUAGE.
The effect is, that exmh uses native charset/language and gpg uses the english 
one.

---------------------
#!/bin/sh
volcheck
LANG=de
LANGUAGE=en
LC_ALL=de_DE.ISO8859-1
PATH=/usr/dt/bin:$PATH;
MM_CHARSET=iso-8859-1
export LANG LANGUAGE LC_ALL PATH MM_CHARSET ;
umask 7
/opt/dfki/bin/exmh $*
---------------------------

Bis dann
Klaus

--

-- 
(Continue reading)

Julian Stacey | 6 Jun 18:13 2008

Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2

> Hello,
> 
> =22Julian Stacey=22 <jhs=40berklix.org>:
> >I cant get EXMH to integrate with GPG,
> >( I'm a long term EXMH user, but new to GPG & this list )
> Pleas ensure, that the calling environment of gpg is english, because exm=
> h=20
> checks for the english messages. Usage of gpg with language set to other =
> won't=20
> work. Here my workaround, when the default (login) language is other.=20
> Especially look at the difference between the environment variable LANG a=
> nd=20
> LANGUAGE.
> The effect is, that exmh uses native charset/language and gpg uses the en=
> glish=20
> one.

Interesting, Thanks for the reply :-)
A good guess, yes I am in Germany,
Unfortunately that doesnt seem to be the problem.
I have no LANG and LANGUAGE in my environment, 
( I'm English & I leave it to default American keyboard layout & fonts etc),
Nearest I have to interesting env vars is:
	SPUNK_COUNTRY=049
	SPUNK_LANGUAGE=2	# For estic for istec PBX/TK isdn control
	TZ=Europe/Berlin
	USA_RESIDENT=NO
Anyone else got an idea ?

Julian
(Continue reading)

Harvey Eneman | 6 Jun 21:39 2008
Picon

Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2

Hi Julian,

I've been using exmh with pgp/gpg for many years.  I'm currently 
using exmh 2.7.2 with gpg 1.4.9 on RedHat (Linux 2.6.9).  Comparing
your exmh default with mine, I see the following gpg differences:

gpgCacheIds:	persistent
gpgKeyQueryMethod:	hkp
gpgShortMessages:	0
gpgShowInline:	none

I suspect the use of "gpgShowInline: all" and/or "gpgKeyQueryMethod: email" 
may be relevant to explaining the behavior you're seeing.

Harv

From: Julian Stacey <jhs <at> berklix.org>
Subject: Enabling GPG Crypt & Key lookup on EXMH 2.7.2
Date: 2008-06-04 23:58:49 GMT
Hi exmh-users <at> redhat.com
I cant get EXMH to integrate with GPG,
( I'm a long term EXMH user, but new to GPG & this list )
EXMH wont recognise & click to decrypt,
I also can't encrypt from within EXMH
(Continue reading)

Klaus Elsbernd | 8 Jun 19:04 2008
X-Face
Picon
Picon

Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2


jhs <at> berklix.org said:
> Interesting, Thanks for the reply :-) A good guess, yes I am in Germany,
> Unfortunately that doesnt seem to be the problem. I have no LANG and LANGUAGE
> in my environment, 
That depends on your default environment. And if there is an option in .gnupg/
gnupg.conf
Setting the variable might be a try. Have a look at the exmh-log. you should 
see, if pgp is called, and if you possible trace the call, you might see the 
the calling environment.

And I would at first try to not use q-client.
additionally, setting "show pgp messages inline" to all and "shotr gnupg 
reports" to off will deliver more info.

Bis dann
Klaus

--

-- 
"Sure, vi is user friendly.
 It's just particular about who it makes friends with." ;-) 
                       _________________________________________________________
Deutsches Forschungszentrum für Künstliche Intelligenz GmbH (DFKI GmbH)
Klaus Elsbernd; System Administrator	| Klaus.Elsbernd <at> dfki.de
Trippstadter Straße 122			| elsbernd <at> dfki.uni-kl.de
67657 Kaiserslautern; Germany		| Fernruf: 0631/20575-586 Fernbild: -582
Geschäftsführung: Prof. Dr. Wolfgang Wahlster (Vorsitzender), Dr. Walter Olthoff
Vorsitzender des AR: Prof. Hans A. Aukes| Amtsgericht Kaiserslautern, HRB 2313 

(Continue reading)

Julian Stacey | 9 Jun 23:28 2008

Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2

Harvey Eneman wrote:
> I've been using exmh with pgp/gpg for many years.  I'm currently 
> using exmh 2.7.2 with gpg 1.4.9 on RedHat (Linux 2.6.9).  Comparing
> your exmh default with mine, I see the following gpg differences:
> 
> gpgCacheIds:	persistent
> gpgKeyQueryMethod:	hkp
> gpgShortMessages:	0
> gpgShowInline:	none
> 
> I suspect the use of "gpgShowInline: all" and/or "gpgKeyQueryMethod: email" 
> may be relevant to explaining the behavior you're seeing.
> 
> Harv

& "Klaus Elsbernd" <elsbernd <at> dfki.uni-kl.de> wrote:

> Setting the variable might be a try. Have a look at the exmh-log. you should 
> see, if pgp is called, and if you possible trace the call, you might see the 
> the calling environment.

I was looking all over for pathname of log till I saw there was a button :-)

> And I would at first try to not use q-client.
> additionally, setting "show pgp messages inline" to all and "shotr gnupg 
> reports" to off will deliver more info.

Thanks both, I've got it working now.  
Well, nearly, with the exception that I have to keep typing passphrase.
q-client is manually running, & I exported the env before calling exmh,
(Continue reading)

Valdis.Kletnieks | 9 Jun 23:35 2008
Picon

Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2

On Mon, 09 Jun 2008 23:28:32 +0200, Julian Stacey said:

> Thanks both, I've got it working now.  
> Well, nearly, with the exception that I have to keep typing passphrase.
> q-client is manually running, & I exported the env before calling exmh,
> & q-client is callable, but but "q-client list" show empty.

That's probably at least partially due to the fact that the last time I touched
the PGP code (and I think I was the last to do so), q-client didn't exist yet.

Look under 'preferences' / 'General PGP Interface' - is the 'Keep PGP
passphrase' button what you're looking for?
_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Harvey Eneman | 9 Jun 23:44 2008
Picon

Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2

Julian,

I'm glad to hear that you've made progress.

jhs <at> berklix.org said:
> Well, nearly, with the exception that I have to keep typing passphrase.

I think you need to set your pgpKeepPass to 1.

Regards,

Harv

From: Julian Stacey <jhs <at> berklix.org>
Subject: Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2
Date: 2008-06-09 21:28:32 GMT
Harvey Eneman wrote:
> I've been using exmh with pgp/gpg for many years.  I'm currently 
> using exmh 2.7.2 with gpg 1.4.9 on RedHat (Linux 2.6.9).  Comparing
> your exmh default with mine, I see the following gpg differences:
> 
> gpgCacheIds:	persistent
> gpgKeyQueryMethod:	hkp
> gpgShortMessages:	0
(Continue reading)

Julian Stacey | 10 Jun 00:34 2008

Re: Enabling GPG Crypt & Key lookup on EXMH 2.7.2

Valdis.Kletnieks <at> vt.edu wrote:
> 
> On Mon, 09 Jun 2008 23:28:32 +0200, Julian Stacey said:
> 
> > Thanks both, I've got it working now.  
> > Well, nearly, with the exception that I have to keep typing passphrase.
> > q-client is manually running, & I exported the env before calling exmh,
> > & q-client is callable, but but "q-client list" show empty.
> 
> That's probably at least partially due to the fact that the last time I touched
> the PGP code (and I think I was the last to do so), 

I'm running exmh-2.7.2 on FreeBSD-6.2

> q-client didn't exist yet.

After 	cd /usr/ports/mail/exmh2 ; make extract	
	ie at architercture neutral level before any customising
	for FreeBSD specific as in 'make patch' called by macros
	of 'make all'
There are just 2 q-client strings:

 lib/extrasInit.tcl:
	{pgp(getextcmd) pgpGetExtCmd {/usr/bin/q-client get %s} {Method to query external passphrase cache}
 lib/extrasInit.tcl:
	{pgp(delextcmd) pgpDelExtCmd {/usr/bin/q-client delete %s} {Method to invalidate external
passphrase cache}

& no more q-client dtrings after make patch.
I would guess Exmh is missing some "q-client put" calls to
(Continue reading)


Gmane