-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday, May 6 at 08:44 PM, quoth Wilkinson, Alex:
> I'm not sure if this is the best way to test from the CLI,
It is.
> but as you can see t-prot doesn't seem to alter the message at all.
Aha! Well, there you have it; not a mutt config problem, but a t-prot
config problem.
> This was a fake message a created for testing:
>
> #cat /var/tmp/test.txt | /usr/local/bin/t-prot -acelmtS -Mmutt --spass
I use t-prot like this: t-prot -cemtwk -M=mutt
Things I observe about how you're using t-prot:
- You're using -a, but you're not using -A, which t-prot requires
(see its documentation)
- You're using -l, but you're not using -L, which t-prot requires
(see its documentation)
I don't know if those are critical, but you should probably fix them.
> Can I run mutt in 'debugging mode' somehow to see what it is
> actually doing ?
I'm pretty sure mutt is using t-prot here; but if t-prot won't alter
the message, there's very little mutt can do about that.
~Kyle
- --
Last comes the beverage of the Orient shore, Mocha, far off, the
fragrant berries bore. Taste the dark fluid with a dainty lip,
Digestion waits on pleasure as you sip.
-- Pope Leo XII
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFGPehzBkIOoMqOI14RApOYAKDFCHP+DxFcEO68gRkFkEeuU8hK+ACg6b+c
qBP0CRUpqB/Rozsv+eEcB0c=
=II+s
-----END PGP SIGNATURE-----
