Re: Decrypting GPG-encoded messages
On Thu, Feb 14, 2002 at 05:13:06PM +, [EMAIL PROTECTED] wrote: Since it's a bit complex and I don't really know what I'm talking about, I'm giving you a link which does. Sorry, previous mail should have gone to list, not to you directly. I've already looked at the link you gave, and it seems to be hopelessly out of date - it refers to Mutt 0.95.3i - and all (most) of the configuration variables it suggests setting no longer exist. I may be a GnuPG newbie, but I'm not a total newbie, and I know how to find/read documentation (at least some of the time, anyway). I've read the instructions given by Justin R Miller (linked from www.mutt.org), and the ones in the contrib directory of the mutt source (they are very similar), and set my mutt up accordingly. However, whenever I try to send a mail encrypted, all I get is a load of blank lines. I don't think it's my particular compilation of mutt, since I get the same behaviour on my self-compiled 1.3.27i (running on Solaris 2.8) and on the precompiled mutt binary that came with SuSE 7.2. I'm beginning to suspect that the instructions may be wrong/out-of-date. Is anyone willing/able to send me a .muttrc which works with GnuPG and a recent version of mutt? In case anyone is willing to have a look, my (condensed) .muttrc is as follows: source /u/dsmith/lib/mutt/gpg.rc ignore from received content- mime-version status x-status message-id ignore sender references return-path lines macro index \eb '/~b ' 'search in message bodies' macro index \cb |urlview\n 'call urlview to extract URLs out of a message' macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' macro generic f1 !less /usr/local/doc/mutt/manual.txt\n Show Mutt documentation macro index f1 !less /usr/local/doc/mutt/manual.txt\n Show Mutt documentation macro pager f1 !less /usr/local/doc/mutt/manual.txt\n Show Mutt documentation set hostname=bristol.st.com set folder=/u/dsmith/Mail set spoolfile=imap://dave smith@bloodroot/inbox set print_command=/pd/genscript/1.3.0/bin/genscript -p - --font=Courier8 | lp set query_command=/u/dsmith/bin/address_lookup '%s' send-hook . set signature=~/.signature send-hook [EMAIL PROTECTED] set signature=~/.signature_bblug set sort=threads set sort_aux=date-received set strict_threads subscribe [EMAIL PROTECTED] subscribe [EMAIL PROTECTED] subscribe [EMAIL PROTECTED] subscribe [EMAIL PROTECTED] And my gpg.rc is as follows: set pgp_decode_command=gpg --no-secmem-warning %?p?--passphrase-fd 0? --no-verbose --batch --output - %f set pgp_verify_command=gpg --no-secmem-warning --no-verbose --batch --output - --verify %s %f set pgp_decrypt_command=gpg --no-secmem-warning --passphrase-fd 0 --no-verbose --batch --output - %f set pgp_sign_command=gpg --no-secmem-warning --no-verbose --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f set pgp_clearsign_command=gpg --no-secmem-warning --no-verbose --batch --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f set pgp_encrypt_only_command=pgpewrap gpg --no-secmem-warning -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f set pgp_encrypt_sign_command=pgpewrap gpg --no-secmem-warning --passphrase-fd 0 -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f set pgp_import_command=gpg --no-secmem-warning --no-verbose --import -v %f set pgp_export_command=gpg --no-secmem-warning --no-verbose --export --armor %r set pgp_verify_key_command=gpg --no-secmem-warning --no-verbose --batch --fingerprint --check-sigs %r set pgp_list_pubring_command=gpg --no-secmem-warning --no-verbose --batch --with-colons --list-keys %r set pgp_list_secring_command=gpg --no-secmem-warning --no-verbose --batch --with-colons --list-secret-keys %r set pgp_getkeys_command= TIA... -- David Smith Tel: +44 (0)1454 462380 (direct) STMicroelectronicsFax: +44 (0)1454 617910 1000 Aztec WestTINA (ST only): (065) 2380 Almondsbury Home: 01454 616963 BRISTOLMobile: 07932 642724 BS32 4SQ Work Email: [EMAIL PROTECTED] Home Email: [EMAIL PROTECTED]
Re: Decrypting GPG-encoded messages
Nick Wilson's last message had 1.3.27i and was GnuPG signed. Nick? Simon. On 15-Feb-02 at 09:05, Dave Smith's transmission stated : Is anyone willing/able to send me a .muttrc which works with GnuPG and a recent version of mutt? -- |-Simon White |-Internet Services Manager |-MTDS S.A. |-tel +212.3.767.4861 |-fax +212.3.767.4863 |-14, rue 16 novembre |-Rabat, Kingdom of Morocco
mutt not saving sent mail
Hi !! I am using 1.3.27 with a .muttrc that I got from Roland Rosenfeld's page with, by now, quite a few modifications. I had previously got the sample muttrc file for 1.2.x and now I am using the sample file for 1.3.x. I used my 1.3.27 for a few days w/ the old muttrc (for 1.2.5) till I was satisfied w/ the changes I made in the new muttrc. The problem I am experiencing is that previously when I sent a message, mutt would ask me if I wanted to save a copy of the message, but I seem to have lost this function w/ my new mutt muttrc. set copy=ask-no is present in both (the old and new) rc files. What am I missing ? I need to keep a copy of the message mainly because I have to use a mighty flaky smtp server that supports pop before smtp and the *technical* contacts seem to think that I am getting a relaying denied mesage because I am not using Outhouse Express !! thanx, Sharukh. -- Dr. Sharukh K. R. Pavri Mumbai, India.
Re: mutt not saving sent mail
Hi! On 2002-02-14 Dr. Sharukh K. R. Pavri. wrote: I am using 1.3.27 with a .muttrc that I got from Roland Rosenfeld's page with, by now, quite a few modifications. I had previously got the sample muttrc file for 1.2.x and now I am using the sample file for 1.3.x. I used my 1.3.27 for a few days w/ the old muttrc (for 1.2.5) till I was satisfied w/ the changes I made in the new muttrc. The problem I am experiencing is that previously when I sent a message, mutt would ask me if I wanted to save a copy of the message, but I seem to have lost this function w/ my new mutt muttrc. set copy=ask-no is present in both (the old and new) rc files. What am I missing ? I need to keep a copy of the What about the values of $record, $force-name, $save-name and possibly defined fcc-hooks. Are there any differences between the two muttrcs. Regards, Christoph -- Christoph Maurer - D - 52072 Aachen mailto:[EMAIL PROTECTED] - http://www.christophmaurer.de On my Homepage: SuSE 7.0 on an Acer Travelmate 508 T Notebook
libncurses/mutt problem on Solaris
Short version: mutt wants a dynamic ncurses lib, but all I could find was a static one. I cannot run mutt on Solaris 8. It configures, makes and installs fine, but when I try to run it, I get: --- ld.so.1: mutt: fatal: libncurses.so.5: open failed: No such file or directory. Killed --- The above error message is to be expected, since the dynamic library in question isn't present anywhere in my server. After that, I found an advise on mutt's web page in which they say that mutt needs the ncurses library available from GNU. I installed the GNU 5.2 library -which creates only a file called ncurses.a (static) and reinstalled mutt from scratch, even trying this command: ./configure --with-curses=/usr/local/lib/ Unfortunately, the mutt installation doesn't understand that all I have is an static library and the error message still prevents mutt from running: --- ld.so.1: mutt: fatal: libncurses.so.5: open failed: No such file or directory. Killed --- Thanks for your kind assistance, -Ramon F. Herrera
Re: Mutt flea
On Fri, Feb 15, 2002 at 03:10:35PM +, Simon White wrote: You probably all use save-hooks and all that, but on my setup: I hit s, then backspace to get rid of the default, and as I hit backspace the string gets 'corrupted', i.e. what I see on screen is a mix of what I typed and what I had before. If I hit backspace loads of times to be sure the buffer is clear I still have a few letters left behind but the path I put in works. Is this a curses issue, or is it Mutt? probably curses is doing what mutt told it to do... -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Decrypting GPG-encoded messages
On Feb 15, Dave Smith [[EMAIL PROTECTED]] wrote: Is anyone willing/able to send me a .muttrc which works with GnuPG and a recent version of mutt? # Name: forward_decrypt # Type: boolean # Default: yes # Controls the handling of encrypted messages when forwarding a message. When # set, the outer layer of encryption is stripped off. This variable is only # used if ``$mime_forward'' is set and ``$mime_forward_decode'' is unset. set forward_decrypt=yes # Name: pgp_autosign # Type: boolean # Default: no # Setting this variable will cause Mutt to always attempt to PGP/MIME sign # outgoing messages. This can be overridden by use of the pgp-menu, when # signing is not required or encryption is requested as well. set pgp_autosign=yes # Name: pgp_autoencrypt # Type: boolean # Default: no # Setting this variable will cause Mutt to always attempt to PGP/MIME encrypt # outgoing messages. This is probably only useful in connection to the # send-hook command. It can be overridden by use of the pgp-menu, when # encryption is not required or signing is requested as well. send-hook . set pgp_autoencrypt=no send-hook mark(|-.*)@(firinn|cymry).org set pgp_autoencrypt=yes #... # Name: pgp_ignore_subkeys # Type: boolean # Default: yes # Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, the # principal key will inherit the subkeys' capabilities. Unset this if you want # to play interesting key selection games. set pgp_ignore_subkeys=yes # Name: pgp_entry_format # Type: string # Default: %4n %t%f %4l/0x%k %-4a %2c %u # This variable allows you to customize the PGP key selection menu to your # personal taste. This string is similar to ``$index_format'', but has its own # set of printf()-like sequences: # %n number # %k key id # %u user id # %a algorithm # %l key length # %f flags # %c capabilities # %t trust/validity of the key-uid association # %[s] date of the key where s is an strftime(3) expression set pgp_entry_format=%4n %t%f %4l/0x%k %-4a %2c %u # Name: pgp_good_sign # Type: regular expression # Default: # If you assign a text to this variable, then a PGP signature is only # considered verified if the output from $pgp_verify_command contains the text. # Use this variable if the exit code from the command is 0 even for bad # signatures. set pgp_good_sign=^gpg: Good signature from # Name: pgp_long_ids # Type: boolean # Default: no # If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs. set pgp_long_ids=no # Name: pgp_replyencrypt # Type: boolean # Default: yes # If set, automatically PGP encrypt replies to messages which are encrypted. set pgp_replyencrypt=yes # Name: pgp_replysign # Type: boolean # Default: no # If set, automatically PGP sign replies to messages which are signed. # Note: this does not work on messages that are encrypted and signed! set pgp_replysign=yes # Name: pgp_replysignencrypted # Type: boolean # Default: no # If set, automatically PGP sign replies to messages which are encrypted. This # makes sense in combination with ``$pgp_replyencrypt'', because it allows you # to sign all messages which are automatically encrypted. This works around # the problem noted in ``$pgp_replysign'', that mutt is not able to find out # whether an encrypted message is also signed. set pgp_replysignencrypted=yes # Name: pgp_retainable_sigs # Type: boolean # Default: no # If set, signed and encrypted messages will consist of nested multipart/signed # and multipart/encrypted body parts. # This is useful for applications like encrypted and signed mailing lists, # where the outer layer (multipart/encrypted) can be easily removed, while the # inner multipart/signed part is retained. set pgp_retainable_sigs=no # Name: pgp_show_unusable # Type: boolean # Default: yes # If set, mutt will display non-usable keys on the PGP key selection menu. # This includes keys which have been revoked, have expired, or have been marked # as ``disabled'' by the user. set pgp_show_unusable=no # Name: pgp_sign_as # Type: string # Default: # If you have more than one key pair, this option allows you to specify which # of your private keys to use. It is recommended that you use the keyid form # to specify your key (e.g., ``0x00112233''). set pgp_sign_as=0xF009764F # Name: pgp_strict_enc # Type: boolean # Default: yes # If set, Mutt will automatically encode PGP/MIME signed messages as # quoted-printable. Please note that unsetting this variable may lead to # problems with non-verifyable PGP signatures, so only change this if you know # what you are doing. set pgp_strict_enc=yes # Name: pgp_timeout # Type: number # Default: 300 # The number of seconds after which a cached passphrase will expire if not # used. set pgp_timeout=0 # Name: pgp_verify_sig # Type: quadoption # Default: yes # If ``yes'', always attempt to verify PGP/MIME signatures. If ``ask-yes'' or # ``ask-no'', ask whether or not to verify the signature. If ``no'', never # attempt
Re: Mutt flea
Perhaps this is where the problem lies. I haven't done anything for ncurses to handle multibyte input (which is what I understand dead-keys to be). If ncurses sees that as 3 characters, it'll think that's how long it displays via a prompt. So the repainting would be farther to the right, etc. (My understanding of dead-keys or compose was that the byte stream is processed in the input-method or the keyboard handler, before the terminal emulator sees that). No, dead keys enable me to hit apostrope ' and then e to get é. It used to be called Compose on some systems and keyboards that had a compose button. ISO-8859-1 is just a specific rule for understanding extended ASCII characters, and not double-byte. Double byte languages are ones that do not use regular latin characters, like sengalese, arabic, hebrew... The text I sent could be copied to a file and compiled with 'tic', so that setting $TERM to 'konsole' would pick up that entry. There's probably an older 'konsole' entry already there, but I reviewed that, and gnome-terminal in the past few months to update them. I'm not sure this will help; I don't want to screw things up. Everything else I have run with curses has behaved OK. Mutt even seems to run beautifully apart from this issue. To expand further, can anyone else reproduce this? Hit s on an email from someone with more than 8 characters before the @ then hit backspace a few times. As you approach the 8th character (or perhaps the 7th if Mutt has added an =) when you hit backspace, the cursor actually jumps forward after the delete. This appears to be the start of the problem. -- |-Simon White |-Internet Services Manager |-MTDS S.A. |-tel +212.3.767.4861 |-fax +212.3.767.4863 |-14, rue 16 novembre |-Rabat, Kingdom of Morocco
How is maildir_trash supposed to work?
I'm a bit confused about how to use maildir_trash. If maildir_trash is off, then when I quit mutt, if I answer no to purging the messages, then it will lose all the Deleted flags. If maildir_trash is on, then that works. However, then it doesn't seem to be possible to purge deleted messages anymore; I press $ and it asks Purge 1 deleted message? ([yes]/no): and I answer yes, but the message still remains in my mailbox. Is it not possible to be able to do BOTH of these: - save Deleted flags in messages - really purge a message pine can do it, out of the box.
Folder-hook question
Hi, I'm wanting to do something like this guy did (apparently): http://www.xs4all.nl/~hanb/dot-mutt/folderhooks And have a rule that makes it so that when I press m while in a certain folder, the message already has the list (say, [EMAIL PROTECTED]) at the To: header for me. Since the method used by Han doesn't seem to work, I ask you now: do you know if what I'm trying to do is possible? Thanks, Carlos. -- Carlos Laviola [EMAIL PROTECTED]
Re: Folder-hook question
* On Fri, Feb 15, 2002 at 06:12:00PM -0200, * Carlos Laviola [EMAIL PROTECTED] wrote: Hi, I'm wanting to do something like this guy did (apparently): http://www.xs4all.nl/~hanb/dot-mutt/folderhooks Sorry I can't look at the website, because I have no webaccess at the moment. And have a rule that makes it so that when I press m while in a certain folder, the message already has the list (say, [EMAIL PROTECTED]) at the To: header for me. Since the method used by Han doesn't seem to work, I ask you now: do you know if what I'm trying to do is possible? folder-hook . bind index m mail folder-hook dsa macro index m \maildsa\ \Mail verschicken\ There is an tab after the dsa to show me an list of aliases beginning with dsa, but I think if you replace the tab with an \n it would be your wanted behaviour. Nicolas
tagging messages based on date
Fellow mutt lovers, I'm wondering if mutt has the ability to tag messages based on a date range. I'm specifically looking to tag all messages received from say 1.1.2002 to 1.31.2002. dan
Re: tagging messages based on date
Dan, I'm wondering if mutt has the ability to tag messages based on a date range. I'm specifically looking to tag all messages received from say 1.1.2002 to 1.31.2002. Say T~r01/01/2002-01/31/2002 man muttrc Chris -- Christopher S. Swingley phone: 907-474-2689 Computer / Network Manager email: [EMAIL PROTECTED] IARC -- Frontier ProgramGPG and PGP keys at my web page: University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle
Re: tagging messages based on date
Hmmm. IAfter reading the muttrc man page I'm not sure why this isn't working. I'm doing T~r02/02/2002-02/05/2002 and even T~r02/02-/02/05 which should both work. mutt 1.3.27i. dan * Christopher S. Swingley ([EMAIL PROTECTED]) wrote: Dan, I'm wondering if mutt has the ability to tag messages based on a date range. I'm specifically looking to tag all messages received from say 1.1.2002 to 1.31.2002. Say T~r01/01/2002-01/31/2002 man muttrc Chris -- Christopher S. Swingley phone: 907-474-2689 Computer / Network Manager email: [EMAIL PROTECTED] IARC -- Frontier ProgramGPG and PGP keys at my web page: University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle
Re: Folder-hook question
On Fri, 15 Feb 2002, Carlos Laviola wrote: Hi, I'm wanting to do something like this guy did (apparently): http://www.xs4all.nl/~hanb/dot-mutt/folderhooks And have a rule that makes it so that when I press m while in a certain folder, the message already has the list (say, [EMAIL PROTECTED]) at the To: header for me. Since the method used by Han doesn't seem to work, I ask you now: do you know if what I'm trying to do is possible? folder-hook mutt my_hdr To: [EMAIL PROTECTED] You do have to hit enter to get it to accept the To: field, but at least you don't have to type it. Don't know how to set it up so that it automagically enters it though. msg24532/pgp0.pgp Description: PGP signature
Re: Decrypting GPG-encoded messages
Jeremy Blosser muttered: On Feb 15, Dave Smith [[EMAIL PROTECTED]] wrote: Is anyone willing/able to send me a .muttrc which works with GnuPG and a recent version of mutt? [huge pgp.rc snipped] Did this have to be on the list? :-| Michael -- PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Decrypting GPG-encoded messages
Michael Tatge wrote: Jeremy Blosser muttered: Is anyone willing/able to send me a .muttrc which works with GnuPG and a recent version of mutt? [huge pgp.rc snipped] Did this have to be on the list? :-| for that matter, is anything wrong with contrib/gpg.rc? works fine for me. -- William Yardley GnuPG public key: http://infinitejazz.net/will/pgp/gpg.asc
Re: tagging messages based on date
dan radom muttered: * Christopher S. Swingley ([EMAIL PROTECTED]) wrote: Dan, I'm wondering if mutt has the ability to tag messages based on a date range. I'm specifically looking to tag all messages received from say 1.1.2002 to 1.31.2002. Hmmm. IAfter reading the muttrc man page I'm not sure why this isn't working. I'm doing T~r02/02/2002-02/05/2002 and even T~r02/02-/02/05 which should both work. mutt 1.3.27i. Which works here. try what again with mutt -F /dev/null to be sure it's not your setup, to be blamed. HTH, Michael -- PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Folder-hook question
On Fri, Feb 15, 2002 at 03:26:32PM -0600, Knute wrote: On Fri, 15 Feb 2002, Carlos Laviola wrote: Hi, I'm wanting to do something like this guy did (apparently): http://www.xs4all.nl/~hanb/dot-mutt/folderhooks And have a rule that makes it so that when I press m while in a certain folder, the message already has the list (say, [EMAIL PROTECTED]) at the To: header for me. Since the method used by Han doesn't seem to work, I ask you now: do you know if what I'm trying to do is possible? folder-hook mutt my_hdr To: [EMAIL PROTECTED] You do have to hit enter to get it to accept the To: field, but at least you don't have to type it. Don't know how to set it up so that it automagically enters it though. This is what I use: folder-hook +Incoming/mutt-users 'macro index M :push mail^[EMAIL PROTECTED]^M^M mail to list' Note that I have 'askcc' set, so one of those ^Ms is an answer to the Cc: prompt. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: Folder-hook question
On 18:12 15 Feb 2002, Carlos Laviola [EMAIL PROTECTED] wrote: | And have a rule that makes it so that when I press m while in a certain | folder, the message already has the list (say, [EMAIL PROTECTED]) at | the To: header for me. Since the method used by Han doesn't seem to | work, I ask you now: do you know if what I'm trying to do is possible? I'm curious. I just use g (group reply) and it puts the list address there anyway. If I'm making a fresh thread I either use g and trim the headers (fresh subject, remove References: and In-Reply-To: stuff) or outright just mail to mutt-users, pissibly looking it up with ^T (external query). Of course, this doesn't answer your folder-hook query, but I'm wondering why you have to use folder-hook? -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ For reading rec.moto, I use one of those carbon-fiber Logitech mice w/a little 'No Fear' sticker on it. - Mike Hardcore DoD#5010 [EMAIL PROTECTED] Apologies to Primus
Re: mutt not saving sent mail
Hi Christoph! On Fri, 15 Feb 2002, Christoph Maurer wrote: Hi! On 2002-02-14 Dr. Sharukh K. R. Pavri. wrote: I am using 1.3.27 with a .muttrc that I got from Roland Rosenfeld's page with, by now, quite a few modifications. I had previously got the sample muttrc file for 1.2.x and now I am using the sample file for 1.3.x. I used my 1.3.27 for a few days w/ the old muttrc (for 1.2.5) till I was satisfied w/ the changes I made in the new muttrc. The problem I am experiencing is that previously when I sent a message, mutt would ask me if I wanted to save a copy of the message, but I seem to have lost this function w/ my new mutt muttrc. set copy=ask-no is present in both (the old and new) rc files. What am I missing ? I need to keep a copy of the What about the values of $record, $force-name, $save-name and possibly defined fcc-hooks. Are there any differences between the two muttrcs. yes, set record= in the new muttrc. Changed it now. thanks, Sharukh. -- Dr. Sharukh K. R. Pavri Mumbai, India.
