Re: mutt and gpg group of keys.
Sven Guckes
> In the company I work for, we use several system wide
> group aliases. I created gpg group of keys for those
> aliases, but cannot find how to use them in mutt.
>
> Mutt seems to look for a key in keyring with the
> name of the alias, however this does not exist.
sounds like the "old" mutt which looks up keys forever. so - upgrade.
but if you problem persists then you should create a better problem
decription with names of key aliases as examples.
cannot talk about things without a name, you know.
Sven
Sven Guckes
hmm..
> I send mail to comite-securite and I'd like mutt to use a
> gpg -r comite-securite (defined as a groupe in ~/.gnupg/config)
>
> However it looks for a key named comite-securite
> in keyring, which does not exist.
so why do you expect *mutt* to look into the setup files of *gpg*?
do you suggest that every program should also check the setup files
of all other programs which *may* have a connection to itself? ;-)
Sven
Sven Guckes
>>> gpg -r comite-securite (defined as a groupe in ~/.gnupg/config)
>>> However it looks for a key named comite-securite
>>> in keyring, which does not exist.
>>
>> so why do you expect *mutt* to look into the setup files of *gpg*?
>> do you suggest that every program should also check the setup files
>> of all other programs which *may* have a connection to itself? ;-)
>
doesn't mutt *use? gpg to look at the gpg config files.
> I'd prefer it not to look at all and use the name I
> gave him without trying to check and failing at doing it.
then why don't you define the address an an alias in the muttrc?
Sven
Paul Walker
> Mutt seems to look for a key in keyring with the name of the alias,
> however this does not exist.
The name is the only thing mutt has from which to find a key. What would you
expect it to do? :-)
You might be able to play with send-hooks - override the relevant
pgp_*_command for that alias with a fixed GPG command containing the key ID
you want to use.
--
Paul
Sven Guckes
> Sven Guckes <use...@guckes.net> wrote :
>
>>> I'd prefer it not to look at all and use the name I
>>> gave him without trying to check and failing at doing it.
>>
>> then why don't you define the address an an alias in the muttrc?
>
> if it was possible to make mutt accept to send
> without trying to get a key from the keyring.
mutt trying to make guesses on data? huh?
> Note also that if I make a mutt alias, the mail won't
> bear the alias as To: but the list of addresses which
> may break filtering for recipients (e.g. me).
To: foo
Bcc: alias
Sven