PGP oldstyle signatures [2]
... and i forgot to attach the parts of my muttrc where things get loaded for GPG and PGP. -Rejo. -- = Rejo Zenger [EMAIL PROTECTED] = http://mediaport.org/~sister (and my_urls.html) PGP: see headers # decode application/pgp set pgp_decode_command="gpg %?p?--passphrase-fd 0? --no-verbose --batch -o - %f" # verify a pgp/mime signature set pgp_verify_command="gpg --no-verbose --batch -o - --verify %s %f" # decrypt a pgp/mime attachment set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch -o - %f" # create a pgp/mime signed attachment # set pgp_sign_command="gpg-2comp --no-verbose --batch -o - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f" set pgp_sign_command="gpg --no-verbose --batch -o - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f" # create a application/pgp signed (old-style) message # set pgp_clearsign_command="gpg-2comp --no-verbose --batch -o - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" set pgp_clearsign_command="gpg --no-verbose --batch -o - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" # create a pgp/mime encrypted attachment # set pgp_encrypt_only_command="pgpewrap gpg-2comp -v --batch -o - --encrypt --textmode --armor --always-trust -- -r %r -- %f" set pgp_encrypt_only_command="pgpewrap gpg -v --batch -o - --encrypt --textmode --armor --always-trust -- -r %r -- %f" # create a pgp/mime encrypted and signed attachment # set pgp_encrypt_sign_command="pgpewrap gpg-2comp --passphrase-fd 0 -v --batch -o - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f" set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 -v --batch -o - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f" # import a key into the public key ring set pgp_import_command="gpg --no-verbose --import -v %f" # export a key from the public key ring set pgp_export_command="gpg --no-verbose --export --armor %r" # verify a key set pgp_verify_key_command="gpg --no-verbose --batch --fingerprint --check-sigs %r" # read in the public key ring set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons --list-keys %r" # read in the secret key ring set pgp_list_secring_command="gpg --no-verbose --batch --with-colons --list-secret-keys %r" # receive key from keyserver: #set pgp_getkeys_command="wrap.sh -g %r" set pgp_getkeys_command="" # Do not sign and/ or encrypt messages by default. unset pgp_autoencrypt unset pgp_autosign # Use this key by default. set pgp_sign_as=0x75FC50F3 # Set the algorithm to use. set pgp_sign_micalg=pgp-sha1 # Forget passphrase after n seconds. set pgp_timeout=1800 # Always verify signatures. set pgp_verify_sig=yes # Do not create old style signatures, if needed it'll be overruled by hand or by send-hook. set pgp_create_traditional=no # Make sure that if i reply to a message that is signed or encrypted i both # sign and encrypt that message. set pgp_replyencrypt set pgp_replysign set pgp_replysignencrypted # decode application/pgp set pgp_decode_command="%?p?PGPPASSFD=0; export PGPPASSFD;? cat %?p?-? %f | pgp +verbose=0 +batchmode -f" # verify a pgp/mime signature set pgp_verify_command="pgp +verbose=0 +batchmode -t %s %f" # decrypt a pgp/mime attachment set pgp_decrypt_command="PGPPASSFD=0; export PGPPASSFD; cat - %f | pgp +verbose=0 +batchmode -f" # create a pgp/mime signed attachment set pgp_sign_command="PGPPASSFD=0; export PGPPASSFD; cat - %f | pgp +verbose=0 +batchmode -abfst %?a? -u %a?" # create a pgp/mime encrypted attachment set pgp_encrypt_only_command="pgp +verbose=0 +encrypttoself +batchmode -aeft %r %f" # create a pgp/mime encrypted and signed attachment set pgp_encrypt_sign_command="PGPPASSFD=0; export PGPPASSFD; cat - %f | pgp +encrypttoself +verbose=0 +batchmode -aefts %?a?-u %a? %r" # import a key into the public key ring set pgp_import_command="pgp -ka %f" # export a key from the public key ring set pgp_export_command="pgp -kxaf %r" # verify a key set pgp_verify_key_command="pgp -kcc %r" # read in the public key ring set pgp_list_pubring_command="pgpring -2 %r" # read in the secret key ring set pgp_list_secring_command="pgpring -s -2 %r" # Do not sign and/ or encrypt messages by default. unset pgp_autoencrypt unset pgp_autosign # Use this key by default. set pgp_sign_as=0xFAE40065 # Set the algorithm to use. set pgp_sign_micalg=pgp-md5 # Forget passphrase after n seconds. set pgp_timeout=1800 # Always verify signatures. set pgp_verify_sig=yes # Do create old style signatures. set pgp_create_traditional=yes # Make sure that if i reply to a message that is signed or encrypted i both # sign and encrypt that message. set pgp_replyencrypt set pgp_replysign set pgp_replysignencrypted PGP signature
Re: unset strict_threads not working?
On May/28/2000, Mikko Hänninen wrote: 1) I *think* (not sure) that if you have had it set, and unset it, you need to make Mutt re-sort the folder. Either re-open it, or change the sort older... Not sure, although it would be easy enough to test. :-) Hmmm ... that was one thing I didn't know :-m I'll try :-) 2) Often the messages don't have an *identical* subject, but instead have "Re: " or something like that in the beginning. Mutt will still No, in this case they really have the same subject. As I said before, this messages are gated from a Fidonet echo. Usually, readers for this echos remove the leading "Re:" in subjects, so this shouldn't be a problem. But I'm glad to see that I had looked at the right points before mailing my problem, because I already knew the $reply_regexp thing :-) 3) As it was recently discussed, Mutt pays attention to the timestamps in messages (the Date header), and will know thread a message that is Yes, I'll have a look at this right now, because this could have some relevance in my problem :-m I'll tell what I find out :-) I hope that helps. If it doesn't, please post us more details... (variable states, message Subject/References sample headers, etc.) I'll do :-) Anyway, another non related (and I hope easier :-)) question: in the kind of mails that I was talking about, the quoted lines usually appear like this: AGG This is a quoted line. I mean, a few letters (the initials of the poster) and the usual "" sign. I find something similar in posts with Gnus. Anyone has a $quote_regexp for this? I could do it myself, but ... well, you know, Open Source is about using the work of others ;-) -- Roberto Suarez Soto ·Sure there's no way to turn it [EMAIL PROTECTED]· Back to the old days Corgo/Lugo/Galicia/Spain ·Of bliss and cheerful laughter
mutt and ssl
Hello, I tried to compile Mutt 1.3.1i with --with-ssl and --enable-imap. But the following happend: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl -I/usr/include/ncurses -I/usr/local/ssl/include -I../intl -Wall -pedantic -g -O2 -c util.c gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl -I/usr/include/ncurses -I/usr/local/ssl/include -I../intl -Wall -pedantic -g -O2 -c imap_ssl.c In file included from ../mutt_menu.h:23, from imap_ssl.c:35: ../keymap.h:112: keymap_defs.h: No such file or directory make[2]: *** [imap_ssl.o] Error 1 make[2]: Leaving directory `/usr/src/mutt-1.3.1/imap' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/mutt-1.3.1' make: *** [all-recursive-am] Error 2 I am using OpenSSL 0.9.4, but I don't have that file on my Harddisk. Any hints? Regards/Gruesse, Norbert -- Norbert Tretkowski, http://nexus.nobse.de pub 1024D/0F7A8D01 1999-11-24 Norbert Tretkowski [EMAIL PROTECTED] Fingerprint = 4A6B 2543 679D 43B0 2B63 5439 AFF4 670B 0F7A 8D01 PGP signature
Re: mutt and ssl
Hi! On Son, Mai 28, 2000 at 01:26:36 +0200, Norbert Tretkowski wrote ../keymap.h:112: keymap_defs.h: No such file or directory Gnagnagna ;-) That has nothing to do with IMAP and SSL. The file "keymap_defs.h" is missing. You can build it with "make keymap_defs.h" after the configure-run. Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.fs.uni-sb.de/~stse/| | PGP Public Keys: http://fsing.fs.uni-sb.de/~stse/pgp.html | PGP signature
Re: mutt and ssl
On Sun, May 28, 2000 at 04:03:36PM +0200, Stephan Seitz wrote: Hi! On Son, Mai 28, 2000 at 01:26:36 +0200, Norbert Tretkowski wrote ../keymap.h:112: keymap_defs.h: No such file or directory Gnagnagna ;-) Wus? ;) That has nothing to do with IMAP and SSL. That problem does not exist when I compile mutt without SSL. The file "keymap_defs.h" is missing. You can build it with "make keymap_defs.h" after the configure-run. Anyway, now it works. Thanks! Regards/Gruesse, Norbert -- Norbert Tretkowski, http://nexus.nobse.de pub 1024D/0F7A8D01 1999-11-24 Norbert Tretkowski [EMAIL PROTECTED] Fingerprint = 4A6B 2543 679D 43B0 2B63 5439 AFF4 670B 0F7A 8D01
Re: unset strict_threads not working?
On May/28/2000, clemensF wrote: AGG This is a quoted line. set quote_regexp="^([A-Za-z ]+|[]%:|}-][]:|}-]*)" Thanks! :-) -- Roberto Suarez Soto ·If it doesn't work, force it. [EMAIL PROTECTED]· If it breaks, it needed replacing anyway. Corgo/Lugo/Galicia/Spain ·
Re: unset strict_threads not working?
Mikko Hänninen muttered: 1) I *think* (not sure) that if you have had it set, and unset it, you need to make Mutt re-sort the folder. Either re-open it, or change the sort older... Not sure, although it would be easy enough to test. :-) Just tested it. If you set strict_threads mutt performs the new threading on the instance. Being paranoid doesn't mean that they *aren't* out to get you. Wisely spoken ;-) HTH, Michael -- The steady state of disks is full. -- Ken Thompson PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: resend-message and FCC
On Fri, May 26, 2000 at 09:32:20PM +0300, Mikko Hänninen wrote: But yes, there should be an option as to whether resend-message will default to Fcc'ing or not -- or if there's no option, the default should be yes. ACK. This bite me several days ago :-((( Best regards, Daniel PGP signature
Re: mutt and ssl
Norbert -- ...and then Norbert Tretkowski said... % On Sun, May 28, 2000 at 04:03:36PM +0200, Stephan Seitz wrote: % % On Son, Mai 28, 2000 at 01:26:36 +0200, Norbert Tretkowski wrote % ../keymap.h:112: keymap_defs.h: No such file or directory % % Gnagnagna ;-) % % Wus? ;) I have a feeling that other folks might spell that "nyah nyah nyah". Imagine thumbs in his ears, too, as his hands wave around. % % That has nothing to do with IMAP and SSL. % % That problem does not exist when I compile mutt without SSL. Could it be because you did a make clean preparing for SSL, or because you didn't do one preparing your original mutt build? I forgot to look at your version, but this bug came up a while back. % % The file "keymap_defs.h" is missing. You can build it with "make % keymap_defs.h" after the configure-run. % % Anyway, now it works. Thanks! Glad to hear that :-) :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: handling text/plain based on extension of the file
Carlos, et al -- ...and then Carlos Puchol said... % hi, Hi! % % i was wondering how to do the following (if possible). In short, as you've probably seen, not in mutt. I don't think that it's a bad idea to have the capability of saying something like autoview text/plain filespec=*.mgd mgp %s but it obviously can't be done yet. % % i reveive ".mgp" files as text/plain attachments, because % most people don't know about magicpoint (a little known % but awesome presentation software), thus they don't have a % mailcap entry of "application/magicpoint; mgp %s" and % a mime entry of "application/magicpoint mgp". As has been discussed, this is a problem in the remote MUA. So what do we do when we get garbled mail from poor users running without the benefit of mutt? We use procmail, of course. While the following is untested, I should think that a rule like :0 fB * Content-Type: text/plain * Content-Disposition: attachment; filename=".*mgd" | $FORMAIL -A"Content-Type: application/magicpoint" would do the trick quite nicely, even if you do have to play with the Content-Disposition string match (maybe just Content.*filename or some such); upon detection of a message that has the matching Content-Type: and Content-Disposition: in the (B)ody, procmail (f)ilters the message through formail (typically defined, with full path and any args, and stored in $FORMAIL) to rewrite (without saving the old) the Content-Type: header. The only problem I see with this brilliant answer :-) is what to do if you are accesssing your mail via an IMAP connection and you do not have the ability to run procmail for your account. Stay tuned for the "how do I have mutt filter my mail?" FAQ entry, which I'm working on diligently (er, well, thinking about contemplating, anyway), which should address some IMAP-user filtering. % % is it possible for me to instruct mutt to invoke mgp % for those attachments that come as text/plan but the % extension of the attachment is .mgp? Once the Content-Type: header is correct, the rest should be easy -- and is left as an exercise for the reader ;-) % % i have dabbled around the manual a bit, but i am not % too experienced with muttrc settings. % % thanks, % % ++ carlos P.S. -- Even though you might see [EMAIL PROTECTED], please be sure to send to [EMAIL PROTECTED] since it's the proper address. :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Exclusive matching
Hi, folks -- ...and then David Champion said... % % Well, it does, but it parses from "top down" -- it takes the whole % string first, and then splits it up to expressions. | can be "or", % so it splits it at that. It doesn't look at the context. % % You can avoid it by quoting it, like you did, or by giving the pattern % in quotes: "^~L (alice|bob|carol)" (or something like that). % % Ah, I see. It's ^~L "(alice|bob|carol)". Precedence would be a good % topic for the manual to go over quickly. Whoops. Pardon me for jumping in here, but shouldn't any parser be able to detect a ( and put everything up until the matching ) in a separate precedence? I still don't see why the parser would break the expression into three ORs with an ( in one and a ) in another unless the code is just plain broken -- but I can't read C enough to have any idea :-) Note that that's not a flame of the code or developers, especially since I'm in no position to provide a patch to "fix" the behavior... :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
