l those hours reading the archives =) I personally use mutt
because of its gpg and mix support, so there's still some interest
--
Johan Andersson <[EMAIL PROTECTED]>, http://johan.nforced.com/
GnuPG public key id: 0x6415B9F7 (1024 bits)
Key fingerprint: CA6F 0720 B0D1 2FBA 74EB 348C 3110 6415 B9F7
msg22391/pgp0.pgp
Description: PGP signature
esearching when this changed. And I suppose this
could be checked at compile time. But autoconf & co are not quite my
friends yet.
So, FWIW, attached is a patch that might be the right thing for you if
you have a newer version of Mixmaster and mutt is acting up.
--
Johan Andersson <[E
when I used a non-english translation for gpg.
Anyway, the solution was to be found in the variable pgp_good_sign.
Check it out, might be the solution if we're lucky :)
--
Johan Andersson <[EMAIL PROTECTED]>, http://johan.nforced.com/
GnuPG public key id: 0x6415B9F7 (1024 bits)
Ke
conds after which a cached
passphrase will expire if not used.
Increase this as much as you dare.
> if you haven't already, i'd highly suggest reading the (very lengthy)
> gnupg user guide, and then reading it again.
I second that! It really is a good read. It
Ok. Just after I sent that mail I somehow got the feeling I had made
a fool out of myself. And yes, I re-read the procmailrc man page and
found out what the 'h' flag is for. Well, that's me, always trying to
be smart. At least this time I learned something :)
--
Johan An
ilter. You need
> of course a second recipe to deliver the mail.
I would rather use formail than grep -v, just in case there should
ever be a non-header line beginning with "Reply-To:"
Something like
| formail -R Reply-To: Stupid-Reply-To:
feels slightly safer.
--
Johan Anderss
it will be set every time a message is opened for display or
replying. But as others have already pointed out, this isn't really a
good idea to begin with.
--
Johan Andersson <[EMAIL PROTECTED]>, GnuPG public key id: 0x6415B9F7
msg21363/pgp0.pgp
Description: PGP signature
