Re: mutt too stateful w/gpg?

Eric Osborne muttered: > ## pgp stuff > pgp-hook '^foo' [EMAIL PROTECTED] # add this on here: send-hook . "unset pgp_autoencrypt pgp_autosign" > #set pgp_autosign > send-hook foo "set pgp_autoencrypt pgp_autosign" > set pgp_replyencrypt# Encrypt replies on encrypted mail > set pgp_reply

Result: Maildir/procmail/Mutt/mutt -y/mailboxes

Thanks guys for hint and comment: Ben Reser <[EMAIL PROTECTED]>, Ken Rachynski <[EMAIL PROTECTED]> Mikko H?nninen <[EMAIL PROTECTED]> Following is what I ended up for my Mutt 1.2.5i (debian-woody). Now it start with "mutt", "mutt -y" or "mutt -z" without hitch. > My mail comes as foll

linebreak as `=20'

Why do some mail messages I receive show carriage returns/line breaks as `=20' ? Is my mutt setup misconfigured, or is this totally unrelated to mutt? -- TIA

Re: linebreak as `=20'

On Sat, Sep 30, 2000 at 04:14:18PM -0500, the/eXtreme wrote: > Why do some mail messages I receive show carriage returns/line breaks > as `=20' ? Is my mutt setup misconfigured, or is this totally unrelated > to mutt? This is a type of MIME encoding called quoted-printable. Mutt handles it just

Re: linebreak as `=20'

can anyone come up with a procmail/formail recipe that will automatically detect these things & add such a header line? i tried this, but everything ended up in /dev/null: ## :0: * =20 |formail -i "Content-Transfer-Encoding: quoted-printable" >>testing ## (besides this is too draconian b

Re: linebreak as `=20'

On 2000.09.30, in <2930210156.A2463@sol>, "Peter Jaques" <[EMAIL PROTECTED]> wrote: > can anyone come up with a procmail/formail recipe that will automatically > detect these things & add such a header line? i tried this, but everything > ended up in /dev/null: > > ## > :0: > * =2