Reply-to-all function?
It seems mutt's default behavior when replying to a message is to only put the sender in the To: header. Is there a way to add Cc: recipients as well? -Chris -- --- Christopher A. Woodfield[EMAIL PROTECTED] Finger for public PGP key 0xB887618B - email for fingerprint PGP signature
Re: Controlling default in save command?
Ok, I think I'm having trouble understanding the conecpt of the hooks. Can someone try to explain it a bit better than the manual does? -C On Mon, May 15, 2000 at 09:10:55PM +0200, Steffan Hoeke wrote: You could use save-hook with, for example save-hook "[EMAIL PROTECTED]" +target or save-hook "~f [EMAIL PROTECTED]" +target or save-hook "~C [EMAIL PROTECTED]" +target Take a look at http://www.mutt.org/doc/manual/manual-3.html#ss3.14 HTH, Steffan On Mon, May 15, 2000 at 01:51:19PM -0400, Chris Woodfield muttered: How does one control the default string that's populated when you save a message? Or in my case, not have one? At the moment (usint the default .muttrc), the default is "=username". My ideal would be the default to be the argument given with the last save command (like pine)... -Chris --- Christopher A. Woodfield[EMAIL PROTECTED] Finger for public PGP key 0xB887618B - email for fingerprint -- http://therookie.dyndns.org -- --- Christopher A. Woodfield[EMAIL PROTECTED] Finger for public PGP key 0xB887618B - email for fingerprint
Controlling default in save command?
How does one control the default string that's populated when you save a message? Or in my case, not have one? At the moment (usint the default .muttrc), the default is "=username". My ideal would be the default to be the argument given with the last save command (like pine)... -Chris --- Christopher A. Woodfield[EMAIL PROTECTED] Finger for public PGP key 0xB887618B - email for fingerprint
Re: mutt-1.2: imap/ssl certificates
Me three. I'm running the latest version of OpenSSH for Linux, on a libc5 machine. I wonder if libc5 could be the issue...however, I don't have access to a glibc2 machine that has access to a IMAP/SSL server to test. -C On Thu, May 11, 2000 at 06:23:47PM +0300, Tommi Komulainen wrote: On Wed, May 10, 2000 at 02:05:30PM +0200, Andre Wobst wrote: I've troubles with the imap ssl certificates, saved in the file certificate_file, which I set to ~/.mutt.certificate_file in my ~/.muttrc. If I do so, I can accept a certificate not only once but always (otherwise this option isn't available). The certificate is stored in the file ~/.mutt.certificate_file. But next time I start mutt again, it asks me again for the certificate check. If I accept it again, the certificate is again added to the file ~/.mutt.certificate_file and it is exactly the same like before -- now stored twice in the same file. How can I store the certificate that way, that mutt acceptes it automatically next time -- what's wrong in the way I'm doing it? You're the second person reporting this erratic behaviour. Unfortunately I have no idea what is going on. The certificate checking is done completely with SSL-library functions. So, either I'm doing something wrong, or those functions are broken on your platform. I think the first option is more likely but I'm yet to figure out why it goes wrong, and only in some cases. Feel free to send any suggestions directly to me or to mutt-dev mailing list. -- Tommi Komulainen [EMAIL PROTECTED] -- --- Christopher A. Woodfield[EMAIL PROTECTED] Finger for public PGP key 0xB887618B - email for fingerprint
pkspxycwrap?
What is this and where does one find it? It's in the pgp6.rc file: # fetch keys set pgp_getkeys_command="pkspxycwrap %r" ... but it sure as tootin' ain't in MY distribution of pgp v6...and I get a "command not found" error every time I try to decrypt or verify a signature. BTW, my copy of PGP is the PGP Command Line Freeware relase for Linux, v6.5.2. And in other news...how does one set a "default" server to use? For example, have mutt go directly to an IMAP server instead of having to c? to it? --- Christopher A. Woodfield[EMAIL PROTECTED] Finger for public PGP key 0xB887618B - email for fingerprint
Re: PGP error messages
On Fri, Jan 21, 2000 at 05:10:38PM +, Lars Hecking wrote:
Error in /home/jmnova3/.muttrc, line 102: pgp_v2: unknown variable
Error in /home/jmnova3/.muttrc, line 103: pgp_v2_language: unknown variable
Error in /home/jmnova3/.muttrc, line 104: pgp_v2_pubring: unknown variable
Error in /home/jmnova3/.muttrc, line 105: pgp_v2_secring: unknown variable
Error in /home/jmnova3/.muttrc, line 106: pgp_default_version: unknown variable
Error in /home/jmnova3/.muttrc, line 107: pgp_receive_version: unknown variable
Error in /home/jmnova3/.muttrc, line 108: pgp_send_version: unknown variable
Error in /home/jmnova3/.muttrc, line 109: pgp_key_version: unknown variable
source: errors in /home/jmnova3/.muttrc
Press any key to continue...
Now I *know* these variables work for other people, because I've looked
through the example .rc files linked from the mutt.org website. What am
I doing wrong?
Now I *know* these variables won't work for this version of mutt because
the pgp/gpg interface changed between 1.0 and 1.1 (or 0.95/0.96).
See doc/PGP-Notes.txt and contrib/{gpg,pgp2,pgp5}.rc, and the usual
funny manual.
Going through the archives, I found this mail, which mirrors exactly the
errors I'm getting. I'm running 1.0.1-us.
Funny thing is, all of these variables are referred to in the
doc/manual.txt file, except for the pgp_v2* variables. I can't even put
the pgp_default_version variable in my .muttrc without getting the unkown
variable editor.
THe other thing is that according to said doc/manual.txt, the only options
for pgp_default_version are pgp2, pgp5, and gpg. I just installed
6.5.2...am I going to be able to use that, or do I have to roll back to
5.x?
-Chris Woodfield
