alarm when attaching xml files
I sent hundreds of pdf files for every xml file. Hoever, because of the way I generate the pdf files, I often mistakenly attach the xml source. Is there a way to configure (without source changes) mutt so that it will issue a warning or to even refuse to attach xml files? -- - Eric Smith
Re: alarm when attaching xml files
=- Eric Smith wrote on Mon 18.Aug'08 at 13:10:10 +0200 -= > I sent hundreds of pdf files for every xml file. Hoever, because > of the way I generate the pdf files, I often mistakenly attach the > xml source. > > Is there a way to configure (without source changes) mutt so that > it will issue a warning or to even refuse to attach xml files? => wiki -> ConfigTricks -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
Re: trash folder in 1.5.18
Hi, On 8/17/08, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > > On Saturday, August 16 at 06:25 PM, quoth P Kapat: >> The trash folder patch from >> http://cedricduval.free.fr/mutt/patches/#trash is only upto the >> mutt version 1.5.5.1; there are no patches after that. I am guessing >> that it has been included in the original code. > > It has not been. OK. >> I have used the trash folder option in 1.5.17 (the binary version >> included with Ubuntu Hardy). Any help? > > That old patch will *probably* work. You can at least try it. I tried to patch the already patched (with sidebar) code with the trash.folder patch. It was not entirely clean (output given below). Nevertheless the configure and make process didn't give any error and I am able to use the "set trash=" option now! Is it okay to live with these errors? BTW, I tried to apply this patch before applying the sidebar patch and the errors were similar. Thanks again. PATCH OUTPUT: $ patch -p1 < patch-1.5.5.1.cd.trash_folder.3.4 patching file commands.c Hunk #1 FAILED at 663. 1 out of 1 hunk FAILED -- saving rejects to file commands.c.rej patching file flags.c Hunk #1 FAILED at 65. Hunk #2 succeeded at 96 (offset 6 lines). 1 out of 2 hunks FAILED -- saving rejects to file flags.c.rej patching file globals.h Hunk #1 succeeded at 144 (offset 34 lines). patching file imap/message.c Hunk #1 succeeded at 816 (offset 192 lines). patching file init.h Hunk #1 succeeded at 2966 (offset 407 lines). patching file mutt.h Hunk #1 succeeded at 201 (offset 4 lines). Hunk #2 succeeded at 709 with fuzz 1 (offset 72 lines). Hunk #3 succeeded at 814 with fuzz 1 (offset 48 lines). patching file muttlib.c Hunk #1 FAILED at 1181. 1 out of 1 hunk FAILED -- saving rejects to file muttlib.c.rej patching file mx.c Hunk #1 succeeded at 818 (offset 3 lines). Hunk #2 succeeded at 997 (offset -4 lines). Hunk #3 succeeded at 1026 (offset 3 lines). Hunk #4 succeeded at 1221 (offset -2 lines). patching file postpone.c Hunk #1 succeeded at 279 (offset 4 lines). patching file PATCHES -- Regards PK -- http://counter.li.org #402424
attachment checking with smtp sending
Hi, I am trying to use mutt for Gmail and hence these questions. I came across the CheckAttach scripts here: http://wiki.mutt.org/?ConfigTricks/CheckAttach I am looking at the console (non-GUI/TUI) version. But I am also using the smtp_url in my muttrc to set gmail's smtp srever. So, is it possible to modify/use this CheckAttach script in my setup? -- Regards PK -- http://counter.li.org #402424
Re: trash folder in 1.5.18
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, August 18 at 06:33 PM, quoth P Kapat: > I tried to patch the already patched (with sidebar) code with the > trash.folder patch. It was not entirely clean (output given below). Uy. Unfortunately, those FAILED lines probably mean that you need to reconcile the patch with those files by hand in order to make it work *correctly*. > Nevertheless the configure and make process didn't give any error > and I am able to use the "set trash=" option now! Is it okay to live > with these errors? BTW, I tried to apply this patch before applying > the sidebar patch and the errors were similar. If it works for you, cool; unfortunately, I suspect that even though it compiled without errors, it doesn't actually do all the right things. Having code that compiles without errors is akin to saying that your essay has no spelling errors: it's important, but it doesn't guarantee that whats in there makes any sense. If you're not much of a C programmer, you can try applying the two patches in reverse order (i.e. apply the trash patch first, and the sidebar patch second), or you can try asking the author of the trash patch to fix it for you. ~Kyle - -- The purpose of computing is insight, not numbers. -- Richard W. Hamming -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkip/tkACgkQBkIOoMqOI14KwQCePA+v71xixeZkwQG9/+NfqjeB efgAoLVeHDEly+TC9tc4qjGiDiGsElCQ =CxBv -END PGP SIGNATURE-
config file
Hi, I am tyring to integrate PGP with Mutt. Can anyone of you supply me a basic muttrc which has PGP configurations ? I did setup PGP properly butsomehow its not working when sending mails. Thanks, Ravi
Re: config file
On (18/08/08 16:41), Ravi Uday wrote: | | Hi, | | I am tyring to integrate PGP with Mutt. Can anyone of you supply me a | basic muttrc | which has PGP configurations ? | I did setup PGP properly butsomehow its not working when sending mails. | | Thanks, | Ravi | I "borrowed" this portion of my .muttrc, but can not remember who deserves the credit. (I do remember it was a highly respected source.) Even so, all the usual warnings apply. ## GPG set pgp_decode_command="gpg %?p?--passphrase-fd 0? --no-verbose --batch --output - %f" set pgp_verify_command="gpg --no-verbose --batch --output - --verify %s %f" set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch --output - %f" set pgp_sign_command="gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f" set pgp_clearsign_command="gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" set pgp_encrypt_only_command="pgpewrap gpg --batch --quiet --no-verbose --output - --encrypt --textmode --armor --always-trust --encrypt-to -- -r %r -- %f" set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 --batch --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? --armor --always-trust --encrypt-to -- -r %r -- %f" set pgp_import_command="gpg --no-verbose --import -v %f" set pgp_export_command="gpg --no-verbose --export --armor %r" set pgp_verify_key_command="gpg --no-verbose --batch --fingerprint --check-sigs %r" set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons --list-keys %r" set pgp_list_secring_command="gpg --no-verbose --batch --with-colons --list-secret-keys %r" set pgp_autosign=yes set pgp_sign_as= set pgp_replyencrypt=yes set pgp_timeout=1800 set pgp_good_sign="^gpg: Good signature from" # GPG/PGP related color directives: mono bodybold"^gpg: Good signature" mono bodyreverse "^gpg: Bad signature from.*" color bodybrightblack cyan "^gpg: Signature made.*" color bodybrightblack green "^gpg: Good signature from.*" color bodybrightblack yellow"^gpg: Can't check signature.*" color bodybrightblack yellow"^gpg: WARNING: .*" color bodybrightwhite red "^gpg: BAD signature from.*" -- [EMAIL PROTECTED] GPG key 1024D/99421A63 2005-01-05 EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 signature.asc Description: Digital signature
Re: config file
Thanks John, Thats pretty much I had.. but then I cant see the --BEGIN PGP MESSAGE-- ... --END PGP MESSAGE -- and -BEGIN PGP SIGNATURE- ... -END PGP SIGNATURE- texts inline in the body of the mail. There is a attachment in the mail and that contains the signature part..! Can we have it inlined in the body of hte mail ? Thanks, - Ravi On Mon, Aug 18, 2008 at 5:57 PM, John <[EMAIL PROTECTED]> wrote: > On (18/08/08 16:41), Ravi Uday wrote: > | > | Hi, > | > | I am tyring to integrate PGP with Mutt. Can anyone of you supply me a > | basic muttrc > | which has PGP configurations ? > | I did setup PGP properly butsomehow its not working when sending mails. > | > | Thanks, > | Ravi > | > > I "borrowed" this portion of my .muttrc, but can not remember who > deserves the credit. (I do remember it was a highly respected source.) > Even so, all the usual warnings apply. > > ## GPG > set pgp_decode_command="gpg %?p?--passphrase-fd 0? --no-verbose --batch > --output - %f" > set pgp_verify_command="gpg --no-verbose --batch --output - --verify %s %f" > set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch --output > - %f" > set pgp_sign_command="gpg --no-verbose --batch --output - --passphrase-fd 0 > --armor --detach-sign --textmode %?a?-u %a? %f" > set pgp_clearsign_command="gpg --no-verbose --batch --output - > --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" > set pgp_encrypt_only_command="pgpewrap gpg --batch --quiet --no-verbose > --output - --encrypt --textmode --armor --always-trust --encrypt-to key here> -- -r %r -- %f" > set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 --batch > --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? > --armor --always-trust --encrypt-to -- -r %r -- %f" > set pgp_import_command="gpg --no-verbose --import -v %f" > set pgp_export_command="gpg --no-verbose --export --armor %r" > set pgp_verify_key_command="gpg --no-verbose --batch --fingerprint > --check-sigs %r" > set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons > --list-keys %r" > set pgp_list_secring_command="gpg --no-verbose --batch --with-colons > --list-secret-keys %r" > set pgp_autosign=yes > set pgp_sign_as= > set pgp_replyencrypt=yes > set pgp_timeout=1800 > set pgp_good_sign="^gpg: Good signature from" > # GPG/PGP related color directives: > mono bodybold"^gpg: Good signature" > mono bodyreverse "^gpg: Bad signature from.*" > color bodybrightblack cyan "^gpg: Signature made.*" > color bodybrightblack green "^gpg: Good signature from.*" > color bodybrightblack yellow"^gpg: Can't check > signature.*" > color bodybrightblack yellow"^gpg: WARNING: .*" > color bodybrightwhite red "^gpg: BAD signature from.*" > > > > -- > [EMAIL PROTECTED] > > GPG key 1024D/99421A63 2005-01-05 > EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 > gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkiqGpEACgkQeBOf6ZlCGmPVcQCghV7EUyUofoj3PrhXSo8B2jch > QR0AoKeOWYepGR2Zs5KelEPrKg0Eh5x5 > =4a35 > -END PGP SIGNATURE- > >
smime_keys init doesn't create directories
I'm using the mutt 1.5.17 package on ubuntu 8.04. I have a thawte email certificate I'm trying to use with mutt. About the first thing in the smime readme is to "smime_keys init", which should create the ~/.smime/ set of directories and subdirectories I have in my .muttrc. Unfortunately, no directories or the .index files are created. I threw some print statements in the smime_keys perl script, and it looks like it's getting all the correct variables. I'm not a perlmonger, so I'm not sure how to change the script for force it to really create the files and directories it needs. Also, since it's not working quite right, if I make the files by hand, I don't know why the script isn't working, so it may break further when I need it. Has anyone else ran into where smime_keys init doesn't init, and fixed it? Thanks for the help. -- Andrew Diederich
Re: trash folder in 1.5.18
Hi, On 8/18/08, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > > Uy. Unfortunately, those FAILED lines probably mean that you need to > reconcile the patch with those files by hand in order to make it work > *correctly*. Ah, that is the tricky part. Though I can read the syntax of the source code and the patch, but not knowing the utility of the statements, it will be impossible to patch them correctly. > If you're not much of a C programmer, you can try applying the two > patches in reverse order (i.e. apply the trash patch first, and the > sidebar patch second), or you can try asking the author of the trash > patch to fix it for you. I'll try to contact the author and see. Thanks the nonetheless! -- Regards PK -- http://counter.li.org #402424
Re: config file
Anybody ??? - Ravi On Mon, Aug 18, 2008 at 6:18 PM, Ravi Uday <[EMAIL PROTECTED]> wrote: > Thanks John, > > Thats pretty much I had.. but then I cant see the > > --BEGIN PGP MESSAGE-- > ... > --END PGP MESSAGE -- > > and > > -BEGIN PGP SIGNATURE- > ... > -END PGP SIGNATURE- > > texts inline in the body of the mail. > > There is a attachment in the mail and that contains the signature > part..! Can we have it inlined in the body of hte mail ? > > Thanks, > - Ravi > > On Mon, Aug 18, 2008 at 5:57 PM, John <[EMAIL PROTECTED]> wrote: >> On (18/08/08 16:41), Ravi Uday wrote: >> | >> | Hi, >> | >> | I am tyring to integrate PGP with Mutt. Can anyone of you supply me a >> | basic muttrc >> | which has PGP configurations ? >> | I did setup PGP properly butsomehow its not working when sending mails. >> | >> | Thanks, >> | Ravi >> | >> >> I "borrowed" this portion of my .muttrc, but can not remember who >> deserves the credit. (I do remember it was a highly respected source.) >> Even so, all the usual warnings apply. >> >> ## GPG >> set pgp_decode_command="gpg %?p?--passphrase-fd 0? --no-verbose --batch >> --output - %f" >> set pgp_verify_command="gpg --no-verbose --batch --output - --verify %s %f" >> set pgp_decrypt_command="gpg --passphrase-fd 0 --no-verbose --batch --output >> - %f" >> set pgp_sign_command="gpg --no-verbose --batch --output - --passphrase-fd 0 >> --armor --detach-sign --textmode %?a?-u %a? %f" >> set pgp_clearsign_command="gpg --no-verbose --batch --output - >> --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f" >> set pgp_encrypt_only_command="pgpewrap gpg --batch --quiet --no-verbose >> --output - --encrypt --textmode --armor --always-trust --encrypt-to > GPG key here> -- -r %r -- %f" >> set pgp_encrypt_sign_command="pgpewrap gpg --passphrase-fd 0 --batch >> --quiet --no-verbose --textmode --output - --encrypt --sign %?a?-u %a? >> --armor --always-trust --encrypt-to -- -r %r -- %f" >> set pgp_import_command="gpg --no-verbose --import -v %f" >> set pgp_export_command="gpg --no-verbose --export --armor %r" >> set pgp_verify_key_command="gpg --no-verbose --batch --fingerprint >> --check-sigs %r" >> set pgp_list_pubring_command="gpg --no-verbose --batch --with-colons >> --list-keys %r" >> set pgp_list_secring_command="gpg --no-verbose --batch --with-colons >> --list-secret-keys %r" >> set pgp_autosign=yes >> set pgp_sign_as= >> set pgp_replyencrypt=yes >> set pgp_timeout=1800 >> set pgp_good_sign="^gpg: Good signature from" >> # GPG/PGP related color directives: >> mono bodybold"^gpg: Good signature" >> mono bodyreverse "^gpg: Bad signature from.*" >> color bodybrightblack cyan "^gpg: Signature made.*" >> color bodybrightblack green "^gpg: Good signature >> from.*" >> color bodybrightblack yellow"^gpg: Can't check >> signature.*" >> color bodybrightblack yellow"^gpg: WARNING: .*" >> color bodybrightwhite red "^gpg: BAD signature from.*" >> >> >> >> -- >> [EMAIL PROTECTED] >> >> GPG key 1024D/99421A63 2005-01-05 >> EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 >> gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 >> >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.9 (GNU/Linux) >> >> iEYEARECAAYFAkiqGpEACgkQeBOf6ZlCGmPVcQCghV7EUyUofoj3PrhXSo8B2jch >> QR0AoKeOWYepGR2Zs5KelEPrKg0Eh5x5 >> =4a35 >> -END PGP SIGNATURE- >> >> >
Re: trash folder in 1.5.18
> >> http://cedricduval.free.fr/mutt/patches/#trash is only upto the > >> mutt version 1.5.5.1; there are no patches after that. I am guessing > >> that it has been included in the original code. > > > > It has not been. Cedric hasn't updated it AFAIK, but a google on "cedric duval trash patch" turns up http://scie.nti.st/2007/6/21/mutt-trash-folder-patch-for-1-5-16 . Maybe that version will apply more cleanly to 1.5.18. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
