GPG 1.0.3 and mutt
I recently decided to try GnuPG after using only pgp2 off and on for some years. It was only after I downloaded it and played with it for a while, that I realised that version 1.0.3 was very recent. I had got in right at the beginning of a new version. This new version incorporates RSA which I understand came out of copyright only in September. This allows one I gather to encrypt in a manner compatible with pgp2. The gpg.rc script assumes the use of gpg-2comp and this assumes that RSA patches to gpg have been installed. Version 1.0.3 appears to alter the whole game. So my question is this - what do we have to use in place of gpg.rc. Has anybody given this any thought or has anyone who used an earlier version of gpg got any war stories about upgrading to 1.0.3? Now an extra question. I always get "gpg: Please note that you don't have secure memory on this system". I added "no-secmem-warning" to ~/.gnupg/options as suggested and I then made gpg suid root. I still get the error message. Any ideas? Cheers, Brian. -- Associate Professor Brian Salter-Duke (Brian Duke) [EMAIL PROTECTED] Chemistry, School of BECS, SITE, NT University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847. http://www.smps.ntu.edu.au/ Get PGP2 Key:- http://www.smps.ntu.edu.au/chemistry/duke.key.html
FEATURE-REQUEST: mutt looks for PGPPASS environment variable
Hello mutt-developers, here is a feature request for future versions of mutt: Mutt looks for the PGPPASS environment variable. If this is set, then no passphrase is needed to be send to pgp program, because pgp looks for the PGPPASS variable by itself. Mutt will also not ask the user for the passphrase. This should be easy to implement. The user would then have the option to set the passphrase via a wrapper-script permanently. For example: muttwrap --- #!/usr/bin/sh set $passparam=$* if ( ps -U $LOGNAME | grep mutt | grep -v muttwrap /dev/null ) then echo "WARNING: You are already running Mutt." echo " Starting Mutt in readonly mode." echo echo "Please enter passphrase: " stty -echo read pgppassphrase PGPPASS=$pgppassphrase; export PGPPASS stty echo $PATHTOMUTT/mutt -R $* else echo "Please enter passphrase: " stty -echo read pgppassphrase PGPPASS=$pgppassphrase; export PGPPASS stty echo $PATHTOMUTT/mutt $passparam fi -- Thank you very much! Regards, Daniel.
editing mails, then save it instead of sending
I use mutt since some months and has all the features I can imagine. Great. But one thing I am missing: Sometimes I want to edit a mail, and then save it. I think it is only possible to edit and resend it. (OK, I could resent it to myself, but that's not a nice solution) Has someone an solution? -- Thomas Guettler Office: [EMAIL PROTECTED] www.interface-business.de Private:[EMAIL PROTECTED] http://yi.org/guettli
Re: editing mails, then save it instead of sending
Thomas Guettler proclaimed on mutt-users that: mail, and then save it. I think it is only possible to edit and resend it. (OK, I could resent it to myself, but that's not a nice solution) Has someone an solution? You can postpone messages. mallet@mjollnir~ grep postpone .muttrc set postponed=+postponed# mailbox to store postponed messages set recall # prompt to recall postponed messages -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI What is worth doing is worth the trouble of asking somebody to do.
Re: GPG 1.0.3 and mutt
Brian Salter-Duke wrote: I recently decided to try GnuPG after using only pgp2 off and on for some years. It was only after I downloaded it and played with it for a while, that I realised that version 1.0.3 was very recent. I had got in right at the beginning of a new version. This new version incorporates RSA which I understand came out of copyright only in September. i don't know but note: 1.0.3 has a nasty bug that can cause signatures to be verified that shouldn't (if there are multiple signatures). use 1.0.4 instead. Now an extra question. I always get "gpg: Please note that you don't have secure memory on this system". I added "no-secmem-warning" to ~/.gnupg/options as suggested and I then made gpg suid root. I still get the error message. Any ideas? it means that's your machine doesn't have the mlock() system call or that the gpg compile was configured to believe that you don't have it. i.e. HAVE_MLOCK wasn't defined. you can't turn this message off without recompiling gpg to use mlock() (if you do have it). raf
color
I'm trying to set up color with mutt (1.2.5i) but I am getting "color: unknown command" errors from my muttrc. Is there some trick that I'm missing? Mike -- Mike Ericksonmee@quidquam http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: FEATURE-REQUEST: mutt looks for PGPPASS environment variable
Don't do that. Storing the pgp pass phrase in an environment variable may have been a valid option on MS-DOS computers. It isn't on Unix machines, since the environment is not guaranteed to be confidential. Also, what's the point in using a shell script like the one below? - There is no reason to avoid running two mutts on the same mailbox. Mutt _does_ know how to graciously deal with concurrent access to mail folders. - There is no point in asking for the pass phrase in a shell script, and then storing it in $PGPPASS. Mutt will ask for the pass phrase the first time it's needed, and remember it for the coming $pgp_timeout seconds. The default is 300 seconds; you can easily change that from your .muttrc. Note that the mechanism mutt uses to pass the pass phrase to pgp _is_ safe against eavesdropping by other users on the same system. On 2000-10-20 10:21:20 +0200, Daniel Kollar wrote: Date: Fri, 20 Oct 2000 10:21:20 +0200 From: Daniel Kollar [EMAIL PROTECTED] To: Mutt User List [EMAIL PROTECTED] Subject: FEATURE-REQUEST: mutt looks for PGPPASS environment variable Mail-Followup-To: Mutt User List [EMAIL PROTECTED] User-Agent: Mutt/1.2i Hello mutt-developers, here is a feature request for future versions of mutt: Mutt looks for the PGPPASS environment variable. If this is set, then no passphrase is needed to be send to pgp program, because pgp looks for the PGPPASS variable by itself. Mutt will also not ask the user for the passphrase. This should be easy to implement. The user would then have the option to set the passphrase via a wrapper-script permanently. For example: muttwrap --- #!/usr/bin/sh set $passparam=$* if ( ps -U $LOGNAME | grep mutt | grep -v muttwrap /dev/null ) then echo "WARNING: You are already running Mutt." echo " Starting Mutt in readonly mode." echo echo "Please enter passphrase: " stty -echo read pgppassphrase PGPPASS=$pgppassphrase; export PGPPASS stty echo $PATHTOMUTT/mutt -R $* else echo "Please enter passphrase: " stty -echo read pgppassphrase PGPPASS=$pgppassphrase; export PGPPASS stty echo $PATHTOMUTT/mutt $passparam fi -- Thank you very much! Regards, Daniel. -- Thomas Roessler [EMAIL PROTECTED]
Re: GPG 1.0.3 and mutt
On Fri, Oct 20, 2000 at 05:02:57PM +0930, Brian Salter-Duke wrote: I recently decided to try GnuPG after using only pgp2 off and on for some years. It was only after I downloaded it and played with it for a while, that I realised that version 1.0.3 was very recent. I had got in right at the beginning of a new version. This new version incorporates RSA which I understand came out of copyright only in September. This allows one I gather to encrypt in a manner compatible with pgp2. I don't know abou that, as I have not generated a new key pair. The man page does not indicate any commands specific to "RSA". I do know that I can now verify email signed with an RSA key, which was my main interest in 1.0.3. The gpg.rc script assumes the use of gpg-2comp and this assumes that RSA patches to gpg have been installed. Version 1.0.3 appears to alter the whole game. So my question is this - what do we have to use in place of gpg.rc. Has anybody given this any thought or has anyone who used an earlier version of gpg got any war stories about upgrading to 1.0.3? I have not changed it in the least. However, I have had no reason to do so. Perhaps someone who uses an RSA-only version of PGP would ask me to do so, then I would have to dink with it. Or tell them to upgrade to GPG. :-) Now an extra question. I always get "gpg: Please note that you don't have secure memory on this system". I added "no-secmem-warning" to ~/.gnupg/options as suggested and I then made gpg suid root. I still get the error message. Any ideas? Sorry, no ideas here. -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley PGP signature
Re: FEATURE-REQUEST: mutt looks for PGPPASS environment variable
Don't do that. Storing the pgp pass phrase in an environment variable may have been a valid option on MS-DOS computers. It isn't on Unix machines, since the environment is not guaranteed to be confidential. I'm working on unix. In the PGP CmdLineGuide you will find a section about this. There you can read that using this feature is safe when you use in in a environment where no one else has access to it. I'm doing that. The environment is only active as long as mutt is open. No one from outside can access it. The wrapper script asks me for entering the passphrase and starts mutt immedeately after this. So, it is safe. The only thing a would agree is that someone can change the wrapper script to send the passphrase via email to outside... Also, what's the point in using a shell script like the one below? - There is no reason to avoid running two mutts on the same mailbox. Mutt _does_ know how to graciously deal with concurrent access to mail folders. - There is no point in asking for the pass phrase in a shell script, and then storing it in $PGPPASS. Mutt will ask for the pass phrase the first time it's needed, and remember it for the coming $pgp_timeout seconds. The default is 300 seconds; you can easily change that from your .muttrc. Maybe you have read my previous email regarding the mutt_octet-filter which can decrypt pgp encrypted octet-streams. The PGPPASS environment variable is the easiest way to remember the passphrase. But now I have to enter the passphrase two times. One for my octet-filter and one for mutt. What solution to you see? Daniel.
Re: GPG 1.0.3 and mutt
On Fri, Oct 20, 2000 at 05:02:57PM +0930, Brian Salter-Duke wrote: I recently decided to try GnuPG after using only pgp2 off and on for some years. It was only after I downloaded it and played with it for a while, that I realised that version 1.0.3 was very recent. I had got in right at the beginning of a new version. This new version incorporates RSA which I understand came out of copyright only in September. This allows one I gather to encrypt in a manner compatible with pgp2. I believe the gpg only deciphers with RSA, and doesn't encrypt using it. Sorry, but I wouldn't know anything about pgp2 though... -- Dan Boger System Administrator [EMAIL PROTECTED] PGP signature
Re: editing mails, then save it instead of sending
On Fri, Oct 20, 2000 at 11:00:01AM +0200, Thomas Guettler wrote: I use mutt since some months and has all the features I can imagine. Great. But one thing I am missing: Sometimes I want to edit a mail, and then save it. I think it is only possible to edit and resend it. (OK, I could resent it to myself, but that's not a nice solution) Has someone an solution? e edit edit the raw message so just hit 'e' on the message you want to edit it'll open it up in your editor, and put the modified message right after the old one, with the old message marked for deletion... or is that not what you meant? -- Dan Boger System Administrator [EMAIL PROTECTED] PGP signature
Re: GPG 1.0.3 and mutt
Dan Boger writes: On Fri, Oct 20, 2000 at 05:02:57PM +0930, Brian Salter-Duke wrote: I recently decided to try GnuPG after using only pgp2 off and on for some years. It was only after I downloaded it and played with it for a while, that I realised that version 1.0.3 was very recent. I had got in I strongly suggest to use 1.0.4 instead. All versions up to and including 1.0.3 have a serious bug: Noteworthy changes in version 1.0.4 (2000-10-17) * Fixed a serious bug which could lead to false signature verification results when more than one signature is fed to gpg. This is the primary reason for releasing this version. [...] right at the beginning of a new version. This new version incorporates RSA which I understand came out of copyright only in September. This allows one I gather to encrypt in a manner compatible with pgp2. I believe the gpg only deciphers with RSA, and doesn't encrypt using it. Sorry, but I wouldn't know anything about pgp2 though... This is correct. Noteworthy changes in version 1.0.3 (2000-09-18) [...] * RSA is supported. Key generation does not yet work but will come soon.
Re: FEATURE-REQUEST: mutt looks for PGPPASS environment variable
On Fri, Oct 20, 2000 at 01:51:13PM +0200, Daniel Kollar wrote: In the PGP CmdLineGuide you will find a section about this. There you can read that using this feature is safe when you use in in a environment where no one else has access to it. I'm doing that. The environment is only active as long as mutt is open. No one from outside can access it. The wrapper script asks me for entering the passphrase and starts mutt immedeately after this. So, it is safe. The only thing a would agree is that someone can change the wrapper script to send the passphrase via email to outside... what about people accessing mutt's enviroment through the proc filesystem? or via strace? "an enviroment where no one else has access to it" ususally means a standalone computer, or one where you are the ONLY user (including root)... if it's a multi user machine, your env isn't safe. -- Dan Boger System Administrator [EMAIL PROTECTED] PGP signature
Re: FEATURE-REQUEST: mutt looks for PGPPASS environment variable
On 2000-10-20 13:51:13 +0200, Daniel Kollar wrote: I'm doing that. The environment is only active as long as mutt is open. No one from outside can access it. That's your particular environment. However, mutt is designed in a way which makes it suitable for use on real multi-user systems. You'll understand that we won't encourage practices which are extremely unsafe on such systems - users will get used to these pratices, and run into traps on real multi-user systems. The only thing a would agree is that someone can change the wrapper script to send the passphrase via email to outside... If someone can let you execute Trojan programs or scripts, you have a problem anyways. Maybe you have read my previous email regarding the mutt_octet-filter which can decrypt pgp encrypted octet-streams. The PGPPASS environment variable is the easiest way to remember the passphrase. Did you try to change the content-type of these octet-streams to application/pgp? With the more recent mutt versions, you can comfortably do this from within mutt. -- Thomas Roessler [EMAIL PROTECTED]
Re: editing mails, then save it instead of sending
Thomas Guettler [EMAIL PROTECTED] wrote on Fri, 20 Oct 2000: I use mutt since some months and has all the features I can imagine. Great. But one thing I am missing: Sometimes I want to edit a mail, and then save it. I think it is only possible to edit and resend it. (OK, I could resent it to myself, but that's not a nice solution) Has someone an solution? Yes, upgrade to 1.2.5, which has a nice "edit-message" function. Actually, the same functionality is in 1.0.1 too, when you select a message for "edit and resend", you can use the w(rite) command to write it back to the folder. After that you can then quit the message without sending it. But the edit-message function in 1.2.5 is much nicer. 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 / A mind is a terrible thing to ... er ... h?
Re: FEATURE-REQUEST: mutt looks for PGPPASS environment variable
From a bash prompt, try running: COLUMNS= ps ae | grep mutt and see if you don't change your mind about using PGPPASS. -- Bob Bell [EMAIL PROTECTED] - "Just don't create a file called -rf. :-)" -- Larry Wall, creator of the Perl programming language
Re: color
On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: I'm trying to set up color with mutt (1.2.5i) but I am getting "color: unknown command" errors from my muttrc. Is there some trick that I'm missing? Perhaps you should try colour instead :) Seriously, can you post a few lines before and after the color statement?
Re: color
On Fri, Oct 20, 2000 at 10:50:03PM +0800, Anthony Liu wrote:
On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote:
I'm trying to set up color with mutt (1.2.5i) but I am getting
"color: unknown command" errors from my muttrc. Is there some trick
that I'm missing?
Perhaps you should try colour instead :)
Seriously, can you post a few lines before and after the color
statement?
Here ya go: (`r!cat ~/.muttrc | grep -5 color` -- gotta love vi)
# set index format string
set index_format="%4C %Z %{%b %d} %-15.15F (%4l) %s"
# COLOR
color quoted brightblue default
color signature red green
color indicator green black
color error brightred default
color status yellow blue
color tree magenta default
color tilde magenta default
color message brightcyan default
color markers brightcyan brightblue # Should be default for val 2
color attachment brightmagenta default
color search default green
color header brightred default ^(From|Subject):
color body magenta default "(ftp|http)://[^ ]+" # point out URLs
color body magenta default [-a-z_0-9.]+@[-a-z_0-9.]+# e-mail addresses
color underline brightgreen default
# KEY BINDINGS
bind index j next-entry
bind index k previous-entry
bind pager j next-entry
Mike
--
Mike Ericksonmee@quidquam http://www.quidquam.com/
"Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: color
On 20 Oct 2000, at 22:50, Anthony Liu wrote: On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: I'm trying to set up color with mutt (1.2.5i) but I am getting "color: unknown command" errors from my muttrc. Is there some trick that I'm missing? Perhaps you should try colour instead :) Seriously, can you post a few lines before and after the color statement? Hi, Actually, it sounds like color support has been turned off. What does the output from "mutt -v" show. Specifically, what curses lib is your mutt built against and does "mutt -v" show +HAVE_COLOR or -HAVE_COLOR? -Harold -- "Life sucks, deal with it!"
Re: color
On Fri, Oct 20, 2000 at 10:29:17AM -0600, Harold Oga wrote: On 20 Oct 2000, at 22:50, Anthony Liu wrote: On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: I'm trying to set up color with mutt (1.2.5i) but I am getting "color: unknown command" errors from my muttrc. Is there some trick that I'm missing? Perhaps you should try colour instead :) Seriously, can you post a few lines before and after the color statement? Hi, Actually, it sounds like color support has been turned off. What does the output from "mutt -v" show. Specifically, what curses lib is your mutt built against and does "mutt -v" show +HAVE_COLOR or -HAVE_COLOR? Sure enough -HAVE_COLOR is in the compile options. However, when I went back to the source and did a ./configure --help, I didn't see any option to include color support. How do I recompile with color support? Thanks Mike -- Mike Ericksonmee@quidquam http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: color
Sounds like your curses lib doesn't support color. You might try ncurses * Mike E [EMAIL PROTECTED] [001020 11:56]: On Fri, Oct 20, 2000 at 10:29:17AM -0600, Harold Oga wrote: On 20 Oct 2000, at 22:50, Anthony Liu wrote: On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: I'm trying to set up color with mutt (1.2.5i) but I am getting "color: unknown command" errors from my muttrc. Is there some trick that I'm missing? Perhaps you should try colour instead :) Seriously, can you post a few lines before and after the color statement? Hi, Actually, it sounds like color support has been turned off. What does the output from "mutt -v" show. Specifically, what curses lib is your mutt built against and does "mutt -v" show +HAVE_COLOR or -HAVE_COLOR? Sure enough -HAVE_COLOR is in the compile options. However, when I went back to the source and did a ./configure --help, I didn't see any option to include color support. How do I recompile with color support? Thanks Mike -- Mike Ericksonmee@quidquam http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Re: color
On Fri, Oct 20, 2000 at 12:01:13PM -0500, Larry Rosenman wrote: Sounds like your curses lib doesn't support color. You might try ncurses here is the full output of 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: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] 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/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. Mike -- Mike Ericksonmee@quidquam http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: color
* Mike E [EMAIL PROTECTED] [001020 12:14]: On Fri, Oct 20, 2000 at 12:01:13PM -0500, Larry Rosenman wrote: Sounds like your curses lib doesn't support color. You might try ncurses As I said, the curses lib doesn't support color... Here is my mutt -v: Mutt 1.3.10i (2000-10-11) 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: UnixWare 5 Compile options: DOMAIN="lerctr.org" +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL +USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META -HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV +ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL="/usr/local/bin/ispell" SENDMAIL="/etc/mail/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. here is the full output of 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: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] 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/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. Mike -- Mike Ericksonmee@quidquam http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Re: color
On Fri, Oct 20, 2000 at 10:02:31AM -0700, Mike E wrote: System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] You'd better obtain more recent version of ncurses and recompile. I have version 4.2 while you have only 1.8.6. -- Eugene Paskevich | *==(--- | "Alrighty then!" [EMAIL PROTECTED]| ---)==* |-- Ace Venture Public PGP key: mailto:[EMAIL PROTECTED]?subject=publicpgpkey Fingerprint: 03 BE 52 C8 41 8C 10 DC 2F 81 A2 21 28 5E D3 12 ## A friend in need is a pest indeed. ##
Re: color
On Fri, 20 Oct 2000, Mike E wrote: On Fri, Oct 20, 2000 at 12:01:13PM -0500, Larry Rosenman wrote: Sounds like your curses lib doesn't support color. You might try ncurses here is the full output of mutt -v that version "does", but mutt's configure script does not recognize it. 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: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: editing mails, then save it instead of sending
On Fri, Oct 20, 2000 at 04:25:32PM +0300, Mikko Hänninen wrote: Yes, upgrade to 1.2.5, which has a nice "edit-message" function. Actually, the same functionality is in 1.0.1 too, when you select a message for "edit and resend", you can use the w(rite) command to write it back to the folder. After that you can then quit the message without sending it. But the edit-message function in 1.2.5 is much nicer. Hmm... the 1.0.1 functionality seems more useful to me. Is there any way to edit and resend a message in 1.2.5? -- Daniel J. Peng /"\ Harry Browne, Libertarian \ / ASCII Ribbon Campaign for President! X Against Outlook HTML Mail http://www.harrybrowne.org/ / \ http://www.thebackrow.net/ Thompson, if he is to be believed, has sampled the entire rainbow of legal and illegal drugs in heroic efforts to feel better than he does. As for the truth about his health: I have asked around about it. I am told that he appears to be strong and rosy, and steadily sane. But we will be doing what he wants us to do, I think, if we consider his exterior a sort of Dorian Gray facade. Inwardly, he is being eaten alive by tinhorn politicians. The disease is fatal. There is no known cure. The most we can do for the poor devil, it seems to me, is to name his disease in his honor. From this moment on, let all those who feel that Americans can be as easily led to beauty as to ugliness, to truth as to public relations, to joy as to bitterness, be said to be suffering from Hunter Thompson's disease. I don't have it this morning. It comes and goes. This morning I don't have Hunter Thompson's disease. -- Kurt Vonnegut Jr., on Dr. Hunter S. Thompson: Excerpt from "A Political Disease", Vonnegut's review of "Fear and Loathing: On the Campaign Trail '72"
Re: editing mails, then save it instead of sending
Daniel J Peng [EMAIL PROTECTED] wrote on Fri, 20 Oct 2000: Hmm... the 1.0.1 functionality seems more useful to me. Is there any way to edit and resend a message in 1.2.5? Sure, esc-e (the default key binding for it anyway), the function is called resend-message. The original 1.0 functionality was useful, but it had two features combined into one function: sending an email using an existing email as a base, and editing an existing email. By splitting the features into separate functions (edit-message, resend-message) they both work better. Regards, 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 / By all means, let's not confuse ourselves with the facts!
Re: color
On Fri, Oct 20, 2000 at 08:43:13PM +0300, Eugene Paskevich wrote: On Fri, Oct 20, 2000 at 10:02:31AM -0700, Mike E wrote: System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] You'd better obtain more recent version of ncurses and recompile. I have version 4.2 while you have only 1.8.6. The current version of ncurses is 5.1 (2708) There's an faq at http://dickey.his.com/ncurses/ncurses.faq.html -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Moving 'PGP output follows' to the bottom
Hi, I've been testing Mutt, trying to get it quite close to what I'm used to w/ Pine. One question about PGP; I get the following at the top of the PGP messages: [-- PGP output follows (current time: Fri Oct 20 23:04:51 2000) --] cut gpg messages [-- End of PGP output --] [-- The following data is signed --] the message I'm not really interested about PGP internals the first thing in the message. Is there a way to move that down to the bottom of the message, like some Pine+PGP implementations do? Not on the list, please Cc:. -- Pekka Savola "Tell me of difficulties surmounted, [EMAIL PROTECTED] not those you stumble over and fall"
Is there a Pine-to-Mutt FAQ?
Hi, I've been trying to get used to Mutt. It's not too easy when you have like 5 years of Pine experience behind you. Anyway, I was wondering if there is a Pine-to-Mutt conversion HOWTO or FAQ. I'm _sure_ that would be needed. I sure as hell needed one myself, and had to go through this mailing list archives a lot, ask friends etc. If it doesn't exist, it should cover things like: - How to make Mutt look/feel as much pine as reasonably possible (easy transition) - pointers to a few neat files, one or two joint big ones? - How to make Mutt skip from folder to folder searching for new mails when tab is hit using a macro - How to replace aggerable commands, ie. e.g. 'Mark all messages in this mailbox received between 01-Jul and 01-Aug' [how do you do this anyway?] - And a lot of similar issues that always crop up when a Pine user tries to use Mutt. Not on the list, please Cc:. -- Pekka Savola "Tell me of difficulties surmounted, [EMAIL PROTECTED] not those you stumble over and fall"
Re: Is there a Pine-to-Mutt FAQ?
Pekka Savola [EMAIL PROTECTED] wrote on Fri, 20 Oct 2000: Anyway, I was wondering if there is a Pine-to-Mutt conversion HOWTO or FAQ. I've not heard of one, but I never did use Pine much so I haven't even looked, or paid much attention. I'm _sure_ that would be needed. Right, one would be useful no doubt. Someone only has to write it. :-) - How to make Mutt look/feel as much pine as reasonably possible (easy transition) - pointers to a few neat files, one or two joint big ones? I don't know if there's more to it than the included pine.rc..? - How to replace aggerable commands, ie. e.g. 'Mark all messages in this mailbox received between 01-Jul and 01-Aug' [how do you do this anyway?] Mark, do you mean tag? T~d 1/7-1/8 That is: tag-pattern, and tag messages with a sent-date between 1/7 and 1/8 (dd/mm format). Regards, 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 / It's not an optical illusion, it just looks like one.
