Re: mutt sucks

[Dave Ewart]

On Tuesday, 06.09.2005 at 17:54 -0600, Ben Pearre wrote:

 Made ya look!  Actually I love Mutt, mostly...

You had me worried there, for a moment :-P

 I know this thread is increasingly off-topic, but I'm going to throw
 in my one Mutt annoyance and see if anyone has a solution.  I asked on
 mutt-user a couple of years ago and got no useful reply...
 
 How do I tell Mutt to PGP-encrypt any message for which all recipients
 have keys in my keyring?  I think Kmail does this, so it's really an
 embarassment that Mutt doesn't (didn't?)  support it.  Any hints?  Use
 the Source, Cuke?  I was starting in on that but got distracted by
 research.  D'oh!

There's no explicit option for this, AFAIK.  You can choose to always
encrypt, which I guess will simply fail if you don't have the
appropriate keys.

Alternatively, you could write a short script which reads the output of
gpg --list-keys and writes out part of your ~/.muttrc with hooks to
'always encrypt' for those users.

I don't think there's any reliable way to deal with the situation where
a message sent is to multiple recipients, some of whom you have keys for
and some of whom you do not, though.

How does KMail's logic work there?  I assume it's more than simply
always encrypt?

Dave.
-- 
Please don't CC me on list messages!
...
Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED]
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92



signature.asc
Description: Digital signature

Re: mutt sucks

[Jon Dowland]

On Wed, Sep 07, 2005 at 09:32:31AM +0100, Dave Ewart wrote:
 Alternatively, you could write a short script which reads the output
 of gpg --list-keys and writes out part of your ~/.muttrc with hooks
 to 'always encrypt' for those users.

That sounds like an idea - you could generate a list of send-hook
commands. Here's an example using autosign rather than encrypt:



# in muttrc:
send-hook . 'unset pgp_autosign'
source autosigners.muttrc

# in autosigners.muttrc.in:
send-hook REGEXP 'set pgp_autosign'

# in Makefile
autosigners.muttrc: autosigners.muttrc.in list
sh generate.sh list autosigners.muttrc
list:
gpg --list-keys | do something useful  list

# in generate.sh
for i in `cat list`; do cpp -DREGEXP=$i autosigners.muttrc.in; done



(loosely adapted from something else; will need some fixing)

 I don't think there's any reliable way to deal with the situation
 where a message sent is to multiple recipients, some of whom you have
 keys for and some of whom you do not, though.

In that situation, it'd be pointless to encrypt the message for anyone,
since it would be going out on-the-clear at some point.

-- 
Jon Dowland
http://jon.dowland.name/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]