-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday, May 7 at 01:31 PM, quoth Haines Brown:
> I guess the most straightforward procedure would be to rely on
> procmail to direct incoming mail to differet inboxes that rmail and
> mutt can access.
Probably, yup.
> You were kind to reply, but your message starts with the set of lines
> below.
No, my message actually *doesn't* start with those lines. Those are
something that your mutt displayed because it tried to verify my PGP
signature. I use PGP (or, more specifically, GnuPG) to sign all of my
messages. Since you don't have gpg set up properly, gpg was unable to
verify my signature, and that's essentially what it's telling you.
If you don't like seeing that junk at the top of messages, you should
either set up gpg correctly OR you should change your mutt
configuration so that it doesn't attempt to verify all signatures
(e.g. set crypt_verify_sig=no).
> And then I go to reply to your message within mutt, and my reply is
> aborted when an editor should show up. So I had to retreat to rmail
> for this reply.
That happened for the same reason: you have told mutt that it *must*
verify pgp signatures, but then you didn't set up gpg so that mutt
*could*. Either don't tell mutt that it must verify pgp signatures OR
set up gpg so that it can do as you've told it.
Put another way, you've essentially placed mutt in a round room (i.e.
a computer without gpg set up properly) and told it "whenever a
message with a signature arrives, go stand in the corner (i.e. verify
that signature)". My message had a signature, and so mutt went crazy
trying to find a corner to stand in. Of course, since it's in a round
room, it failed miserably.
So, either put mutt in a room with a corner (e.g. set up gpg
correctly) OR don't tell mutt to stand in a corner whenever messages
with signatures show up (e.g. set crypt_verify_sig=no).
Does that make sense?
> To save a message in mutt, if I hit the "s" key I'm prompted for a
> mailbox.
Yup - that's how you can move messages between folders.
> However I'm used to saving messages as a plain text that I can name
> and put into a default directory,
Why would you do that?
> and if I page back to use the same saveAs... name, the message is
> appended to the previous one with the same name.
...right... because you've essentially told mutt "copy the message
into the mailbox that I specify by name, and delete the version of the
message in the current mailbox". When you do that, mutt has to figure
out what kind of mailbox you've told it to copy the message into. By
giving it the name of a file that already exists, mutt is forced to
assume that it's saving the message into an mbox-style mailbox, and so
must append the message to the end of that file.
> As best I can make out, that is done with save-hook, I suppose, but
> not sure how to call that function.
I think you're confused; save-hook has nothing to do with this.
What are you trying to accomplish by saving messages as text files?
And why are you trying to tell mutt to save them all with the same
name?
It sounds like you have some rather unusual "backup" or "archive"
scheme that you're trying to adhere to, and my bet is that there is a
MUCH easier way to do the same thing. If you explain what it is that
you're trying to accomplish with this "default folder of text files",
maybe we can help.
~Kyle
- --
I created a cron job to remind me of the Alamo.
-- Arun Rodrigues
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkoDMCUACgkQBkIOoMqOI168+ACfQlcd65MHYUe6oyBz5srj03E/
uYQAoNlHfqW8BVPrYZcGl2OdjY9sTSUW
=CDMj
-----END PGP SIGNATURE-----
