Re: Bad IDN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, May 26 at 01:35 AM, quoth markus reichelt: >Error in ~/.mutt-aliases, line 1: Warning: Bad IDN 'cs.hmc.edu' in >alias 'muttdude'. I don't entirely understand the IDN business (it seems like black voodoo to me), but it might go away if you compile mutt without idn support (--without-idn). ~Kyle - -- If any man come to me, and hate not his father, and mother, and wife, and children, and brethren, and sisters, yeah, and his own life also, he cannot be my disciple. -- Prince of Peace, Jesus Christ (Luke 14:26) -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFGV8sPBkIOoMqOI14RAuoUAJ9jZXFQt7IQcBW0aPCpF1YUrC+37gCeIgeA Qjhr9snu69wv5mBm9qIa6M8= =ORW1 -END PGP SIGNATURE-
Bad IDN
Hi, I'm having some fun with mutt 1.5.15 ... make distclean; ./configure --enable-hcache && make && sudo make install for one, I noticed that aliases don't work, even done by the book source ~/.mutt-aliases set alias_file=~/.mutt-aliases even the example mentioned in the doc alias muttdude [EMAIL PROTECTED] (Michael Elkins) produces this fine error: Error in ~/.mutt-aliases, line 1: Warning: Bad IDN 'cs.hmc.edu' in alias 'muttdude'. So I decided to tell this list about it and gee, guess what happened ... I can't compose mails with mutt 1.5.15 at all! mutt complains about a bad IDN again stubbornly refuses to accept the address. I'm back on .13 for now. my system runs slackware 11.0 with a recent kernel: Mutt 1.5.15 (2007-04-06) Copyright (C) 1996-2007 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: Linux 2.6.20.11 (i686) ncurses: ncurses 5.5.20051010 (compiled with 5.5) libidn: 0.6.5 (compiled with 0.6.5) Einstellungen bei der Compilierung: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_INODESORT -USE_POP -USE_IMAP -USE_SMTP -USE_GSS -USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -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="/usr/bin/ispell" SENDMAIL="/usr/bin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER -- left blank, right bald pgprSTiAus8VX.pgp Description: PGP signature
Re: OT: offending sig + headers
Michelle, On Thu, May 24, 2007 at 07:25:27PM +0200, Michelle Konzack wrote: > Am 2007-05-17 20:45:54, schrieb Derek Martin: > > that's true, I am arrogant. But I'm also right. My methods minimize > > the time spent reviewing unwanted mail, while also GUARANTEEING ZERO > > LOST MAIL WITH 100% CERTAINTY. No other anti-spam methodology can do > > This is not right, since IF someone want to send you quickly a message > YOU LOST THIS MESSAGE and OFFEND THE SENDER! -- You lost! SPAM is whatever the individual defines it to be. I have defined private messages from list participants as spam, and I am not concerned about losing them -- obviously. *I* get to decide what is important *to me*, and I don't believe it is possible that any participants here can have something "important" to tell me that is unsuitable for posting to the list. And if it really is that important, I can be found fairly easily through the information contained in my sig, as I have stated repeatedly. I didn't want to be rude, but I also don't want to rehash this whole thread, so the only other thing I have to say is that I did read all of your messages, and your arguments are not any different from all of the other arguments people have made over the last 5 years or so, and I remain unswayed. I find your methods unsuitable. I believe I adequately addressed each one of your points previously in the thread. If you choose to black-list me because you think my behavior is anti-social, that's your prerogative. Please let this thread die the death it deserves. ;-) Thanks! -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience. pgpCmJyWyG5WR.pgp Description: PGP signature
Re: Poll: Quoting behaviour
* Rocco Rutte <[EMAIL PROTECTED]> [2007-03-19 22:21 +0100]: > So the question is how to proceed. The following options are > available: > > 1) Introduce $quote_empty that makes this behaviour configurable > 2) Restore the original behaviour for the f=f handler > 3) Do 1 + 2 > > Opinions? 3) -- dave [ please don't CC me ]
Re: What do mutt users use as a calendar/reminder program?
On Fri, May 25, 2007 at 08:48:58AM +0200, Sander Smeenk wrote: > Quoting Glen Barber ([EMAIL PROTECTED]): > > > There is a program (probably in your distributions package manager) > > called `remind`. There is also a great calendar program called > > `wyrd`. These two work great together. > > It's just too bad none of these textbased tools support CalDAV/WebDAV. > So it looks like remind is what people here like, plus one of its many front-ends, thanks all. -- Chris Green
