pgp encryption problem
Hi you all, I'd like to use a not certified public key for encryption. On command line with 'pgp -e filename' this works fine. But out of mutt I get an 'Encryption error': --- cut here - Pretty Good Privacy(tm) Version 6.5.1 Int. (c) 1999 Network Associates Inc. Export of this software may be restricted by the U.S. government. WARNING: Because this public key is not certified with a trusted signature, it is not known with high confidence that this public key actually belongs to: "Fxxx Oxxx Txxx [EMAIL PROTECTED]". Encryption error For a usage summary, type: pgp -h For more detailed help, consult the PGP User's Guide. --- cut here - (I just x'ed out the name and email address) Regards, Daniel.
Adding headers
Is there a way to add headrs to the header menu screen? What I want is to be asked if I want to set the "Followup-To:" header, just like I'm asked if I want to edit the CC or BCC header. it seems that my_hdrs command doesn't do the trick, since it adds the same header to every message. Am I missing something? Thanks, Dan PGP signature
Re: pgp encryption problem
I solved the problem by myself. In batchmode, pgp refuses to use an uncertified key and aborts with this Encryption Error. I just needed to remove the "+batchmode" entry in the pgp encrypt command for mutt. On Thu, Sep 14, 2000 at 02:22:02PM +0200, Daniel Kollar wrote: Date: Thu, 14 Sep 2000 14:22:02 +0200 From: Daniel Kollar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: pgp encryption problem Mail-Followup-To: [EMAIL PROTECTED] Hi you all, I'd like to use a not certified public key for encryption. On command line with 'pgp -e filename' this works fine. But out of mutt I get an 'Encryption error': --- cut here - Pretty Good Privacy(tm) Version 6.5.1 Int. (c) 1999 Network Associates Inc. Export of this software may be restricted by the U.S. government. WARNING: Because this public key is not certified with a trusted signature, it is not known with high confidence that this public key actually belongs to: "Fxxx Oxxx Txxx [EMAIL PROTECTED]". Encryption error For a usage summary, type: pgp -h For more detailed help, consult the PGP User's Guide. --- cut here - (I just x'ed out the name and email address) Regards, Daniel.
Re: Adding headers
On Thu, Sep 14, 2000 at 09:34:08AM -0400, Dan Boger wrote: Is there a way to add headrs to the header menu screen? What I want is to be asked if I want to set the "Followup-To:" header, just like I'm asked if I want to edit the CC or BCC header. it seems that my_hdrs command doesn't do the trick, since it adds the same header to every message. Have you tried 'set edit_headers' and editing the header during message editing? -- - Bruce
Re: Adding headers
On Thu, Sep 14, 2000 at 10:17:46AM -0400, Bruce DeVisser wrote: On Thu, Sep 14, 2000 at 09:34:08AM -0400, Dan Boger wrote: Is there a way to add headrs to the header menu screen? What I want is to be asked if I want to set the "Followup-To:" header, just like I'm asked if I want to edit the CC or BCC header. it seems that my_hdrs command doesn't do the trick, since it adds the same header to every message. Have you tried 'set edit_headers' and editing the header during message editing? yes, but that just let's me type them in the message, it doesn't add it to the post edit menu... I could use this, just not optimal... :) Dan PGP signature
mutt cannot send subject line Hello, I am using OpenBSD 2.7 with Mutt 1.1us - here's the details:
Compile options: -DOMAIN -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL The problem is that mutt does not send the specified subject line but sends nothing i nstead ( not even a simbol ). Now I am sending this from the comman line with sendmail and th e subject is fine. Where can the problem be? Below is my muttrc file # # My muttrc file # set abort_nosubject=ask-yes set fast_reply=no set hdrs=yes unmy_hdr # Key bindings bind pager Up previous-line bind pager Down next-line bind pager PageUp previous-page bind pager PageDn next-page bind pager Right next-entry bind pager Left previous-entry # Mailing lists lists [EMAIL PROTECTED] lists [EMAIL PROTECTED] lists [EMAIL PROTECTED] lists [EMAIL PROTECTED] lists [EMAIL PROTECTED] # Mailboxes SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL The problem is that mutt does not send the specified subject line but sends nothing i nstead ( not even a simbol ). Now I am sending this from the comman line with sendmail and th e subject is fine. Where can the problem be? Below is my muttrc file # # My muttrc file # set
save-hook works, but...
Hi,
I'm running mutt 1.2.5 and I have something really odd. I have
two save hooks:
save-hook sgi.com =work
save-hook cray.com =work
My intention is to have mail from those addresses default to my work
mailbox. When I hit 's' I get the following at the bottom of the screen:
Save to mailbox ('?' for list): =work
This is what I'm expecting. However, when I hit return to actually save,
the line clears and nothing happens -- as if I aborted the save.
Yet when I hit ctrl-J instead of return, it accepts that I want to
save it to my work mailbox.
Am I trying to use this in an unexpected way? This seems really odd to me.
Dean
Re: save-hook works, but...
Dean Luick [EMAIL PROTECTED] wrote on Thu, 14 Sep 2000:
Save to mailbox ('?' for list): =work
This is what I'm expecting. However, when I hit return to actually save,
the line clears and nothing happens -- as if I aborted the save.
Yet when I hit ctrl-J instead of return, it accepts that I want to
save it to my work mailbox.
Am I trying to use this in an unexpected way? This seems really odd to me.
The problem is likely not at all related to your save-hooks. Does this
happen even with other emails, when you press s to save them? Does
entering text at other prompts work?
My guess would be that there's something wrong with your keyboard
definitions. The active keymap at that save-prompt is the editor..
Unfortunately there is no way in Mutt to view the editor keymap
definitions. :-(
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs /
Zimmerman's Law of Complaints: Nobody notices when things go right.
Translation How-To?
Hi, I'm trying to find out how I can get mutt to speak French, but I'm getting more and more confused about it. I'm sorry I didn't find much doc about translation issues. Here's the situation: - I have access to 2 different Unix accounts where I'm a non-privileged user : one is running Linux, the other Solaris - if I use the system-mutt on any of these accounts (both are 1.0), messages are displayed in French - I've installed Mutt 1.2.5i on both accounts (non-privileged user) from the tarball, with minimum configure options (prefix=$HOME, with-slang). On the Solaris box, I come up with a French-speaking mutt, on the Linux box it sticks to English. - I've also tried to use the --with-enable-gettext configure option under Linux, but that doesn't change a thing. Are there environment variables I need to set in order to have French language used? If so, how come /usr/bin/mutt is French and ~/bin/mutt isn't (Linux)? Do I need to do more than ./configure; make; make install ? That's all I had to do on the Solaris box to get a French Mutt... FWIW, here are the versions for /usr/bin/mutt and ~/bin/mutt (under Linux): %/usr/bin/mutt -v Mutt 1.0.1i (2000-01-18) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.2.16 [using slang 10202] Options de compilation : -DOMAIN -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_GPG -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/var/tmp/mutt-root/etc" SYSCONFDIR="/var/tmp/mutt-root/etc" -ISPELL _PGPPATH="/usr/bin/gpg" _PGPGPGPATH="/usr/bin/gpg" Pour contacter les développeurs, veuillez écrire à [EMAIL PROTECTED]. %mutt -v Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.2.16 [using slang 10202] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="~colinet/lib/mutt" SYSCONFDIR="~colinet/etc" ISPELL="/usr/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. %locale LANG=fr_FR LC_CTYPE="fr" LC_NUMERIC="fr" LC_TIME="fr" LC_COLLATE="fr" LC_MONETARY="fr" LC_MESSAGES="fr" LC_ALL=fr Any help appreciated. -- Renaud
Translation How-To?
Hi I'm trying to find out how I can get mutt to speak French, but I'm getting more and more confused about it. I'm sorry I didn't find much doc about translation issues. Here's the situation: - I have access to 2 different Unix accounts where I'm a non-privileged user : one is running Linux, the other Solaris - if I use the system-mutt on any of these accounts (both are 1.0), messages are displayed in French - I've installed Mutt 1.2.5i on both accounts (non-privileged user) from the tarball, with minimum configure options (prefix=$HOME, with-slang). On the Solaris box, I come up with a French-speaking mutt, on the Linux box it sticks to English. - I've also tried to use the --with-enable-gettext configure option under Linux, but that doesn't change a thing. Are there environment variables I need to set in order to have French language used? If so, how come /usr/bin/mutt is French and ~/bin/mutt isn't (Linux)? Do I need to do more than ./configure; make; make install ? That's all I had to do on the Solaris box to get a French Mutt... FWIW, here are the versions for /usr/bin/mutt and ~/bin/mutt (under Linux): %/usr/bin/mutt -v Mutt 1.0.1i (2000-01-18) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.2.16 [using slang 10202] Options de compilation : -DOMAIN -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_GSS +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_GPG -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/var/tmp/mutt-root/etc" SYSCONFDIR="/var/tmp/mutt-root/etc" -ISPELL _PGPPATH="/usr/bin/gpg" _PGPGPGPATH="/usr/bin/gpg" Pour contacter les développeurs, veuillez écrire à [EMAIL PROTECTED]. %mutt -v Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.2.16 [using slang 10202] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="~colinet/lib/mutt" SYSCONFDIR="~colinet/etc" ISPELL="/usr/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. %locale LANG=fr_FR LC_CTYPE="fr" LC_NUMERIC="fr" LC_TIME="fr" LC_COLLATE="fr" LC_MONETARY="fr" LC_MESSAGES="fr" LC_ALL=fr Any help appreciated. -- Renaud
Re: signature detection for color and mono
Bya godzina 23:09:20 w roda 13 wrzesie, gdy do autobusu wsiad kanar i wrzasn:"David Champion!!! Bilecik do kontroli!!!" A on(a) na to: Is there any way to disable this? I want the pager to treat signatures the same as the body Correct me if i am wrong you do not wan colorful signature? If so do in your .muttrc this: color white black This will make signatures be written with white (gray) letters on black background. For more information see manual Sec. 3.6 HANDON -- |/ |_, _ .- --,2:480/135@fido[EMAIL PROTECTED] |__ |_|. | \ |_|. ._' /_. 101:1000/135@unholy ... Droga wrd jaboni prowadzi w nieznane...
Re: signing with PGP
Bya godzina 01:48:43 w czwartek 14 wrzesie, gdy do autobusu wsiad kanar i wrzasn:"Lars Hecking!!! Bilecik do kontroli!!!" A on(a) na to: i save parts of message into separate files and i invoke "$ gpg --verify sigfile textfiel" i get an error. What's up? Any one knows? The signature is created over the whole body, including MIME headers (but excluding the application/pgp-signature part, obviously :) You mean everything what is between part delimiters? Thank you. Bye. -- |/ |_, _ .- --,2:480/135@fido[EMAIL PROTECTED] |__ |_|. | \ |_|. ._' /_. 101:1000/135@unholy ... Od tej pory wszystko moe si zdarzy. Akcja toczy si...
Re: signature detection for color and mono
On 2000.09.14, in [EMAIL PROTECTED], "Lukasz Stelmach" [EMAIL PROTECTED] wrote: By³a godzina 23:09:20 w ¶roda 13 wrzesieñ, gdy do autobusu wsiad³ kanar i wrzasn±³:"David Champion!!! Bilecik do kontroli!!!" A on(a) na to: Is there any way to disable this? I want the pager to treat signatures the same as the body Correct me if i am wrong you do not wan colorful signature? If so do in Correct, but I also want my body regexes to color parts of the signature -- I don't want it treated as a single big block. The thing is: I have directions in .muttrc for coloring URLs and email addresses differently from the surrounding text. These often appear in signatures, and I'd like them similarly highlighted there. I think this requires a code patch, but not a major one. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
