Error opening mailbox
Hi, I use IMAP and my INBOX has just 38 msgs. Still I am unable to open the mails after fetching the errors. Could anyone tell me how to fix this. If I press TAB and then open anyother folder say 'Sent' I can view all of them. Only INBOX fails. I have : set spoolfile=imap://email.xxx.com/INBOX set folder=imap://email.xxx.com/ set imap_user = 'ruday' set imap_pass = '' OSX: bash-3.2$ mutt-1.5.21/mutt -v Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 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: Darwin 10.8.0 (i386) ncurses: ncurses 5.7.20081102 (compiled with 5.7) libiconv: 1.11 Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME +EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE -ISPELL SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/Applications/mutt-install/share/mutt" SYSCONFDIR="/Applications/mutt-install/etc" EXECSHELL="bash" -MIXMASTER To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. bash-3.2$
Re: Error opening mailbox
Paul, I am not sure what you meant. Could be little clear. Let me know if my mail isn't clear - Ravi On Thu, Nov 24, 2011 at 5:53 PM, Paul wrote: > Everything is here but the error(s). > > On Thursday, 24 November, 2011 at 07:12:23 GMT, Ravi Uday wrote: >> >> Hi, >> >> I use IMAP and my INBOX has just 38 msgs. >> Still I am unable to open the mails after fetching the errors. >> Could anyone tell me how to fix this. >> >> If I press TAB and then open anyother folder say 'Sent' I can view all of >> them. >> Only INBOX fails. >> I have : >> >> set spoolfile=imap://email.xxx.com/INBOX >> set folder=imap://email.xxx.com/ >> set imap_user = 'ruday' >> set imap_pass = '' >> >> OSX: >> >> bash-3.2$ mutt-1.5.21/mutt -v >> Mutt 1.5.21 (2010-09-15) >> Copyright (C) 1996-2009 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: Darwin 10.8.0 (i386) >> ncurses: ncurses 5.7.20081102 (compiled with 5.7) >> libiconv: 1.11 >> Compile options: >> -DOMAIN >> -DEBUG >> -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL >> -USE_FLOCK >> +USE_POP +USE_IMAP -USE_SMTP >> +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO >> +HAVE_REGCOMP -USE_GNU_REGEX >> +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET >> +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM >> +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME >> -CRYPT_BACKEND_GPGME >> +EXACT_ADDRESS -SUN_ATTACHMENT >> +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET >> +HAVE_LANGINFO_YESEXPR >> +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE >> -ISPELL >> SENDMAIL="/usr/sbin/sendmail" >> MAILPATH="/var/mail" >> PKGDATADIR="/Applications/mutt-install/share/mutt" >> SYSCONFDIR="/Applications/mutt-install/etc" >> EXECSHELL="bash" >> -MIXMASTER >> To contact the developers, please mail to . >> To report a bug, please visit http://bugs.mutt.org/. >> >> bash-3.2$ > > -- > > . >
Pager view - status not seen
Hi, I used to see on new msgs, the letters 'F', 'T', '+' symbols before subject after I login to mutt. But its not to be seen now. Is there any line that I am missing now in my .muttrc ? - Ravi
font setting
Hi, When I compose my view my editior is set as vim. How can I automatically set the color and font type in my outgoing mails when I use mutt to send emails. Like i need all my msgs in blue, italisize and font=ariel. Thanks, - Ravi
Re: font setting
Yes thats what the default intention was :( Is there any plans for mutt to release this kind of font/html support ? Anyother way to do this or any other mail client which I could use - Ravi On Mon, Jan 23, 2012 at 9:08 PM, Michael Graham wrote: > On 22/01/2012 18:35, Ravi Uday wrote: > >> How can I automatically set the color and font type in my outgoing mails >> when I use mutt to send emails. Like i need all my msgs in blue, italisize >> and font=ariel. > > > Do you mean you want to set it so that the *recipient* sees the underlining, > blue test, &c.? If that is what you mean, then it sounds like you want to > send email in HTML format, which I’m pretty certain mutt doesn’t do. > > -- > Mike __ __ __ > / /_ ___ _/ /__ _/ / _ __ > / '_/ _ \/ __/ _ `/ / _ `/ __/ _ \ |/ / Raconteur, Mostly > /_/\_\\___/_/ \_,_/_/\_,_/\__/\___/___/ <http://koralatov.com/>
mutt-users@mutt.org
Hi, I am trying to install mutt on sunos box but I get this error: checking whether iconv.h defines iconv_t... yes checking whether this iconv is good enough... no configure: error: Try using libiconv instead bash-2.05b$ Do You know how to proceed Ravi
Re: mutt-users@mutt.org
Hi Vlad, Here it is: Seems like configure couldn't find the SO. configure:18489: checking whether this iconv is good enough configure:18527: gcc -o conftest -Wall -pedantic -g -O2 conftest.c -liconv >&5 configure:18530: $? = 0 configure:18536: ./conftest ld.so.1: conftest: fatal: libiconv.so.2: open failed: No such file or directory ./configure: line 1: 23577 Killed ./conftest$ac_exeext configure:18539: $? = 137 configure: program exited with status 137 Ravi > > On Thu, Apr 24, 2008 at 11:19 AM, Vladimir Marek <[EMAIL PROTECTED]> wrote: > > > > > > I am trying to install mutt on sunos box but I get this error: > > > > > > checking whether iconv.h defines iconv_t... yes > > > checking whether this iconv is good enough... no > > > configure: error: Try using libiconv instead > > > bash-2.05b$ > > > > config.log should have the details. Try looking for "checking whether > > this iconv is good enough" and some errors around. > > > > -- > >Vlad > > > >
Re: mutt-users@mutt.org
Thanks Vlad, Here are more o/p: bash-2.05b$ uname -a SunOS 11 5.8 Generic_117350-34 sun4u sparc SUNW,Netra-T12 bash-2.05b$ cat /var/sadm/install/contents | grep libiconv.so bash-2.05b$ But we hvae iconv dir under lib intact - bash-2.05b$ cat /var/sadm/install/contents | grep iconv | more /usr/bin/geniconvtbl f none 0555 root bin 123520 27123 947116526 SUNWcsu /usr/bin/iconv f none 0555 root bin 11996 42547 947116534 SUNWcsu /usr/include/iconv.h f none 0644 root bin 566 46749 947110181 SUNWhea /usr/lib/iconv d none 0755 root bin SUNWkiu8x SUNWhiu8x SUNWcsu SUNWuiu8x SUNW uiu8 SUNWciu8x SUNWtiu8x SUNWloc SUNWislcc SUNWislcx SUNWisolc SUNWisolx SUNWj iu8x SUNWlocx /usr/lib/iconv/646%8859.so f none 0755 bin bin 5520 34564 940251623 SUNWislcc /usr/lib/iconv/646%ISO8859-1.so=646%8859.so s none SUNWislcc /usr/lib/iconv/646%ISO8859-2.so=646%8859.so s none SUNWislcc /usr/lib/iconv/646%ISO8859-4.so=646%8859.so s none SUNWislcc /usr/lib/iconv/646%ISO8859-5.so=646%8859.so s none SUNWislcc /usr/lib/iconv/646%ISO8859-7.so=646%8859.so s none SUNWislcc /usr/lib/iconv/646%ISO8859-9.so=646%8859.so s none SUNWislcc /usr/lib/iconv/646%UCS-2.so f none 0555 root bin 7116 54099 1042853349 SUNWuiu 8 /usr/lib/iconv/646%UCS-2BE.so f none 0555 root bin 7136 48707 1042853349 SUNWu iu8 and bash-2.05b$ ls /opt/csw/lib /opt/csw/lib: No such file or directory bash-2.05b$ So sunfreeware.com is the way to go ? Ravi On Thu, Apr 24, 2008 at 12:02 PM, Vladimir Marek <[EMAIL PROTECTED]> wrote: > > > I am trying to install mutt on sunos box but I get this error: > > > > Seems like configure couldn't find the SO. > > > > configure:18489: checking whether this iconv is good enough > > configure:18527: gcc -o conftest -Wall -pedantic -g -O2 conftest.c > > -liconv >&5 > > configure:18530: $? = 0 > > configure:18536: ./conftest > > ld.so.1: conftest: fatal: libiconv.so.2: open failed: No such file or > > directory > > ./configure: line 1: 23577 Killed ./conftest$ac_exeext > > configure:18539: $? = 137 > > configure: program exited with status 137 > > You haven't specified which sunos you are running. Locate the iconv > library by > > $ cat /var/sadm/install/contents | grep libiconv.so > > You will have to set LD_LIBRARY_PATH appropriately. Chances are that > it's in /opt/csw/lib . If you don't have one, you can get one from > companion (sunfreeware.com). > > -- >Vlad >
coloring headers
Hi,
1. In the header of the recvd mail, how to make each mail address
different color and
reflect the same color in the body of the mail if it(the
name/address) appears there. ?
2. When we reply ('g'/'r'), oriiginal mail will prepend each line with
'>', how to make it show
'-->' instead
Sorry if these questions are asked before !
Ravi
coloring body
Hi, I have this in my .muttrc color body blueblack "((To:) .*)|((Cc:) .*)" This does the job for one line. But most of the times To / Cc will be extending to next 2-3 line due to long listings of names. Is there a way to color entire To/Cc field list ? - Ravi
threaded view
Hi guys, I have these set sort=threads set duplicate_threads=yes If someone replies to a threaded message how to make it display at the bottom/latest in the index view ? I mean if the thread is really old and if someone now replies to that, it gets buried somewhere :( Ravi
Re: threaded view
that works ! thanks On Wed, May 14, 2008 at 12:23 PM, Leon Weber <[EMAIL PROTECTED]> wrote: > On 14.05.2008 12:00:53, Ravi Uday wrote: >> Hi guys, >> >> I have these >> >> set sort=threads >> set duplicate_threads=yes >> >> If someone replies to a threaded message how to make it display at the >> bottom/latest in the index view ? >> I mean if the thread is really old and if someone now replies to that, >> it gets buried somewhere :( > > set sort_aux = last-date > > -- > Leon Weber, [EMAIL PROTECTED] 0x8E04D7FC > blog: https://leonweber.de/blog > jabber: [EMAIL PROTECTED] (icq: 261067046) > -- > Anyway, you should learn German. It's no more difficult than regex. (Richard > Quinn) >
Change folders
Hi mutt folks, When I select a different folders using 'c' and '?' it starts to load the folder and msgs from start. Is there a way to bypass/cache this and make mutt load the folder faster ? Thanks, Ravi
short-keys
Hi Mutt users, Does anyone has a comprehensive list of short cut keys while navigating/composing/deleting mails when using mutt 1.5.17 I mean I have so many similar apps(xterm/emac/vi/sendmail etc) opened and I kind of get confused with different keyboard key combo's. Maybe I can take a printout and stick it up the wall :) Responses appreciated in advance Ravi
network-error
Hi users, I face this problem quite often. In vi I compose a lengthy reply and then save it and hit'y' and pop comes this Network-Error unable to send msg. I use mutt 1.5.17. And formatting is so different in vi that I can't later just copy the msg stored under /tmp/mutt* and have it mailed in windows !! Is there a workaround to solve this often network-error i see. Thanks in Advance. Ravi
Re: network-error
Where do you find the logs !? Ravi On Wed, Jun 25, 2008 at 4:52 PM, Sahil Tandon <[EMAIL PROTECTED]> wrote: > Ravi Uday <[EMAIL PROTECTED]> wrote: > >> I face this problem quite often. In vi I compose a lengthy reply and >> then save it and hit'y' and pop >> comes this Network-Error unable to send msg. I use mutt 1.5.17. And >> formatting is so different in vi that I can't >> later just copy the msg stored under /tmp/mutt* and have it mailed in >> windows !! >> Is there a workaround to solve this often network-error i see. > > Check the logs and find out why this error occurs and fix the actual problem. > > -- > Sahil Tandon <[EMAIL PROTECTED]> >
Re: .muttrc
Just to add to this, If there is a way to retrieve your ~/.muttrc from a existing mutt session, please let me know. That would help too as my .muttrc is deleted :( TIA, Ravi On Tue, Jul 22, 2008 at 11:23 AM, Ravi Uday <[EMAIL PROTECTED]> wrote: > Hi folks, > > I screwed up my .muttrc and its lost.. > I had the file at ~/.muttrc > > I did a mv ~/ ~/.muttrc > > instead of > > mv ~/ ~/.mutt/ > > and now its gone.. :( > Is there a way to retrieve my ~/.muttrc back on Sun ? > > Thanks in advance, > Ravi >
.muttrc
Hi folks, I screwed up my .muttrc and its lost.. I had the file at ~/.muttrc I did a mv ~/ ~/.muttrc instead of mv ~/ ~/.mutt/ and now its gone.. :( Is there a way to retrieve my ~/.muttrc back on Sun ? Thanks in advance, Ravi
auto-move mails
Hi, In mutt 1.5.17 is there a way we can setup a rule where if the number of emails touches 150 move the first 50 to a specified folder ? We can then map this rule witha key too ? Thanks, - Ravi
Re: .muttrc
Rocco, In that link I didn't find a way to add this request.. If anyone can add the care ticket request that would be great ! Thanks, Ravi On Fri, Jul 25, 2008 at 8:36 AM, Rocco Rutte <[EMAIL PROTECTED]> wrote: > Hi, > > * Michelle Konzack wrote: > >> I wish, there was a function which dump the actuell running config... > > Please add this wish to http://dev.mutt.org/trac/ticket/3064. Maybe it'll be > easy to implement another command such as "save" that will print the > contents to a file rather then a paged menu. > > Rocco >
PGP
Hi, Maybe I am too lazy to google this stuff but what are PGP messages.. I mean I see emails with -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 .. .. -BEGIN PGP SIGNATURE- etc so what does it mean ? Why does mutt support PGP ? Do we need anything to have it setup in our mutt.. Or do we need PGP at all ?? Thanks In Advance Ravi
Re: PGP
Thanks Marianne.. On Wed, Jul 30, 2008 at 6:45 AM, Marianne Promberger <[EMAIL PROTECTED]> wrote: > Hi, > > On Tuesday, 29 July 2008, 21:20 (UTC-0700), Ravi Uday wrote: >> Hi, >> >> Maybe I am too lazy to google this stuff > > Apparently. > >> but what are PGP messages.. I >> mean I see emails with >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> .. >> .. >> -BEGIN PGP SIGNATURE- >> >> etc so what does it mean ? Why does mutt support PGP ? > > The message was cryptographically signed. If you have the public key > corresponding to the private key it was signed with (you can get this > public key e.g. from a public key server), mutt can invoke a > cryptographic program on your system (e.g. GnuPG) to verify that the > signature was made with the private key corresponding to the public > key you have. > > Whether the real-life identity of the person who claims to have sent > the e-mail in fact is the only one having access to that private key > is something that you would need to verify independently, and you > should really google for that (e.g. "web of trust"). > >> Do we need anything to have it setup in our mutt.. > > Yes. > >> Or do we need PGP at all ?? > > That depends on what you mean by "need". > > m. >
sourcing rc
Hi, Whenever I open mutt, I dont get the threaded view..though I have these: set sort=threads set duplicate_threads=yes set sort_aux=last-date I need to :source ~/.muttrc to get into threaded view mode. Samething hapens when I move to a different mailbox and back to INBOX. Do you know why Thanks Ravi
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
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- > >
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: config file
Hi Kyle, signature is indeed verified.. When i send a mail, I see this in the body of the mail: [-- PGP output follows (current time: Tue Aug 19 09:53:01 2008) --] gpg: Signature made Tue Aug 19 09:45:35 2008 PDT using DSA key ID E4D5F777 gpg: Good signature from "xx <[EMAIL PROTECTED]>" [-- End of PGP output --] [-- The following data is signed --] xx [-- End of signed data --] And then there is an attachment (as seen from Outlook 'ATT00076.dat' which has : -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (SunOS) iD8DBQFIqvivwPhtruTV93cRAvQVAKCCUNzqUt4NAgW4NVGtgvscir0PbACeLugg TIGka5xULC+sJIkgKRQ0wl8= =KZe1 -END PGP SIGNATURE- So how can we have this embedded in the body of the mail itself ? and have the name of the file attachment changed to 'signature.asc' When you send a mail, I can see in the body: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- ... -END PGP SIGNATURE- I would like to have the same format..in the body of the mail itself :) Thanks, - Ravi On Tue, Aug 19, 2008 at 7:11 AM, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Monday, August 18 at 09:35 PM, quoth Ravi Uday: >>> Thats pretty much I had.. but then I cant see the >>> >>> --BEGIN PGP MESSAGE-- > > Can't read them, or are they not there? > >>> There is a attachment in the mail and that contains the signature >>> part..! Can we have it inlined in the body of hte mail ? > > Sounds like you're not having mutt actually verify the signature. Add > the following to your muttrc: > > set crypt_verify_sig=yes > > ~Kyle > - -- > Compassion is the basis of morality. > -- Arnold Schopenhauer > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkiq1KgACgkQBkIOoMqOI16O2wCg2vCrf+QuS9iUHBuwI2GbQYZr > u4MAoIZmr+z5wQzUenfjuG4dTwYGDh6J > =gapP > -END PGP SIGNATURE- >
pager width
Hi, - How to set in the pager mode the line character width to '80' its currently 75. Thanks, - Ravi
Unexpected network error
Hi, If i leave mutt open for say 1 or2 hrs theres 99% chance of the "An unexpected network error occurred. " when I try to send mail using 'y' key. I end up closing mutt reopen and then retry this time it goes through. So is there any place i can check why the error occured ? Or any variable which helps me avoid this.. Thanks Ravi
Re: Unexpected network error
Hi Kyle, Yes am using imap with mutt. $timeout was at 15. I reduced it to 10 now. Here are the details: set timeout=10 #set time_inc=250 set net_inc=1 set read_inc=10 set write_inc=10 set connect_timeout=10 #timeout a network connection after x secs Hope th above should fix it. Will get back if it doesnt Thanks, Ravi On Wed, Sep 24, 2008 at 9:45 PM, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wednesday, September 24 at 07:25 PM, quoth Ravi Uday: >> If i leave mutt open for say 1 or2 hrs theres 99% chance of the "An >> unexpected network error occurred. " when I try to send mail using >> 'y' key. I end up closing mutt reopen and then retry this time it >> goes through. > > There's not usually much more information than that, but that sort of > error message suggests to me that you're using mutt to access an IMAP > mailbox, and your connection timed out. I'd say reduce your timeout > values ($timeout and $imap_keepalive). > > ~Kyle > - -- > He who dares not offend cannot be honest. >-- Thomas Paine > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkjbF30ACgkQBkIOoMqOI146lwCeNW2cfAV0/oR8HY81/KY8tTvg > hMwAn2ehvmbPU8Wv2cz4bmrikC578EWA > =0p00 > -END PGP SIGNATURE- >
Re: Unexpected network error
I dont ahve $imap_keepalive set. So you want me to have this : $timeout=15 $imap_keepalive=10 Ravi On Thu, Sep 25, 2008 at 1:47 PM, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thursday, September 25 at 01:35 PM, quoth Ravi Uday: >>Hi Kyle, >> >>Yes am using imap with mutt. $timeout was at 15. I reduced it to 10 now. > > Mutt's IMAP code didn't (until *very* recently) always behave itself > when $timeout is smaller than $imap_keepalive (which defaults to 300). > So unless you're following the hg devel tree pretty closely, I > strongly recommend that you put $timeout back where it was and reduce > $imap_keepalive. > > ~Kyle > - -- > The past isn't dead and buried. In fact, it isn't even past. >-- William Faulkner > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkjb+NEACgkQBkIOoMqOI16jVwCgmvd50vUDT/ReesZCVIKAm0/8 > BMYAoIzMHV3WnZuJZIKC/E2FOW1sejZ9 > =mbFE > -END PGP SIGNATURE- >
Re: Unexpected network error
On Thu, Sep 25, 2008 at 9:01 PM, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thursday, September 25 at 04:26 PM, quoth Ravi Uday: >>I dont ahve $imap_keepalive set. >>So you want me to have this : >> >>$timeout=15 >>$imap_keepalive=10 > > That's awfully small. You can make them bigger (e.g. timeout=300, > imap_keepalive=60, or even larger). I know the man page makes it sound > like timeout really needs to be extra small, but don't sweat it. The > default is 600, and you generally don't really need it anywhere near > as small as 15. Think about that: that's potentially checking your > email every 15 seconds. Depending on the number of mailboxes you have Well 600 is damn big, check your emails every 10mins !! How did you(they) arrive at this number ? Outlook does it every 20 secs or lesser. And its better to get your mails fast then wait for 10mins.. Since I use mutt in a corporate n/w, it doesnt matter if its 10secs/20secs. Ravi > and the latency of your connection, it could easily take longer than > that to complete a check for mail! I know mail admins that get grumpy > when people check their email even every 5 minutes, due to all the > network traffic they generate. When you're checking a file on disk, > well, you can check that pretty dang often without a performance > effect. But over the network? You may be causing your own problem by > having such small timeouts. > > Generally, I would say: stick with the default values unless you have > a reason to change them (the defaults weren't chosen by morons). > Chances are, you can probably leave $timeout at 600. Give the defaults > a try, and go from there. > > ~Kyle > - -- > What progress we are making. In the Middle Ages they would have burned > me. Now they are content with burning my books. > -- Sigmund Freud > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkjcXo4ACgkQBkIOoMqOI16qcQCeOhB3O9JjRDtJDuA96+KFcWmb > 2KcAoM5bQBTBZXtSSC4s4DeCduvRF2vV > =rK7o > -END PGP SIGNATURE- >
Re: Unexpected network error
On Fri, Sep 26, 2008 at 1:28 PM, Kyle Wheeler <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Friday, September 26 at 12:39 PM, quoth Ravi Uday:
>>> That's awfully small. You can make them bigger (e.g. timeout=300,
>>> imap_keepalive=60, or even larger). I know the man page makes it sound
>>> like timeout really needs to be extra small, but don't sweat it. The
>>> default is 600, and you generally don't really need it anywhere near
>>> as small as 15. Think about that: that's potentially checking your
>>> email every 15 seconds. Depending on the number of mailboxes you have
>>
>> Well 600 is damn big, check your emails every 10mins !! How did
>> you(they) arrive at this number?
>
> Generally, over IMAP, the *best* way to do it is to use IMAP's IDLE
> extension. What happens is that the IMAP server will *notify* you when
> you get mail, rather than having you constantly ask it "now? how about
> now? now? now? what about now?", and mutt fully supports the IDLE
> feature (better than some IMAP servers do, actually).
>
> Anyway, I don't know where the 10 minute default came from in the
> beginning, but I think it's quite reasonable.
>
>> Outlook does it every 20 secs or lesser.
>
> No, I'm afraid you're mistaken.
>
> http://email.about.com/od/outlookexpresstips/qt/et052206.htm says:
>
> Decide on how often you want Windows Mail or Outlook Express to
> look for new mail. Typical values are between 10 and 60 minutes.
>
> www.outlook-tips.net/beginner/autosr.htm says:
>
> You should not check it more often than every 8 -10 min because it
> creates too much load on your mail server and a large amount of
> mail will cause some versions of Outlook to hang if it is still
> downloading mail when the next automatic mail pass starts.
>
> I also just loaded up my copy of VirtualBox to check out Microsoft
> Outlook 2000 myself. The default setting for new accounts is to check
> for new messages every 10 minutes, and it's *impossible* to change
> that setting to less than 1 minute (you can see a screen shot of the
Well I am not mistaken. I dont know which version you are using or looked at:
Here is mine : MS Office Outlook 2003 (11.8...) SP3
And in there I can clearly set it at 1 minute.
(Goto : Tools->Send/Receive --> Send-Receive-Settings --> Define
Send/Receive groups)
In there you can see the least allowed is 1 min.
I also spoke with network-admin and he confirmed its in the order of secs.
Practically, I also asked my colleague to send me a email. And within
20-30secs it was there in my Outlook.
> dialog box here: http://www.memoryhole.net/~kyle/outlook.png - note
> the "Check for new messages every" config option in the center of the
> dialog box).
>
>> And its better to get your mails fast then wait for 10mins..
>
> Ummm, okay... I think if someone has something that important to say,
> they should use a medium other than email (such as the phone). Email
> transmission can easily introduce delays of several minutes, long
> before you even have the chance to receive it.
>
>> Since I use mutt in a corporate n/w, it doesnt matter if its
>> 10secs/20secs.
>
> The speed of your network doesn't matter. What matters is the load and
> response time of your IMAP server. I know mail admins (good ones) that
> have warned their users against checking mail more often than every 5
> minutes, despite the fact that most of their clients use a full-duplex
> 100 Base-T ethernet connection to connect to the server (and some use
> gigabit). It's not necessarily the bandwidth, but also the disk I/O -
> when you've got 20+ people all checking their entire folder
> hierarchies constantly, that can kill your server.
>
> Just as an experiment, see how long it takes for the following command
> to kill your computer (or just imagine it; trust me, your computer
> will quickly become unusable):
>
> while true; do find $HOME >/dev/null & done
>
> ...or, even more fun:
>
> while true; do
> find $HOME -type f -exec tail {} \; >/dev/null &
> done
>
> Now, granted, there are ways that you may be able to mitigate the
> problem, and let's not get into questions of how powerful and/or
> efficient and/or well-configured your mail server is. The fact of the
> matter is: checking your mail that quickly (every few seconds) over
> and over again is not only uncommon, but generally a really bad
> idea---even on a corporate network.
>
Well most commonly all your terminals(PCs) will be wired to a VLAN operating
over a catalyst giga-bit switch
Re: Unexpected network error
Ok..sounds like IDLE extension is the way to go. Let me see how to make that extension. Thanks Kyle - Ravi On Fri, Sep 26, 2008 at 3:44 PM, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Friday, September 26 at 03:23 PM, quoth Ravi Uday: >>> I also just loaded up my copy of VirtualBox to check out Microsoft >>> Outlook 2000 myself. The default setting for new accounts is to check >>> for new messages every 10 minutes, and it's *impossible* to change >>> that setting to less than 1 minute (you can see a screen shot of the >> >> Well I am not mistaken. I dont know which version you are using or looked at: >> Here is mine : MS Office Outlook 2003 (11.8...) SP3 >> >> And in there I can clearly set it at 1 minute. >> (Goto : Tools->Send/Receive --> Send-Receive-Settings --> Define >> Send/Receive groups) >> In there you can see the least allowed is 1 min. > > Which is EXACTLY WHAT I SAID. It's impossible to set it to less than 1 > minute. You said you were configuring your Outlook to check every 20 > seconds, which is technically impossible by your own admission. > >> I also spoke with network-admin and he confirmed its in the order of >> secs. > > 60 seconds is "on the order of secs". > >> Practically, I also asked my colleague to send me a email. And within >> 20-30secs it was there in my Outlook. > > That's got nothing to do with anything. The 20-30 second delay could > easily be how long it takes to deliver email, and Outlook could easily > be using the IMAP IDLE extension (or whatever the equivalent is in the > MAPI protocol), which would mean that the mail client gets notified > the very moment that email arrives. > > Mutt also supports the IDLE extension, and can do the exact same thing > you just observed Outlook do, and mutt can do that even with $timeout > set to 600, because IDLE doesn't rely on the client re-checking for > new email. IDLE *informs* the client of new mail *unasked*. It can be > thought of as a "push" protocol. > > Let me say that again: the IDLE extension means that your client tells > the server "let me know when new mail comes", which is different from > periodically checking for new mail. > >> Well most commonly all your terminals(PCs) will be wired to a VLAN >> operating over a catalyst giga-bit switches. It has the capacity to >> switch packets at x-gigs per secs and we are here talking of kb's of >> mail data. Its negligence IMO. > > You didn't read what I wrote. I'm talking about load on the > server, not bandwidth. The fanciness of your network is *irrelevant* > to my point. > > ~Kyle > - -- > They say marriages are made in Heaven. But so is thunder and > lightning. > -- Clint Eastwood > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkjdZdIACgkQBkIOoMqOI17KOQCfaCWjxpk5K+AeZQ+ygREEbNI4 > PRAAnA5Npbg7s0PkHkVtQUaQuYmt6ctv > =8cF0 > -END PGP SIGNATURE- >
global address list
Hi Is there a way to import and use global address list (as in outlook) to mutt? So that we can choose from that addr an id to send mail ? - Ravi
ask for pwd
hi, how to make mutt ask for pwd each time you send email ? maybe once every 10 mails or based on a timer Ravi
Re: ask for pwd
Yea I meant password. I used to use PGP signing with mutt and when we hit 'y' used to ask our password before sending. Now that I removed PGP signing and it doesn't ask for password Ravi On Mon, Mar 2, 2009 at 12:22 PM, Kumar Appaiah wrote: > On Mon, Mar 2, 2009 at 2:10 PM, Kyle Wheeler wrote: >> On Monday, March 2 at 11:54 AM, quoth Ravi Uday: >>>how to make mutt ask for pwd each time you send email ? >>>maybe once every 10 mails or based on a timer >> >> Ask for a pwd? Mutt can't even *change* its pwd (without a patch). >> >> Why would you want mutt to do that? What are you trying to accomplish? > > Using my context sensitive parsing of SMSpeak[1], I presume he means password. > > Kumar > > [1]: http://e-mail.is-not-s.ms/ > -- > Kumar >
Re: ask for pwd
> Ahhh. Well then, I think you can simply create a macro to unset your > $smtp_pass variable every time you send a message, e.g.: > > macro compose y 'unset smtp_pass' > Can this be changed to ask for pwd if mailbox is idle for sometime, typing password for each send operation is time consuming, once in a while is fine. - Ravi
signature
hi how can you make mutt enter the signature at 'cursor' position instead of appending it at the end of mail Ravi
Re: signature
On Fri, Apr 10, 2009 at 1:02 PM, J. Limon wrote: > On Fri, Apr 10, 2009 at 12:54:51PM -0700, Ravi Uday wrote: >> hi >> how can you make mutt enter the signature at 'cursor' position instead >> of appending it at the end of mail >> Ravi > > What's the point of a sig *not* at the end of an email? That would make it > something completely different wouldn't it? > The problem is if its a lengthy email thread with many people replying ontop of each other, when I now write a mail my sig., will be the last line in that email, and doesn';t make sense as to where I ended the email Ravi > -- > "If a problem can be solved there is no use worrying about it. If it can't be > solved, worrying will do no good." >
make install failure
I am trying to install stable mutt version : mutt-1.4.2.3 I configured mutt on my sun m/c using configure --prefix= command properly. (configure --prefix=/users/xxx/mutt-1.4.2.3 --enable-pop --enable-imap --enable-locales-fix) There were no errors, but when i ran 'make install' I got these errors ? >> In file included from /sw/packages/gcc/c3.4.3-p3/sparc-sun-solaris2.8/lib/gcc/sparc-sun-solaris2.8/3.4.3/include/sys/signal.h:44, from /usr/include/signal.h:26, from ../mutt.h:34, from auth.c:23: /usr/include/sys/siginfo.h:259: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:261: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:292: error: parse error before '}' token /usr/include/sys/siginfo.h:292: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:294: error: parse error before '}' token /usr/include/sys/siginfo.h:294: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:390: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:392: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:398: error: conflicting types for '__fault' /usr/include/sys/siginfo.h:267: error: previous declaration of '__fault' was here /usr/include/sys/siginfo.h:404: error: conflicting types for '__file' /usr/include/sys/siginfo.h:273: error: previous declaration of '__file' was here /usr/include/sys/siginfo.h:420: error: conflicting types for '__prof' /usr/include/sys/siginfo.h:287: error: previous declaration of '__prof' was here /usr/include/sys/siginfo.h:424: error: conflicting types for '__rctl' /usr/include/sys/siginfo.h:291: error: previous declaration of '__rctl' was here /usr/include/sys/siginfo.h:426: error: parse error before '}' token /usr/include/sys/siginfo.h:426: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:428: error: parse error before '}' token /usr/include/sys/siginfo.h:428: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t" /usr/include/sys/siginfo.h:437: error: parse error before '}' token /usr/include/sys/siginfo.h:437: error: ISO C forbids data definition with no type or storage class In file included from /usr/include/signal.h:26, from ../mutt.h:34, from auth.c:23: /sw/packages/gcc/c3.4.3-p3/sparc-sun-solaris2.8/lib/gcc/sparc-sun-solaris2.8/3.4.3/include/sys/signal.h:96: error: parse error before "siginfo_t" In file included from ../mutt.h:34, from auth.c:23: /usr/include/signal.h:111: error: parse error before "siginfo_t" /usr/include/signal.h:113: error: parse error before "siginfo_t" make-3.79.1-p3a[2]: *** [auth.o] Error 1 make-3.79.1-p3a[2]: Leaving directory `/users/ruday/mutt-1.4.2.3/imap' make-3.79.1-p3a[1]: *** [install-recursive] Error 1 make-3.79.1-p3a[1]: Leaving directory `/users/ruday/mutt-1.4.2.3' make-3.79.1-p3a: *** [install] Error 2 bash-2.05b$ >> any clues ?
Fwd: make install failure
Anybody care to respond ?? or any other aliases -- Forwarded message -- From: Ravi Uday Date: Wed, May 20, 2009 at 5:38 PM Subject: make install failure To: mutt-users@mutt.org I am trying to install stable mutt version : mutt-1.4.2.3 I configured mutt on my sun m/c using configure --prefix= command properly. (configure --prefix=/users/xxx/mutt-1.4.2.3 --enable-pop --enable-imap --enable-locales-fix) There were no errors, but when i ran 'make install' I got these errors ? >> In file included from /sw/packages/gcc/c3.4.3-p3/sparc-sun-solaris2.8/lib/gcc/sparc-sun-solaris2.8/3.4.3/include/sys/signal.h:44, from /usr/include/signal.h:26, from ../mutt.h:34, from auth.c:23: /usr/include/sys/siginfo.h:259: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:261: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:292: error: parse error before '}' token /usr/include/sys/siginfo.h:292: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:294: error: parse error before '}' token /usr/include/sys/siginfo.h:294: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:390: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:392: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:398: error: conflicting types for '__fault' /usr/include/sys/siginfo.h:267: error: previous declaration of '__fault' was here /usr/include/sys/siginfo.h:404: error: conflicting types for '__file' /usr/include/sys/siginfo.h:273: error: previous declaration of '__file' was here /usr/include/sys/siginfo.h:420: error: conflicting types for '__prof' /usr/include/sys/siginfo.h:287: error: previous declaration of '__prof' was here /usr/include/sys/siginfo.h:424: error: conflicting types for '__rctl' /usr/include/sys/siginfo.h:291: error: previous declaration of '__rctl' was here /usr/include/sys/siginfo.h:426: error: parse error before '}' token /usr/include/sys/siginfo.h:426: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:428: error: parse error before '}' token /usr/include/sys/siginfo.h:428: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t" /usr/include/sys/siginfo.h:437: error: parse error before '}' token /usr/include/sys/siginfo.h:437: error: ISO C forbids data definition with no type or storage class In file included from /usr/include/signal.h:26, from ../mutt.h:34, from auth.c:23: /sw/packages/gcc/c3.4.3-p3/sparc-sun-solaris2.8/lib/gcc/sparc-sun-solaris2.8/3.4.3/include/sys/signal.h:96: error: parse error before "siginfo_t" In file included from ../mutt.h:34, from auth.c:23: /usr/include/signal.h:111: error: parse error before "siginfo_t" /usr/include/signal.h:113: error: parse error before "siginfo_t" make-3.79.1-p3a[2]: *** [auth.o] Error 1 make-3.79.1-p3a[2]: Leaving directory `/users/ruday/mutt-1.4.2.3/imap' make-3.79.1-p3a[1]: *** [install-recursive] Error 1 make-3.79.1-p3a[1]: Leaving directory `/users/ruday/mutt-1.4.2.3' make-3.79.1-p3a: *** [install] Error 2 bash-2.05b$ >> any clues ?
Error when running 'mutt'
bash-2.05b$ mutt Error in /users/xxx/.muttrc, line 166: net_inc: unknown variable Error in /users/xxx/.muttrc, line 181: wrap: unknown variable Error in /users/xxx/.muttrc, line 201: forward_edit: unknown variable Error in /users/xxx/.muttrc, line 248: unauto_view: unknown command source: errors in /users/xxx/.muttrc bash-2.05b$ mutt -v Mutt 1.4i (2002-05-29)
make install failure
hi, I was able to proceed further but am getting following errors when installing : mutt-1.5.19 Please help : ) > manual.xml syntax error in file ./gen-map-doc at line 3, next 2 tokens "use strict" syntax error in file ./gen-map-doc at line 9, next 2 tokens ""cat @ARGV |" or" syntax error in file ./gen-map-doc at line 11, next 2 tokens "/(\w+) "(.+)"/ or" syntax error in file ./gen-map-doc at line 21, next 2 tokens "$map and" Spurious backslash ignored at ./gen-map-doc line 21. Search pattern not terminated in file ./gen-map-doc at line 24, next char ^? syntax error in file ./gen-map-doc at line 42, next 2 tokens "}" Search pattern not terminated in file ./gen-map-doc at line 43, next char ^? syntax error in file ./gen-map-doc at line 51, next 2 tokens "my $map " Execution of ./gen-map-doc aborted due to compilation errors. make-3.79.1-p3a[3]: *** [stamp-doc-xml] Error 255 make-3.79.1-p3a[3]: Leaving directory `/users/xxx/mutt-1.5.19/doc' make-3.79.1-p3a[2]: *** [install-am] Error 2 make-3.79.1-p3a[2]: Leaving directory `/users/xxx/mutt-1.5.19/doc' make-3.79.1-p3a[1]: *** [install-recursive] Error 1 make-3.79.1-p3a[1]: Leaving directory `/users/xxx/mutt-1.5.19' make-3.79.1-p3a: *** [install] Error 2 bash-2.05b$ On Thu, May 21, 2009 at 7:15 PM, Kyle Wheeler wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thursday, May 21 at 09:48 AM, quoth Ravi Uday: > >In file included from > >/sw/packages/gcc/c3.4.3-p3/sparc-sun-solaris2.8/lib/gcc/sparc-sun-solaris2.8/3.4.3/include/sys/signal.h:44, > > from /usr/include/signal.h:26, > > from ../mutt.h:34, > > from auth.c:23: > >/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t" > >/usr/include/sys/siginfo.h:261: error: ISO C forbids data definition > >with no type or storage class > >/usr/include/sys/siginfo.h:292: error: parse error before '}' token > > If you do a google search for that error, you will find this: > http://forums.sun.com/thread.jspa?threadID=5077618 > > I guess what has happened is that you're using a gcc compiler that > was built on Solaris 9 (or some other Solaris release older than > Solaris 10 b69), and this gcc release has a set of "fixed" gcc > specific headers that don't match your s10b69 system headers any > more. > > The fix is to build a fresh set of gcc "fixed" headers: > > # cd /opt/sfw/gcc-3/lib/gcc-lib/i386-pc-solaris2.9/3.3.2/install-tools/ > # cat > mkheaders.conf > SHELL=/bin/sh > SYSTEM_HEADER_DIR="/usr/include" > OTHER_FIXINCLUDES_DIRS="" > FIXPROTO_DEFINES="-D_XOPEN_SOURCE" > STMP_FIXPROTO="stmp-fixproto" > STMP_FIXINC="stmp-fixinc" > ^D > > # ./mkheaders > > Obviously, on your system the paths are slightly different, but I'm > guessing that the problem is the same and the fix is probably very > similar too. > > ~Kyle > - -- > And thou shalt smite the house of Ahab thy master, that I may avenge > the blood of my servants the prophets, and the blood of all the > servants of the LORD, at the hand of Jezebel. For the whole house of > Ahab shall perish. > -- Bible, II Kings (9:7-8) > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iQIcBAEBCAAGBQJKFVsXAAoJECuveozR/AWeidsQALY7Rtrzm5LdU3k1oKKaiv44 > 4/6ualhurVPExJqltedSa0U1Y8YV8vC4OFMnTuipXKR05ISQ4znXdoYhP+TVxivT > l3u4sm7bySA0raM3rcf0cVQRafecND+ZCJ17VoaUoldbC4W11+kynIALpzUgNyiX > AbsjUT46oO7JfvJ8Bpem17HQj61/ikzKH2ycZ3jdTC8rXwbcGFC2YkOmJzECkki0 > ds6/WdEFAQrE3ol1YUpyH/Zutbm7wt0ctgJyfekCK3w+b8/6etYGsE2QqCk+XGz9 > 8IvX7lCuwTbdK6KlNa/yYtZe3n+ZMhGZBSNP+8RV7hlAmLSgzEa3tTyE4gmBnKZw > L7BY2Kh3kAz3EEXdd3nqZx+FZ0V3sp6UCCHjD72y8OIpJGrJEeWQFTxeWnma91GI > uFilmb637E/cNduarm/hvReSGz8BruLCT6rf7TzX08Xs229Iwu8e7K2xzVCMQlpD > i6yisia1U1paHwkWFtojxNLhtZjt7X3PlaVMq1E2vwGW67AONKxN+GxlZE6pDC5K > BJhvYxVRlIxzMeNZlxoTRL0zkJhZJqDVpChRgvpQxSMebeKcC+PafmkGbqeBRQob > P5vOPfKZ7i9z9qpg/c6s3sy3xdpu3PLsG6GqbAZiyvljs5oSxpm3+D0PxYniUJH5 > jVdZ+JrtjBcLaxYRyzDw > =XbUI > -END PGP SIGNATURE-
Re: make install failure
Its 4.0 bash-2.05b$ perl -v This is perl, version 4.0 $RCSfile: perl.c,v $$Revision: 4.0.1.8 $$Date: 1993/02/05 19:39:30 $ Patch level: 36 On Wed, May 27, 2009 at 5:55 PM, Rocco Rutte wrote: > Hi, > > * Ravi Uday wrote: > >> syntax error in file ./gen-map-doc at line 3, next 2 tokens "use strict" > [...] > > What perl version do you have? > > Rocco >
Re: make install failure
Ok, i did 'make clean' and 'make install' after changing toplevel Makefile. Following errors are seen. Any clues ? >> In file included from /sw/packages/gcc/c3.4.3-p3/sparc-sun-solaris2.8/lib/gcc/sparc-sun-solaris2.8/3.4.3/include/sys/signal.h:44, from /usr/include/signal.h:26, from ../mutt.h:37, from auth.c:27: /usr/include/sys/siginfo.h:259: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:261: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:292: error: parse error before '}' token /usr/include/sys/siginfo.h:292: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:294: error: parse error before '}' token /usr/include/sys/siginfo.h:294: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:390: error: parse error before "ctid_t" /usr/include/sys/siginfo.h:392: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:398: error: conflicting types for '__fault' /usr/include/sys/siginfo.h:267: error: previous declaration of '__fault' was here /usr/include/sys/siginfo.h:404: error: conflicting types for '__file' /usr/include/sys/siginfo.h:273: error: previous declaration of '__file' was here /usr/include/sys/siginfo.h:420: error: conflicting types for '__prof' /usr/include/sys/siginfo.h:287: error: previous declaration of '__prof' was here /usr/include/sys/siginfo.h:424: error: conflicting types for '__rctl' /usr/include/sys/siginfo.h:291: error: previous declaration of '__rctl' was here /usr/include/sys/siginfo.h:426: error: parse error before '}' token /usr/include/sys/siginfo.h:426: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:428: error: parse error before '}' token /usr/include/sys/siginfo.h:428: error: ISO C forbids data definition with no type or storage class /usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t" /usr/include/sys/siginfo.h:437: error: parse error before '}' token /usr/include/sys/siginfo.h:437: error: ISO C forbids data definition with no type or storage class In file included from /usr/include/signal.h:26, from ../mutt.h:37, from auth.c:27: /sw/packages/gcc/c3.4.3-p3/sparc-sun-solaris2.8/lib/gcc/sparc-sun-solaris2.8/3.4.3/include/sys/signal.h:96: error: parse error before "siginfo_t" In file included from ../mutt.h:37, from auth.c:27: /usr/include/signal.h:111: error: parse error before "siginfo_t" /usr/include/signal.h:113: error: parse error before "siginfo_t" make-3.79.1-p7[2]: *** [auth.o] Error 1 make-3.79.1-p7[2]: Leaving directory `/users/ruday/mutt-1.5.19/imap' make-3.79.1-p7[1]: *** [install-recursive] Error 1 make-3.79.1-p7[1]: Leaving directory `/users/ruday/mutt-1.5.19' make-3.79.1-p7: *** [install] Error 2 bash-2.05b$ >> bash-2.05b$ uname -a SunOS xx-view2 5.10 Generic_137111-06 sun4u sparc SUNW,Sun-Fire-V890 bash-2.05b$ On Thu, May 28, 2009 at 5:04 PM, Rocco Rutte wrote: > Hi, > > * Ravi Uday wrote: > >> Its 4.0 > > Wow. > >> $RCSfile: perl.c,v $$Revision: 4.0.1.8 $$Date: 1993/02/05 19:39:30 $ >> Patch level: 36 > > Your perl version is from 1993! Did you get that from a museum on tape? :-) > > Seriously, I don't think we should/need/do support something older than > perl 5.003. With perl 4 I think your only options is to not build docs > at all (edit top-level Makefile and remove 'doc' from the SUBDIRS and > DIST_SUBDIRS lines) (or remove the perl call in doc/Makefile.am and live > with partial documentation). > > Rocco >
Re: make install failure
I was expecting the 'configure' script to fail with 'old gcc' error msg ? - Ravi On Wed, Jun 3, 2009 at 8:42 PM, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wednesday, June 3 at 11:48 AM, quoth Ravi Uday: >>Ok, i did 'make clean' and 'make install' after changing toplevel Makefile. >> >>Following errors are seen. Any clues ? > > What I said before was that, according to google, these errors most > likely indicate that your compiler (gcc) was originally configured and > compiled on an older version of Solaris and that now that you've > upgraded to a newer version, your compiler needs to be updated. > > These look like the exact same type of errors. If we assume for the > moment that my advice was correct, you will continue to get these > exact same errors until you update your compiler. > > What were you expecting to happen? Why were you expecting that? > > ~Kyle > - -- > Habits of thought persist through the centuries; and while a healthy > brain may reject the doctrine it no longer believes, it will continue > to feel the same sentiments formerly associated with that doctrine. > -- Charlotte Perkins Gilman > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iQIcBAEBCAAGBQJKJpLDAAoJECuveozR/AWeTe0P+waFaGzowBfeR2ZMUhVKVrLa > y1SlYVN6zBM2WbO17mq2mydrRT7jo6xSjpSWoWWM0QNT2/OzC44u3gaFlhANozCd > Q4KJFAWN5FQRMdsRKHJlQomeCSFXE0f8MjxcLHQwgZU5Yfw/99gpL/CFsgk9Q7l1 > /9H12QRAjl1n2eqwkpeQXqsDujMwYUJ/WBGZKRN15/EnYNRVR9rgQezH1XdbjN/Y > +pL20a7tQPun5y6PMxSMvMdCEvoixOrQPMoxyyIiYWxwyjbwqdSHeU3MAGcZuvAu > hdx8xVBF3f3n69xVfpb8Dps6CZMdlRuVBvxq8zIb+icXOtK7XD6qM4i5lEtXuegP > zLZbQm8lwo9AoFWasXugcnrSh9WwmRh9+u0/C1EXfBJRDESMWRhGKGj83WOpPtHv > HhUvGy/iqM8jGAFAYvpyS0CPRtziBB2v9SASd11TitFtswfRrijNFRP/lFrFrghT > mCylsNxMw4+29MMRuZiWUdW9lYDQovUGUz+v417P4B8/B1YKK95bAM3E5vEd/8o5 > +t/IH6pb9N6j/7/XdT2JYdBSLFKj5QGCy+Z3fDJdSgi68WCjsYsFrnythhp8+/En > QspiVfpX3d5q9XZjnhpYdi7JENUmCUMNZneAfGT1crg1M6TwksVo1+j3VCBQCsm3 > d56jY2iP3i8QxrKVoQI/ > =C5Vj > -END PGP SIGNATURE- >
pressing 'g' truncates
hi after reading mail, when i press 'g' to reply-to-all i see mail msg is truncated to some bytes. How to get whole mail alongside my reply. - ravi
Re: pressing 'g' truncates
I think its only some msgs, as I don't see it happening now. But it definitely happens. Is there a way to find out which msgs it truncates - Ravi On Thu, Aug 13, 2009 at 7:09 PM, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Thursday, August 13 at 05:21 PM, quoth Ravi Uday: >>after reading mail, when i press 'g' to reply-to-all >>i see mail msg is truncated to some bytes. >>How to get whole mail alongside my reply. > > Hmm, it's not *supposed* to be truncated. Is there something unusual > about one particular message, or are ALL messages truncated? > > ~Kyle > - -- > Captain, the most elementary and valuable statement in science, the > beginning of wisdom is "I do not know." > -- Lt. Cmdr Data > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iQIcBAEBCAAGBQJKhBeaAAoJECuveozR/AWeV7kP/1ApnPoKm7WiGNag13wf60Yq > HSbuNI+kplJzUcxBRlKKn1xKhRsYmosbLC4gPQ2HhUdwoaZznAFB4SlDYmqBvtwU > 1FuLBj+osvQoVCCF3obFmHEYDTfXfNhf2u1a2clF2oIagcRjFudN6PUiGO6sPGqj > AbVfE2+4rAdjTpzNwlGedmGmU2AmFjE814PCAdUeYy3A3EyTHsOhd67OUCtOJkU0 > 2n8VhR4YzJbih1d0H58ftY0D9pDDS+2qzJhPsmU65TTA7vALC0h8KU03SKObfAUp > 7mSrLXxWSnDmetemuxeqrBjj187dGrUQ86VawioJry5Di8xSrV3Z3ejfyUtgUgUl > Kmd4FOn9QKT7UvqQnfrL/N2pk9pUeqz59+h6znEKu8pjEJ9qWR+Ysp3pt2Y7Z+5E > guXP/ccdP6JXoSE+YIWoGa9cV20QFu5S7QDLkWCEjepvs6QgqQU6q6r0Vflk1SWY > oDSzBXXctzHMtqR8zTYGbedkb8OE8CSUIZf7wt/v4D+9asvcGfM9k2yicmuVplRN > iR5BOH3oRz++L2jwOx/fxBFhRrsIp7lsByd0pdbmNwZ7KsXe/HwtcWY8q5nutnpR > aNUr4/IT7GDeoJQ0aErd3jc8LhKOodmMoJ1SDUfY+QJugRaUwtI86foMBLDFl0Xq > EttPTs3hj2gX5Pw0gA9J > =Sfrw > -END PGP SIGNATURE- >
time
Hi, how to change the date and time format from PST to IndianStandardTime (IST) in .muttrc - ravi
Re: time
Kyle, This didn't work. The mail header shows : Date: Tue, 5 Jan 2010 21:59:44 -0800 but my laptop's time is : Jan-6th-2010 11:38 AM. - Ravi On Tue, Jan 5, 2010 at 11:50 PM, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tuesday, January 5 at 11:42 PM, quoth Ravi Uday: >>Hi, >> >>how to change the date and time format from >>PST to IndianStandardTime (IST) in .muttrc > > Add this to your ~/.bashrc: > > export TZ=IST > > ~Kyle > - -- > However many holy words you read, However many you speak, what good > will they do you If you do not act on upon them? > -- Buddha > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iQIcBAEBCAAGBQJLQ4MBAAoJECuveozR/AWeg+4P/iuYmERmpA5Bz5Be6abU1/6l > 3I/CzVLamlSKfWvPeXvalTBYZKv9nHb4Hqw3U8tmoVC926aLjl5bfb38dbrHmQ/j > DtJE9xkOS7wNU+T13l4p3IrZaCPua3Ld0YP6nzvWrRpnlJXgxbJsDn/3tTlR8VZ4 > /bGGwOq9Co31wskN0q5HYHs5wUrrmb8j4FMFur+7iOScRkvU0t+9ltDYxdSN84YT > YAhmZ8NIpm0r9RWQniREwqP2/oZiVqhoqEVbBbte2BGEajy/0oOJLVZ471j8fSYy > E42xYVSU7sEMKQfIUG4P84Wkw7COszL+LR0iLw0XphIzYeGx5X6Z6EnArqINIBa8 > T3EUiovCW5PRCraW+LOCOWKkD2GrDCwyfmXs3x25sw2YgnE/keskEt3kYNmwSjCu > HdNG2iRsGh6kOYvgWmfgBXFl7hd37aSRq18B5pijMw69aIBjKdORy3jy1TpNamst > AtZ+TuSgL8OecRXPYPCMZJPxmRo7mk5BQUFRMm+U8xaeF2uXYfbs2/y48LpSnaD5 > zILkjzIw8r04cRo1JEehMjETozo0BOj7JCESmw6KDpMXKrcLUJ1taZbkDkYc/R9b > lkO0Ri/LNud132CuTL+VL3l9YNNHDocSAKWCdBlCznT5l0mH4iXGqCtakCx2BKM1 > c4KCEjULj82nyvEfHfFc > =WlUG > -END PGP SIGNATURE- >
Re: time
Yes I did it. On the linux server where i run mutt : bash-3.00$ date Wed Jan 6 08:44:40 IST 2010 Now from within mutt, if I check a recent mail's header, I see this : .. Date: Wed, 6 Jan 2010 00:44:27 -0800 .. I just have export TZ=IST in my .bashrc. Both the dates(from bash and from within mutt) are wrong when I see from my windows m/c. It rightly shows - Jan-6-2010 2:15 PM ! whichis the correct time now - Ravi On Wed, Jan 6, 2010 at 1:27 PM, Patrick Ben Koetter wrote: > * Ravi Uday : >> Kyle, >> >> This didn't work. >> >> The mail header shows : >> >> Date: Tue, 5 Jan 2010 21:59:44 -0800 >> >> but my laptop's time is : Jan-6th-2010 11:38 AM. > > Did you source the ~/.bashrc after editing it? > > p...@rick > > > >> >> - Ravi >> >> On Tue, Jan 5, 2010 at 11:50 PM, Kyle Wheeler >> wrote: >> > -BEGIN PGP SIGNED MESSAGE- >> > Hash: SHA256 >> > >> > On Tuesday, January 5 at 11:42 PM, quoth Ravi Uday: >> >>Hi, >> >> >> >>how to change the date and time format from >> >>PST to IndianStandardTime (IST) in .muttrc >> > >> > Add this to your ~/.bashrc: >> > >> > export TZ=IST >> > >> > ~Kyle >> > - -- >> > However many holy words you read, However many you speak, what good >> > will they do you If you do not act on upon them? >> > -- Buddha >> > -BEGIN PGP SIGNATURE- >> > Comment: Thank you for using encryption! >> > >> > iQIcBAEBCAAGBQJLQ4MBAAoJECuveozR/AWeg+4P/iuYmERmpA5Bz5Be6abU1/6l >> > 3I/CzVLamlSKfWvPeXvalTBYZKv9nHb4Hqw3U8tmoVC926aLjl5bfb38dbrHmQ/j >> > DtJE9xkOS7wNU+T13l4p3IrZaCPua3Ld0YP6nzvWrRpnlJXgxbJsDn/3tTlR8VZ4 >> > /bGGwOq9Co31wskN0q5HYHs5wUrrmb8j4FMFur+7iOScRkvU0t+9ltDYxdSN84YT >> > YAhmZ8NIpm0r9RWQniREwqP2/oZiVqhoqEVbBbte2BGEajy/0oOJLVZ471j8fSYy >> > E42xYVSU7sEMKQfIUG4P84Wkw7COszL+LR0iLw0XphIzYeGx5X6Z6EnArqINIBa8 >> > T3EUiovCW5PRCraW+LOCOWKkD2GrDCwyfmXs3x25sw2YgnE/keskEt3kYNmwSjCu >> > HdNG2iRsGh6kOYvgWmfgBXFl7hd37aSRq18B5pijMw69aIBjKdORy3jy1TpNamst >> > AtZ+TuSgL8OecRXPYPCMZJPxmRo7mk5BQUFRMm+U8xaeF2uXYfbs2/y48LpSnaD5 >> > zILkjzIw8r04cRo1JEehMjETozo0BOj7JCESmw6KDpMXKrcLUJ1taZbkDkYc/R9b >> > lkO0Ri/LNud132CuTL+VL3l9YNNHDocSAKWCdBlCznT5l0mH4iXGqCtakCx2BKM1 >> > c4KCEjULj82nyvEfHfFc >> > =WlUG >> > -END PGP SIGNATURE- >> > > > -- > Postfix - Einrichtung, Betrieb und Wartung > <http://www.postfix-buch.com> > saslfinger (debugging SMTP AUTH): > <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/> >
Re: time
It is still the same. on linux : bash-3.00$ date Wed Jan 6 17:24:25 Asia/Kolkata 2010 bash-3.00$ On a new email, inside mutt the header shows it as : Date: Wed, 6 Jan 2010 09:24:20 -0800 I just have: export TZ="Asia/Kolkata" in my .bashrc. The actual time should be : 10:54:25 PM - Jan-6th-2010. - Ravi On Wed, Jan 6, 2010 at 9:37 PM, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wednesday, January 6 at 11:42 AM, quoth Ravi Uday: >>Kyle, >> >>This didn't work. >> >>The mail header shows : >> >>Date: Tue, 5 Jan 2010 21:59:44 -0800 >> >>but my laptop's time is : Jan-6th-2010 11:38 AM. > > As Derek Martin pointed out, I got the TZ value wrong. It should be: > > export TZ="Asia/Kolkata" > > ~Kyle > - -- > He who joyfully marches in rank and file has already earned my > contempt. He has been given a large brain by mistake, since for him > the spinal cord would suffice. > -- Albert Einstein > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iQIcBAEBCAAGBQJLRLUnAAoJECuveozR/AWeWsEP/iCWPJgPqihMBh8nV3Xut00a > WarmmVnbyYzuyeeXZMB9VoUUNRLjcDy/lO6uc6eyr0GilGNdSz0Qdzuoq62Lq8zb > +FrZjGN00o6OnogAfaO86vLEOe2jSaFJ40vTdxwgfQGAyDVhXh+v/CBBlRkSoO4e > CiZO022yrRG3gTc/B55qFySLhsfmM7SQB/ke1rq5fkVDkrw8QmHbNRSNH24CFUzD > sV+aePUgzdF1CbNbcwD3tuaUcBtraOY+K6Rufse23fhiBCnnY32JwffEPGbo7I6W > 8JyfOmZg+VbOJDxCQUy9TSspSolWf0bnBJiZc4dr9Bf8oFIv6sw3Hnh2rEfMjYnS > vjnZNwE4Uz0sprDWoY6YFGpdzEamGulVVEsV3UA1Mwd81Tg/olNutYCubdibOyCt > Wn0qNRzLjyOFc46QSasPQSrQEWUdoc0u9LuhEhZP2GFbOjE3V0fdc0iuggWW6yCr > YiTbogLuZF1HUPy+u9Ltfd0Mg/MaM1WaHtXjZRRxKBsWSjF+wlNIJJ2s6bi3wfU2 > pQtIcpmhDinxXHkViJ6B5J/XYkN/ywtC7HnWgYewMT2oA7rd0FO5MYblh3vEX1yP > /IDE8V/pV39b3ojnhpBSlLCq1U67w6Ce3eoQ/NbOCFyXKa+ocdOoSyHiqB7+aF/U > aF/yO+dWwIV9IvkSmHIW > =wcqb > -END PGP SIGNATURE- >
msg-body clipped
Hi, In some of the emails i receive if I hit 'g' to reply, I see part of the body of the message is clipped. However in Outlook same mail when reply-all, the whole body is intact. Why does mutt clip the reply ? - Ravi Sample mail: >From gdmur...@xyz.com Wed Feb 3 23:03:43 2010 Received: by xmb-sjc-219.amer.xyz.com id <01caa525.21a21...@xmb-sjc-219.amer.xyz.com>; Wed, 3 Feb 2010 15:03:43 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: Re: xz Date: Wed, 3 Feb 2010 15:03:41 -0800 Message-ID: <997e596f9efa534fa5cc3416fe722b802f4...@xmb-sjc-219.amer.xyz.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: xz Thread-Index: Acqkjf7aIWjlKGFXRlGKIOICnzqpJwAj1p9AAAHvOvA= References: <20100203050146.gd23...@xyz.com> From: "Ganesh Murthy (gdmurthy)" To: "Ganesh Murthys (gdmurthy)" , "Ravi Uday (xyz)" Cc: =20
install error mutt-1.5.19
Following error is seen when installing on Linux x86 64bit m/c
>
if test -f /users/ruday/mutt-install//bin/mutt_dotlock && test xmail
!= x ; then \
chgrp mail /users/ruday/mutt-install//bin/mutt_dotlock && \
chmod 2755 /users/ruday/mutt-install//bin/mutt_dotlock || \
{ echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
fi
chgrp: changing group of
`/users/ruday/mutt-install//bin/mutt_dotlock': Operation not permitted
Can't fix mutt_dotlock's permissions!
make-3.79.1-p7[4]: *** [install-exec-hook] Error 1
make-3.79.1-p7[4]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7[3]: *** [install-exec-am] Error 2
make-3.79.1-p7[3]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7[2]: *** [install-am] Error 2
make-3.79.1-p7[2]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7[1]: *** [install-recursive] Error 1
make-3.79.1-p7[1]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7: *** [install] Error 2
bash-3.00$
>
Anybody knows how to fix it.
- Ravi
configure was done using :
bash-3.00$
bash-3.00$ cat tmp.txt
bash-3.00$ configure --with-exec-shell=bash --enable-imap --enable-pop
--prefix=/users/ruday/mutt-install/ --with-ssl --disable-fcntl
--without-wc-funcs --enable-exact-address
bash-3.00$
bash-3.00$
bash-3.00$ cd bin
bash-3.00$
bash-3.00$ ls
flea mutt muttbug mutt_dotlock pgpewrap pgpring smime_keys
bash-3.00$
bash-3.00$
bash-3.00$ ls -al
total 2580
drwxr-xr-x 2 ruday eng 4096 Aug 4 18:14 .
drwxr-xr-x 5 ruday eng 4096 Aug 4 18:14 ..
-rwxr-xr-x 1 ruday eng 8066 Aug 4 18:14 flea
-rwxr-xr-x 1 ruday eng 2414752 Aug 4 18:14 mutt
-rwxr-xr-x 1 ruday eng 26 Aug 4 18:14 muttbug
-rwxr-xr-x 1 ruday eng 27062 Aug 4 18:14 mutt_dotlock
-rwxr-xr-x 1 ruday eng 12318 Aug 4 18:14 pgpewrap
-rwxr-xr-x 1 ruday eng 120959 Aug 4 18:14 pgpring
-rwxr-xr-x 1 ruday eng 26284 Aug 4 18:14 smime_keys
bash-3.00$
Re: install error mutt-1.5.19
Some errors went away. But still am getting this :
>>
..
/usr/bin/install -c 'flea' '/users/ruday/mutt-install/bin/flea'
/usr/bin/install -c 'smime_keys' '/users/ruday/mutt-install/bin/smime_keys'
make-3.79.1-p7 install-exec-hook
make-3.79.1-p7[4]: Entering directory `/users/ruday/mutt-1.5.19'
if test -f /users/ruday/mutt-install/bin/mutt.dotlock && test -f /users/ruday/mu
tt-install/bin/mutt_dotlock ; then \
rm -f /users/ruday/mutt-install/bin/mutt.dotlock ; \
ln -sf /users/ruday/mutt-install/bin/mutt_dotlock /users/ruday/mutt-inst
all/bin/mutt.dotlock ; \
fi
if test -f /users/ruday/mutt-install/bin/mutt_dotlock && test xmail != x ; then
\
chgrp mail /users/ruday/mutt-install/bin/mutt_dotlock && \
chmod 2755 /users/ruday/mutt-install/bin/mutt_dotlock || \
{ echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
fi
chgrp: changing group of `/users/ruday/mutt-install/bin/mutt_dotlock': Operation
not permitted
Can't fix mutt_dotlock's permissions!
make-3.79.1-p7[4]: *** [install-exec-hook] Error 1
make-3.79.1-p7[4]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7[3]: *** [install-exec-am] Error 2
make-3.79.1-p7[3]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7[2]: *** [install-am] Error 2
make-3.79.1-p7[2]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7[1]: *** [install-recursive] Error 1
make-3.79.1-p7[1]: Leaving directory `/users/ruday/mutt-1.5.19'
make-3.79.1-p7: *** [install] Error 2
bash-3.00$
>
- Ravi
> On Thu, Aug 4, 2011 at 9:16 PM, Jostein Berntsen wrote:
>>
>> On 04.08.11,18:23, Ravi Uday wrote:
>> > Following error is seen when installing on Linux x86 64bit m/c
>> > >
>> > if test -f /users/ruday/mutt-install//bin/mutt_dotlock && test xmail
>> > != x ; then \
>> > chgrp mail /users/ruday/mutt-install//bin/mutt_dotlock && \
>> > chmod 2755 /users/ruday/mutt-install//bin/mutt_dotlock || \
>> > { echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
>> > fi
>> > chgrp: changing group of
>> > `/users/ruday/mutt-install//bin/mutt_dotlock': Operation not permitted
>> > Can't fix mutt_dotlock's permissions!
>> > make-3.79.1-p7[4]: *** [install-exec-hook] Error 1
>> > make-3.79.1-p7[4]: Leaving directory `/users/ruday/mutt-1.5.19'
>> > make-3.79.1-p7[3]: *** [install-exec-am] Error 2
>> > make-3.79.1-p7[3]: Leaving directory `/users/ruday/mutt-1.5.19'
>> > make-3.79.1-p7[2]: *** [install-am] Error 2
>> > make-3.79.1-p7[2]: Leaving directory `/users/ruday/mutt-1.5.19'
>> > make-3.79.1-p7[1]: *** [install-recursive] Error 1
>> > make-3.79.1-p7[1]: Leaving directory `/users/ruday/mutt-1.5.19'
>> > make-3.79.1-p7: *** [install] Error 2
>> > bash-3.00$
>> > >
>> > Anybody knows how to fix it.
>> > - Ravi
>> > configure was done using :
>> >
>>
>> Is there one too many forward slash in this path?
>>
>> /users/ruday/mutt-install//bin/mutt_dotlock
>>
>>
>> Jostein
>>
>>
>
Re: install error mutt-1.5.19
Hi,
I will try latest mutt, but in my office I dont have admin rights (sudo rights)
I am just a user of this linux build server.
SO are you saying there is no way to install if you are not a admin ?
- Ravi
On Fri, Aug 5, 2011 at 12:14 AM, Jostein Berntsen wrote:
> On 04.08.11,23:04, Ravi Uday wrote:
>> Some errors went away. But still am getting this :
>>
>> >>
>> ..
>> /usr/bin/install -c 'flea' '/users/ruday/mutt-install/bin/flea'
>> /usr/bin/install -c 'smime_keys' '/users/ruday/mutt-install/bin/smime_keys'
>> make-3.79.1-p7 install-exec-hook
>> make-3.79.1-p7[4]: Entering directory `/users/ruday/mutt-1.5.19'
>> if test -f /users/ruday/mutt-install/bin/mutt.dotlock && test -f
>> /users/ruday/mu
>> tt-install/bin/mutt_dotlock ; then \
>> rm -f /users/ruday/mutt-install/bin/mutt.dotlock ; \
>> ln -sf /users/ruday/mutt-install/bin/mutt_dotlock
>> /users/ruday/mutt-inst
>> all/bin/mutt.dotlock ; \
>> fi
>> if test -f /users/ruday/mutt-install/bin/mutt_dotlock && test xmail != x ;
>> then
>> \
>> chgrp mail /users/ruday/mutt-install/bin/mutt_dotlock && \
>> chmod 2755 /users/ruday/mutt-install/bin/mutt_dotlock || \
>> { echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
>> fi
>> chgrp: changing group of `/users/ruday/mutt-install/bin/mutt_dotlock':
>> Operation
>> not permitted
>> Can't fix mutt_dotlock's permissions!
>> make-3.79.1-p7[4]: *** [install-exec-hook] Error 1
>> make-3.79.1-p7[4]: Leaving directory `/users/ruday/mutt-1.5.19'
>> make-3.79.1-p7[3]: *** [install-exec-am] Error 2
>> make-3.79.1-p7[3]: Leaving directory `/users/ruday/mutt-1.5.19'
>> make-3.79.1-p7[2]: *** [install-am] Error 2
>> make-3.79.1-p7[2]: Leaving directory `/users/ruday/mutt-1.5.19'
>> make-3.79.1-p7[1]: *** [install-recursive] Error 1
>> make-3.79.1-p7[1]: Leaving directory `/users/ruday/mutt-1.5.19'
>> make-3.79.1-p7: *** [install] Error 2
>> bash-3.00$
>> >
>>
>>
>
> Have you installed with "./configure && make && sudo make install"?
>
> You might also check out the most recent version 1.5.21 which has some bug
> fixes:
>
> http://www.mutt.org/download.html
>
>
> Jostein
>
>
>
Re: install error mutt-1.5.19
Hi David,
Looks like its same issue even w/ 1.5.21 :
make-3.79.1-p7[4]: Entering directory `/users/ruday/mutt-1.5.21'
if test -f /users/ruday/mutt-install/bin/mutt.dotlock && test -f
/users/ruday/mutt-install/bin/mutt_dotlock ; then \
rm -f /users/ruday/mutt-install/bin/mutt.dotlock ; \
ln -sf /users/ruday/mutt-install/bin/mutt_dotlock
/users/ruday/mutt-install/bin/mutt.dotlock ; \
fi
if test -f /users/ruday/mutt-install/bin/mutt_dotlock && test xmail !=
x ; then \
chgrp mail /users/ruday/mutt-install/bin/mutt_dotlock && \
chmod 2755 /users/ruday/mutt-install/bin/mutt_dotlock || \
{ echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
fi
chgrp: changing group of `/users/ruday/mutt-install/bin/mutt_dotlock':
Operation not permitted
Can't fix mutt_dotlock's permissions!
make-3.79.1-p7[4]: *** [install-exec-hook] Error 1
make-3.79.1-p7[4]: Leaving directory `/users/ruday/mutt-1.5.21'
make-3.79.1-p7[3]: *** [install-exec-am] Error 2
make-3.79.1-p7[3]: Leaving directory `/users/ruday/mutt-1.5.21'
make-3.79.1-p7[2]: *** [install-am] Error 2
make-3.79.1-p7[2]: Leaving directory `/users/ruday/mutt-1.5.21'
make-3.79.1-p7[1]: *** [install-recursive] Error 1
make-3.79.1-p7[1]: Leaving directory `/users/ruday/mutt-1.5.21'
make-3.79.1-p7: *** [install] Error 2
bash-3.00$
Not sure what I can do here. I wonder how others manage to install.
Not all have admin rights isn't it ?
- Ravi
On Fri, Aug 5, 2011 at 9:11 PM, David Champion wrote:
> * On 05 Aug 2011, Ravi Uday wrote:
>
>> Hi,
>>
>> I will try latest mutt, but in my office I dont have admin rights
>> (sudo rights) I am just a user of this linux build server. SO are you
>> saying there is no way to install if you are not a admin ?
>
> In th past there have been problems in the install parts of the Makefile
> which make installing as non-admin difficult. As far as I know these
> are fixed in mutt 1.5.21, so you should have better luck if you update.
>
> --
> David Champion • d...@uchicago.edu • IT Services • University of Chicago
>
error opening mail
After I type in my pwd inside after running mutt applicaiton, I get Logging In and then this msg "Error opening mailbox" How do I fix this - Ravi
