Re: Problem composing mail since switching to SuSE
* Kyle Knack <[EMAIL PROTECTED]> [2002-05-31 23:48:21 -0400]: > I recently switched my workstation from RedHat 7.1 to SuSE 7.3, and > now I'm having a funny problem when I compose mail. Mutt is no longer > asking me for a recipient or CC address when I hit 'm' to compose mail > (ask for CC is explicitly turned on in my config). My configuration is > fairly non-stock, but I can't seem to find any option related to this. > If anyone knows off the top of their head what might be causing it, > please let me know. If necessary, I can post all or some of my config > (fairly long). Thanks! 6.3.10 askbcc Type: boolean Default: no If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before editing an outgoing message. 6.3.11 askcc Type: boolean Default: no If set, Mutt will prompt you for carbon-copy (Cc) recipients before editing the body of an outgoing message. Nicolas
Re: attachment! - OE!
* Mehdi Jabal Ameli <[EMAIL PROTECTED]> [2002-06-01 00:46]:
> I want to send a file as attachment and sign whole message.
> I want to use mutt as command line.
> anybody can tell me how I do it?
we could tell you..
> X-Mailer: Microsoft Outlook Express 6.00.2600.
.. but this ain't the Outlook Express list.
> Mehdi Jabalameli _o/\ __o
> [EMAIL PROTECTED] _-< \_ / \ < \,
> ce.sharif.edu/~jabalameli __(_)/_(_)/\___(_) /_(_)__
ohmygod.
here - have some sigdashes: "-- "
You are welcome!
Sven
--
Q: Why use a signature dashes line ("sigdashes") for signatures?
A: Programs can then detect signature more easily. Then they can colorize
them and show them in a monospaced font ("ascii art"), or hide them from view,
delete them on replies, or save them to your sig archive.
Re: attachment! - OE!
* Sven Guckes <[EMAIL PROTECTED]> [2002-06-01 10:22 +0200]:
> * Mehdi Jabal Ameli <[EMAIL PROTECTED]> [2002-06-01 00:46]:
> > I want to send a file as attachment and sign whole message.
> > I want to use mutt as command line.
> > anybody can tell me how I do it?
>
> we could tell you..
>
> > X-Mailer: Microsoft Outlook Express 6.00.2600.
>
> .. but this ain't the Outlook Express list.
What, then? The inappropriate mutt advocacy list?
Gerhard
PS: I know M$ MUAs suck. Big time.
--
mail: gerhard bigfoot de registered Linux user #64239
web:http://www.cs.fhm.edu/~ifw00065/OpenPGP public key id AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9 3667 814B 9CAA AD24 C930
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))
FreeBSD compile errors
error on FreeBSD 4.5... 1.3.27 built ok on this system. no patches or anything... anyone else see an error like this, or should i send a message to mutt-dev? roland% ./configure --sysconfdir=/etc --enable-exact-address [configure works OK] roland% make [...] ./patchlist.sh < ./PATCHES > patchlist.c cd . && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status creating Makefile gcc -DPKGDATADIR=\"/usr/local/share/mutt\" -DSYSCONFDIR=\"/etc\" -DBINDIR=\"/usr/local/bin\" -DMUTTLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H=1 -I. -I. -Iintl -I./intl -I/usr/local/include -Wall -pedantic -g -O2 -c patchlist.c In file included from mutt.h:51, from patchlist.c:5: charset.h:39: syntax error before `ICONV_CONST' *** Error code 1 (line 39 in charset.ht is this:) size_t mutt_iconv (iconv_t, ICONV_CONST char **, size_t *, char **, size_t *, ICONV_CONST char **, const char *); current mutt -v: Mutt 1.3.27i (2002-01-22) Copyright (C) 1996-2001 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: FreeBSD 4.5-RELEASE (i386) [using ncurses 5.1] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK +USE_POP +USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK -HAVE_WC_FUNCS -HAVE_LANGINFO_CODESET -HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO -ISPELL SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the flea(1) utility. -- Will Yardley input: william < @ hq . newdream . net . >
Re: FreeBSD compile errors
On Sat, Jun 01, 2002 at 03:39:46AM -0700, Will Yardley wrote: > error on FreeBSD 4.5... 1.3.27 built ok on this system. > no patches or anything... anyone else see an error like this, or should > i send a message to mutt-dev? > roland% ./configure --sysconfdir=/etc --enable-exact-address > [configure works OK] > ./patchlist.sh < ./PATCHES > patchlist.c > cd . && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status > creating Makefile > gcc -DPKGDATADIR=\"/usr/local/share/mutt\" -DSYSCONFDIR=\"/etc\" > -DBINDIR=\"/usr/local/bin\" -DMUTTLOCALEDIR=\"/usr/local/share/locale\" > -DHAVE_CONFIG_H=1 -I. -I. -Iintl -I./intl -I/usr/local/include -Wall > -pedantic -g -O2 -c patchlist.c > In file included from mutt.h:51, > from patchlist.c:5: > charset.h:39: syntax error before `ICONV_CONST' > *** Error code 1 Make clean, then edit config.h and ensure #define HAVE_ICONV_H 1 #define HAVE_ICONV 1 #define HAVE_ICONV_T_DEF 1 are set, and all should work (assuming you do have libiconv installed) for some reason not picked up automagically Steve -- NetTek Ltd Flat 2, 43 Howitt Road, Belsize Park, London NW3 4LU, UK tel +44-(0)20 7483 1169 fax +44-(0)20 7483 2455 mob 07775 755503 SMS steve-pager (at) gbnet.net [body] gpg 1024D/468952DB 2001-09-19
Re: FreeBSD compile errors
* Will Yardley <[EMAIL PROTECTED]> [2002-06-01 03.39 -0700]: > error on FreeBSD 4.5... 1.3.27 built ok on this system. > > no patches or anything... anyone else see an error like this, or should > i send a message to mutt-dev? > > roland% ./configure --sysconfdir=/etc --enable-exact-address > [configure works OK] > > roland% make [...snip...] I take it you're not using the port; is this CVS-mutt you're fighting with? If so, try with gmake (GNU make) instead of make. HTH -- Martin Karlsson _ GPG/PGP public key: 0x9C924660 ASCII ribbon campaign ( ) -Respect for open standards X -No HTML, RTF, or M$ Word docs in e-mail / \ msg28458/pgp0.pgp Description: PGP signature
IMAP/charset problems?
I have problems with the charsets. I'm using "set charset=iso-8859-1" and "set allow_8bit", which people have reported to work for swedish characters. I still get the swedish characters åäö as ? though. Both in subject line and in the actual mail. Replying works since my editor has the support. I've gone through all kinds of testing and troubleshooting, and still nothing. I'm starting to wonder if it's iso-8859-1 over IMAP? I haven't tried the iconv thing, since it doesn't really seem related. Are there any other things I should try ? Thanks in advance, Patrik
Re: attachment! - OE!
* Gerhard Hring <[EMAIL PROTECTED]> [2002-06-01 08:59]: > > > X-Mailer: Microsoft Outlook Express 6.00.2600. > > .. but this ain't the Outlook Express list. > What, then? The inappropriate mutt advocacy list? if this was the inappropriate advocacy list then we *would* be giving hints for OE users. ;-) > PS: I know M$ MUAs suck. Big time. exactly. "All mailers suck..." Sven -- $ cat setup set auto_sign $ mutt -s "Subject" -a foo.bar \ -F setup [EMAIL PROTECTED]
Re: attachment! - OE!
* Sven Guckes <[EMAIL PROTECTED]> [2002-06-01 15:13 +0200]:
> $ cat setup
> set auto_sign
> $ mutt -s "Subject" -a foo.bar \
> -F setup [EMAIL PROTECTED]
AFAIC this requires an empty passphrase. It would be very nice if there
was an equivalent to ssh_agent for GNUpg. Is there one?
Gerhard
--
mail: gerhard bigfoot de registered Linux user #64239
web:http://www.cs.fhm.edu/~ifw00065/OpenPGP public key id AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9 3667 814B 9CAA AD24 C930
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))
Re: IMAP/charset problems?
Patrik, * Patrik Kullman <[EMAIL PROTECTED]> [2002-06-01 12.38 +0200]: > I have problems with the charsets. I'm using "set charset=iso-8859-1" > and "set allow_8bit", which people have reported to work for swedish > characters. I still get the swedish characters åäö as ? though. Both in > subject line and in the actual mail. Replying works since my editor has > the support. I've gone through all kinds of testing and troubleshooting, > and still nothing. > But you can write å,ä and ö without problem in an xterm and in other apps, correct? If not, what are your values for $LANG and $LC_CTYPE? As far as mutt is concerned, try setting 'send_charset' (in muttrc) to iso-8859-1; perhaps setting 'locale' (in muttrc) to iso-8859-1 will help. hoppas du får det att funka! -- Martin Karlsson _ GPG/PGP public key: 0x9C924660 ASCII ribbon campaign ( ) -Respect for open standards X -No HTML, RTF, or M$ Word docs in e-mail / \ msg28462/pgp0.pgp Description: PGP signature
Re: auto_sign and passphrase
* Gerhard Hring <[EMAIL PROTECTED]> [2002-06-01 13:34]: > > $ cat setup > > set auto_sign > > $ mutt -s "Subject" -a foo.bar \ > > -F setup [EMAIL PROTECTED] > AFAIC this requires an empty passphrase. oops - good point! > It would be very nice if there was an > equivalent to ssh_agent for GNUpg. > Is there one? dunno. but you'll have to decide whether you will trust your plaintext passphrase to some program - or whether you should do all signing youself by answering the passphrase prompt. Sven
Re: FreeBSD compile errors
On Sat, Jun 01, 2002 at 03:39:46 -0700, Will Yardley wrote: > error on FreeBSD 4.5... 1.3.27 built ok on this system. > > no patches or anything... anyone else see an error like this, or should > i send a message to mutt-dev? > > roland% ./configure --sysconfdir=/etc --enable-exact-address > [configure works OK] > iconv is not part of the base system and wont be found. I wonder why your configure didn't complain about a missing iconv. I always need --with-libiconv-prefix=/usr/local on FreeBSD. Which version are you talking about here? 1.4, 1.5.1, or cvs? Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED]
Re: FreeBSD compile errors
On Sat, Jun 01, 2002 at 13:05:44 +0200, Martin Karlsson wrote: > * Will Yardley <[EMAIL PROTECTED]> [2002-06-01 03.39 -0700]: >> error on FreeBSD 4.5... 1.3.27 built ok on this system. >> >> no patches or anything... anyone else see an error like this, or should >> i send a message to mutt-dev? >> >> roland% ./configure --sysconfdir=/etc --enable-exact-address >> [configure works OK] >> >> roland% make > [...snip...] > > I take it you're not using the port; is this CVS-mutt you're > fighting with? If so, try with gmake (GNU make) instead of make. > Nope, that's not needed. cvs-mutt builds here flawlessly with BSD-make (after changing the prepare-script to use autoconf213 and automake14, but that's a different story). Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED]
compile warnings
Just compiled 1.4, bunch of warnings. A couple are of concern, the year thing and why is mutt still using mktemp? Using gcc-3.1. In file included from mutt_menu.h:23, from addrbook.c:20: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from attach.c:21: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from browser.c:21: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from commands.c:22: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from compose.c:21: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from curs_lib.c:20: keymap.h:83: warning: array type has incomplete element type curs_lib.c: In function `mutt_format_string': curs_lib.c:561: warning: implicit declaration of function `wcwidth' In file included from mutt_menu.h:23, from curs_main.c:21: keymap.h:83: warning: array type has incomplete element type edit.c:36: warning: string length `623' is greater than the length `509' ISO C89 compilers are required to support In file included from mutt_menu.h:23, from enter.c:21: keymap.h:83: warning: array type has incomplete element type enter.c: In function `my_wcwidth': enter.c:37: warning: implicit declaration of function `wcwidth' init.c: In function `mutt_init': init.c:1860: warning: implicit declaration of function `getsid' In file included from handler.c:29: keymap.h:83: warning: array type has incomplete element type In file included from help.c:23: keymap.h:83: warning: array type has incomplete element type help.c: In function `print_macro': help.c:106: warning: implicit declaration of function `wcwidth' In file included from mutt_menu.h:23, In file included from mutt_menu.h:23, from keymap.c:20: keymap.h:83: warning: array type has incomplete element type main.c:50: warning: string length `1226' is greater than the length `509' ISO C89 compilers are required to support main.c: In function `mutt_usage': main.c:88: warning: string length `1250' is greater than the length `509' ISO C89 compilers are required to support In file included from mutt_menu.h:23, from menu.c:21: keymap.h:83: warning: array type has incomplete element type In file included from pager.c:22: keymap.h:83: warning: array type has incomplete element type pager.c: In function `format_line': pager.c:1126: warning: implicit declaration of function `wcwidth' In file included from mutt_menu.h:23, from postpone.c:21: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from query.c:20: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from recvattach.c:22: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from recvcmd.c:24: keymap.h:83: warning: array type has incomplete element type In file included from send.c:22: keymap.h:83: warning: array type has incomplete element type In file included from mutt_menu.h:23, from status.c:20: keymap.h:83: warning: array type has incomplete element type pgp.c: In function `pgp_current_time': pgp.c:143: warning: `%c' yields only last 2 digits of year in some locales In file included from mutt_menu.h:23, from pgpkey.c:25: keymap.h:83: warning: array type has incomplete element type muttlib.o: In function `mutt_adv_mktemp': muttlib.o(.text+0xb0): the use of `mktemp' is dangerous, better use `mkstemp' extlib.c: In function `mutt_exit': extlib.c:36: warning: implicit declaration of function `exit'
Re: FreeBSD compile errors
Hi, * Will Yardley [06/01/02 12:39:46 CEST] wrote: > error on FreeBSD 4.5... 1.3.27 built ok on this system. > no patches or anything... anyone else see an error like this, or should > i send a message to mutt-dev? > roland% ./configure --sysconfdir=/etc --enable-exact-address > [configure works OK] --enable-exact-address is broken and should not be used. See INSTALL -- although it doesn't make any real difference to me. > roland% make > [...] > charset.h:39: syntax error before `ICONV_CONST' > *** Error code 1 --with-libiconv-prefix=/usr/local. See the Makefile for any FreeBSD port of mutt. Cheers, Rocco
Re: FreeBSD compile errors
Hi, * Udo Schweigert [06/01/02 18:01:20 CEST] wrote: > On Sat, Jun 01, 2002 at 13:05:44 +0200, Martin Karlsson wrote: > > I take it you're not using the port; is this CVS-mutt > > you're fighting with? If so, try with gmake (GNU make) > > instead of make. > Nope, that's not needed. cvs-mutt builds here flawlessly > with BSD-make (after changing the prepare-script to use > autoconf213 and automake14, but that's a different story). And that story reads? What did/do you have to change? Never any problems here using: ,- | pdmef@klaus:~$ automake --version | automake (GNU automake) 1.4 `- ,- | pdmef@klaus:~$ autoconf --version | Autoconf version 2.13 `- ,- | pdmef@klaus:~$ uname -rms | FreeBSD 4.5-RELEASE-p5 i386 `- Cheers, Rocco
Re: FreeBSD compile errors
Udo Schweigert wrote: > On Sat, Jun 01, 2002 at 03:39:46 -0700, Will Yardley wrote: [ thanks also to steve for his message ] > > error on FreeBSD 4.5... 1.3.27 built ok on this system. > > > > no patches or anything... anyone else see an error like this, or should > > i send a message to mutt-dev? > > > > roland% ./configure --sysconfdir=/etc --enable-exact-address > > [configure works OK] > iconv is not part of the base system and wont be found. I wonder why your > configure didn't complain about a missing iconv. I always need > --with-libiconv-prefix=/usr/local on FreeBSD. > > Which version are you talking about here? 1.4, 1.5.1, or cvs? sorry - thought i wrote that. it was 1.4 i believe libiconv is installed, and i did a second install with some of the arguments that the port uses: CC="cc -I/usr/local/include" LDFLAGS=-L/usr/local/lib ./configure --enable-exact-address --enable-flock --disable-fcntl --with-libiconv-prefix=/usr/local and got the same error. i do get: checking for iconv... no, consider installing GNU libiconv configure: warning: Unable to find an iconv function. See INSTALL for help but configure doesn't fail as it used to. i just assumed that configure would whine if it couldn't find libiconv (it usually has) -- shouldn't a lack of libiconv be noticed in the configure process? i believe that GNU libiconv was installed from ports (and FreeBSD renames the lib and include files to make them start with a 'g' (ie giconv.h)). there's also i'm pretty sure i've just installed libiconv from source on some of my other FreeBSD machines - i can do that if it's easier. looking at the port, i'm pretty sure that it makes changes to deal with the weird naming of iconv: roland% grep giconv config.status s%@LIBICONV@%-lgiconv%g s%@INTLLIBS@%-lintl -lgiconv%g -- Will Yardley input: william < @ hq . newdream . net . >
Re: FreeBSD compile errors
Rocco Rutte wrote: > > > roland% ./configure --sysconfdir=/etc --enable-exact-address > > [configure works OK] > > --enable-exact-address is broken and should not be used. See > INSTALL -- although it doesn't make any real difference to > me. i've seen that, but no one has yet mentioned *why* it's supposedly broken (even when i specifically asked on the list). Works For Me (TM), and i prefer having my address like foo@bar (My Name) than the other way around. it supposedly takes up more memory but i haven't noticed much of an increase in system resources either. > > roland% make > > [...] > > charset.h:39: syntax error before `ICONV_CONST' > > *** Error code 1 > > --with-libiconv-prefix=/usr/local. See the Makefile for any > FreeBSD port of mutt. yeah tried that too see my other message. -- Will Yardley input: william < @ hq . newdream . net . >
Creating Folders/Mailboxes
I am trying Mutt and am having trouble figuring out how to create folders/mailboxes. I have found where you can create mailboxes by saving an e-mail and using a name that doesn't exist but how do I do a folder under other circumstances. Thanks. -- Michael Herman
Re: Creating Folders/Mailboxes
Moin, * Michael Herman <[EMAIL PROTECTED]> [02-06-01 21:04]: >I am trying Mutt and am having trouble figuring out how to create >folders/mailboxes. I have found where you can create mailboxes by >saving an e-mail and using a name that doesn't exist but how do I do >a folder under other circumstances. Just touch(1) them or let your MDA (Maildrop, Procmail, whatever) do the work. Thorsten -- Golly, I'd hate to have a kid like me! - Calvin
Re: Creating Folders/Mailboxes
Hi, * Michael Herman [06/01/02 21:04:21 CEST] wrote: > I am trying Mutt and am having trouble figuring out how to > create folders/mailboxes. All you have to do is: 'touch ~/Mail/foo' (or whatever your favorite location is) and add 'mailboxes =foo' if you've: 'set folder=~/Mail' in your ~/.muttrc. Done. > I have found where you can create mailboxes by saving an > e-mail and using a name that doesn't exist Understood what you mean. If you'd like to save a message, mutt checks for a save-hook first. If none found, the default folder name is equal to the localpart of the mail address. > but how do I do a folder under other circumstances. Not understood. Do you mean defining which mail should be saved to which folder? If so, look at save-hook in the manual -- if not, mind explaining your goal? Cheers, Rocco
Re: FreeBSD compile errors
Hi, * Will Yardley [06/01/02 20:27:28 CEST] wrote: [ errors building 1.4 on FreeBSD ] > sorry - thought i wrote that. it was 1.4 > i believe libiconv is installed, and i did a second install with > some of the arguments that the port uses: > CC="cc -I/usr/local/include" LDFLAGS=-L/usr/local/lib ./configure > --enable-exact-address --enable-flock --disable-fcntl > --with-libiconv-prefix=/usr/local > and got the same error. 1.5 builds fine here, but 1.4 makes problems. > i do get: > checking for iconv... no, consider installing GNU libiconv > configure: warning: Unable to find an iconv function. See INSTALL for help > but configure doesn't fail as it used to. Here too. That's stupid. Even more weired is this: ,- | pdmef@klaus:/tmp/mutt-1.4$ ./prepare --with-libiconv-prefix=/usr/local |--with-iconv=/usr/local | checking for iconv.h... yes | checking whether iconv.h defines iconv_t... yes | configure: warning: Unable to find an iconv function. See INSTALL for help | [...] | The mutt source code was successfully prepared. | Type make && make install to build and install mutt. `- ...which then runs into the same trouble. And /usr/local is correct: ,- | pdmef@klaus:~$ pkg_info -L iconv-2.0_1 | Information for iconv-2.0_1: | /usr/local/include/iconv.h | /usr/local/lib/libiconv.so | /usr/local/lib/libiconv.so.2 `- or... ,- | pdmef@klaus:~$ pkg_info -L libiconv-1.7_1 | Information for libiconv-1.7_1: | /usr/local/include/giconv.h | /usr/local/lib/libgiconv.so | /usr/local/lib/libgiconv.so.2 `- Cheers, Rocco
viewing 'inbox' as mail and not files?
I'm running the latest mutt (1.4i?). For some reason (?), the list of current mail messages was moved to 'inbox'. OK, I'm not sure why, but I can deal with that. When I switch my folder being viewed from default (spool) to 'inbox', mutt shows the messages as just a list of files (no, 'from:', 'subject:', etc.), not mail messages. How can I get mutt to display other folders as messages and not as files lists? Thank you. -- - Martin J. Brown, Jr. - - [EMAIL PROTECTED] - Public PGP Key ID: 0xDB184F7B keyserver: http://certserver.pgp.com/ msg28475/pgp0.pgp Description: PGP signature
Re: Problem composing mail since switching to SuSE
Nicolas,
As I stated, askcc is set to true in my configs, yet it's still not
prompting me. It's also not even asking for a subject before spawning
vi. The default behavior on SuSE (ie: using the .muttrc supplies with
the mutt rpm) -does- ask for this, just my configs from RH 7.1 (latest
mutt from updates) does not work. I'm attaching my configs as well (the
main sections anyway), should anyone want to look at them.
Kyle
* Nicolas Rachinsky <[EMAIL PROTECTED]> [020601 03:38]:
>Date: Sat, 1 Jun 2002 09:36:52 +0200
>From: Nicolas Rachinsky <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Cc: Kyle Knack <[EMAIL PROTECTED]>
>Subject: Re: Problem composing mail since switching to SuSE
>User-Agent: Mutt/1.3.28i
>
>* Kyle Knack <[EMAIL PROTECTED]> [2002-05-31 23:48:21 -0400]:
>> I recently switched my workstation from RedHat 7.1 to SuSE 7.3, and
>> now I'm having a funny problem when I compose mail. Mutt is no longer
>> asking me for a recipient or CC address when I hit 'm' to compose mail
>> (ask for CC is explicitly turned on in my config). My configuration is
>> fairly non-stock, but I can't seem to find any option related to this.
>> If anyone knows off the top of their head what might be causing it,
>> please let me know. If necessary, I can post all or some of my config
>> (fairly long). Thanks!
>
>6.3.10 askbcc
>
>Type: boolean
>
>Default: no
>
>If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients before
>editing an outgoing message.
>
>6.3.11 askcc
>
>Type: boolean
>
>Default: no
>
>If set, Mutt will prompt you for carbon-copy (Cc) recipients before editing the
>body of an outgoing message.
>
>
>Nicolas
>
--
Kyle Knack
([EMAIL PROTECTED])
# Mutt options
# Mail folder options
set copy = yes # Save copies of sent mail
set forward_quote = yes# Use > when forwarding
set indent_string = ">" # Sets indent string to >
set timeout=30
# Site options
set hostname = "only-linux.com" # Hostname of my e-mail
set realname = "Kyle Knack" # My name, of course
set signature = ~/.signature # My default signature
set attribution="* %n <%a> [%(%y%m%d %H:%M)]:"
# Alternate e-mail accounts
#set alternates =
([EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED])
set alternates = [EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED]
# Options I don't want on
unset confirmappend # Don't ask to save messages
unset mark_old# Don't mark unread as old
unset collapse_unread # Don't collapse unread threads
unset markers # Don't mark wrapped lines
unset metoo # Remove my address whrn replying
unset suspend # Don't stop on Ctrl-Z
unset wait_key# For autoview
# Options I DO want
set use_domain# Append my domain to domainless messages
set resolve # ?
set postpone = ask-yes# Prompt before postponing a message
set print = ask-yes # Prompt before printing
set delete = ask-yes # Prompt before deleting
set editor="vim +'/^$'" # Use vim
set header = yes # Copy header into reply
set copy = yes# ?
set nobeep# I hate beeps
set tmpdir = /tmp # Where to write temp stuff
set history = 20 # ?
set nomarkers # No wrapped markers
set menu_scroll # ?
set quit = yes# Quit on quit
set auto_tag
set beep_new # Beep on new mail only
set status_on_top # Keep that mutt info on the top
set mail_check = 5# Mail check interval
set delete = ask-yes # Prompt before deleting
set smart_wrap# Wrap lines ina good way
set tilde
set pager_context = 3
set pager = builtin # Use the builtin pager
set visual = vim # Visual editing with vim
set askcc # Ask for CC's
set hidden_host
set shell=/bin/bash
set include =yes
set abort_nosubject = no # Don't kill subjectless messages
set abort_unmodified = ask-yes # Don't kill bodyless messages
set help = yes
set print_command = "lpr -Plp"
set pager_index_lines = 8 # Split screen
set pager_stop
set check_new = yes # Check for new mail while running
set move = no # Don't ask to move read messages
set query_command="lbdbq '%s'"
set quote_regexp="^([ \t]*[|>:%}#])+"
set envelope_from
set edit_headers
set reverse_name
auto_view text/x-vcard
# Send Hooks
send-hook @dc-sage.org 'set signature = ~/.signature-dcsage'
send-hook @lists.isp-lists.com 'set signature = ~/.signature-isp'
send-hook @skynetweb.com 'my_hdr From: Kyle Knack <[EMAIL PROTECTED]>'
send-hook @skynetweb.com 'my_hdr Reply-To: [EMAIL PROTECTED]'
send-hook @affinity.com 'my_hdr From: Kyle Knack <[EMAIL PROTECTED]>'
send-hook @affinity.com 'my_hdr Reply-To: [EMAIL PROTECTED]'
# Folder Hooks
# folder-hook . 'set index_format="%4C %Z %{%b %d} %-15.15F (%4l) %s"'
#folder-hook . 'set index_format="%3C %Z %[%b %d %H:%M] - %-22.22L (%3l) %s"'
folder-hook . 'set sort = threads'
folder-hook . 'set sort_aux = re
Re: Problem composing mail since switching to SuSE
Hi, * Kyle Knack [2002-06-02 01:32:12 CEST] wrote: > As I stated, askcc is set to true in my configs, yet it's still not > prompting me. It's also not even asking for a subject before spawning > vi. Sounds like $fast_reply is set somewhere. > * Nicolas Rachinsky <[EMAIL PROTECTED]> [020601 03:38]: > >Date: Sat, 1 Jun 2002 09:36:52 +0200 > >From: Nicolas Rachinsky <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Cc: Kyle Knack <[EMAIL PROTECTED]> > >Subject: Re: Problem composing mail since switching to SuSE > >User-Agent: Mutt/1.3.28i Mind explaining why you quote this? IMHO it's completely useless... Cheers, Rocco
Re: Problem composing mail since switching to SuSE
I just explicitly unset fast_reply, to no avail. I checked through the system Muttrc (which I don't even know if it's reading or not since I have my own .muttrc), and it's not set in there either. As for the header copying, I'm honestly not sure why I had that on ;) I turned it off now. Kyle P.S. If I sounded a bit harsh in my prior response, I apologize, I did not intend it in that tone. As I read over it again, it kinda struck me that way. * Rocco Rutte <[EMAIL PROTECTED]> [020601 20:15]: >Hi, > >* Kyle Knack [2002-06-02 01:32:12 CEST] wrote: >> As I stated, askcc is set to true in my configs, yet it's still not >> prompting me. It's also not even asking for a subject before spawning >> vi. > >Sounds like $fast_reply is set somewhere. > >> * Nicolas Rachinsky <[EMAIL PROTECTED]> [020601 03:38]: >> >Date: Sat, 1 Jun 2002 09:36:52 +0200 >> >From: Nicolas Rachinsky <[EMAIL PROTECTED]> >> >To: [EMAIL PROTECTED] >> >Cc: Kyle Knack <[EMAIL PROTECTED]> >> >Subject: Re: Problem composing mail since switching to SuSE >> >User-Agent: Mutt/1.3.28i > >Mind explaining why you quote this? IMHO it's completely >useless... > >Cheers, Rocco > -- Kyle Knack ([EMAIL PROTECTED])
Re: Problem composing mail since switching to SuSE
And, as it always turns out, as soon as I sent that, I figured it out. Apparently mutt is still reading in values from /etc/Muttrc, and something in there is causing this to happen. The fast_reply option is turned off in both my config and the /etc/Muttrc. If anyone is bored and feels like looking at the /etc/Muttrc, I can send it. This brings up the real question to solve my problem - is there any way to make mutt ignore the /etc/Muttrc completely ? I tried 'mutt -F ~/.muttrc', which should be the default behavior with no options, but I get the same results. Thanks! Kyle * Kyle Knack <[EMAIL PROTECTED]> [020601 22:29]: >I just explicitly unset fast_reply, to no avail. I checked through the >system Muttrc (which I don't even know if it's reading or not since I >have my own .muttrc), and it's not set in there either. As for the >header copying, I'm honestly not sure why I had that on ;) I turned it >off now. > > >Kyle > >P.S. If I sounded a bit harsh in my prior response, I apologize, I did >not intend it in that tone. As I read over it again, it kinda struck me >that way. > >* Rocco Rutte <[EMAIL PROTECTED]> [020601 20:15]: >>Hi, >> >>* Kyle Knack [2002-06-02 01:32:12 CEST] wrote: >>> As I stated, askcc is set to true in my configs, yet it's still not >>> prompting me. It's also not even asking for a subject before spawning >>> vi. >> >>Sounds like $fast_reply is set somewhere. >> >>> * Nicolas Rachinsky <[EMAIL PROTECTED]> [020601 03:38]: >>> >Date: Sat, 1 Jun 2002 09:36:52 +0200 >>> >From: Nicolas Rachinsky <[EMAIL PROTECTED]> >>> >To: [EMAIL PROTECTED] >>> >Cc: Kyle Knack <[EMAIL PROTECTED]> >>> >Subject: Re: Problem composing mail since switching to SuSE >>> >User-Agent: Mutt/1.3.28i >> >>Mind explaining why you quote this? IMHO it's completely >>useless... >> >>Cheers, Rocco >> > >-- >Kyle Knack >([EMAIL PROTECTED]) -- Kyle Knack ([EMAIL PROTECTED])
Re: attachment! - OE!
Gerhard, et al -- ...and then Gerhard H?ring said... % % * Sven Guckes <[EMAIL PROTECTED]> [2002-06-01 15:13 +0200]: ... % > $ mutt -s "Subject" -a foo.bar \ % > -F setup [EMAIL PROTECTED] % % AFAIC this requires an empty passphrase. It would be very nice if there % was an equivalent to ssh_agent for GNUpg. Is there one? They're working on it, but it isn't ready yet. In the meantime, perhaps the --passphrase-fd switch would help. % % Gerhard HTH & HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28480/pgp0.pgp Description: PGP signature
Re: Problem composing mail since switching to SuSE
Kyle -- ...and then Kyle Knack said... % % And, as it always turns out, as soon as I sent that, I figured it out. Sort of, I think. % Apparently mutt is still reading in values from /etc/Muttrc, and % something in there is causing this to happen. The fast_reply option is % turned off in both my config and the /etc/Muttrc. If anyone is bored That doesn't make sense; why do you say that mutt is reading from Muttrc when you then say that fast_reply is turned off in Muttrc? % and feels like looking at the /etc/Muttrc, I can send it. This brings % up the real question to solve my problem - is there any way to make mutt % ignore the /etc/Muttrc completely ? I tried 'mutt -F ~/.muttrc', which Of course: [zero] [9:37pm] ~> mutt -h | grep -i muttrc -F specify an alternate muttrc file -ncauses Mutt not to read the system Muttrc % should be the default behavior with no options, but I get the same % results. Thanks! Do you have #set fast_reply or set nofast_reply in either of your muttrc files? It's unlikely, but perhaps it was compiled in as "on" by default. You mentioned your non-standard config; where did you get your mutt itself? % % Kyle % % % * Kyle Knack <[EMAIL PROTECTED]> [020601 22:29]: P.S. -- I really wish you would quit with the top-posting and non-trimming. Sven, do you have a .sig for this? ;-) HTH & HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28481/pgp0.pgp Description: PGP signature
Viewing HTML
I'm having weird problem. I currently have dillo defined in my .mailcap for handling text/html. When I try to view an html e-mail (NYT daily news, for example), the web page is displayed as the source HTML. This also happens with links. Mozilla works properly. Any ideas? Thanks. -- Michael Herman
Re: viewing 'inbox' as mail and not files?
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2002-06-01 21:12]: > I'm running the latest mutt (1.4i?). check your mail header: > User-Agent: Mutt/1.4i it's mutt 1.4 alright. > For some reason (?), the list of current mail messages was moved > to 'inbox'. OK, I'm not sure why, but I can deal with that. "set move" is a default. > When I switch my folder being viewed from default (spool) to > 'inbox', mutt shows the messages as just a list of files > (no, 'from:', 'subject:', etc.), not mail messages. > How can I get mutt to display other folders > as messages and not as files lists? "folders as messages"? huh? a "folder" is a *set* messages. it is thus *not* a message. please be more explicit! > -- > - Martin J. Brown, Jr. - > - [EMAIL PROTECTED] - > > Public PGP Key ID: 0xDB184F7B keyserver: http://certserver.pgp.com/ "Captain Whitespace, - is it you?" Sven
Re: Viewing HTML with "dillo"
* Michael Herman <[EMAIL PROTECTED]> [2002-06-02 02:44]: > I'm having weird problem. I currently have dillo defined in > my .mailcap for handling text/html. When I try to view an > html e-mail (NYT daily news, for example), the web page is > displayed as the source HTML. This also happens with links. > Mozilla works properly. Any ideas? um, share your configuration so we can see it? please? Sven ["what's a 'dillo' - and where can i get one?"] -- Sven Guckes [EMAIL PROTECTED] use "lists address" when you are *not* subscribed use "subscribe address" when you *are* subscribed -> http://www.math.fu-berlin.de/~guckes/mutt/setup.html
Re: Problem composing mail since switching to SuSE
* David T-G <[EMAIL PROTECTED]> [020601 22:44]: >Do you have > > #set fast_reply > >or > > set nofast_reply > >in either of your muttrc files? It's unlikely, but perhaps it was >compiled in as "on" by default. You mentioned your non-standard config; >where did you get your mutt itself? > It turned out to be 'set autoedit' in the Muttrc. I unset it now in mine and all is well. Thanks for the help. Kyle -- Kyle Knack ([EMAIL PROTECTED]) msg28485/pgp0.pgp Description: PGP signature
Re: [gpg] supplying passphrase on command line
* David Thorburn-Gundlach <[EMAIL PROTECTED]> [2002-06-02]: > Gerhard, et al -- > ...and then Gerhard H?ring said... > % * Sven Guckes <[EMAIL PROTECTED]>: > % > $ mutt -s "Subject" -a foo.bar \ > % > -F setup [EMAIL PROTECTED] > % > % AFAIC this requires an empty passphrase. It would be very nice if > % there was an equivalent to ssh_agent for GNUpg. Is there one? > They're working on it, but it isn't ready yet. > In the meantime, perhaps the --passphrase-fd switch would help. $ man gpg /-fd --passphrase-fd n Read the passphrase from file descriptor n. If you use 0 for n, the passphrase will be read from stdin. This can only be used if only one passphrase is supplied. Don't use this option if you can avoid it. interesting. example? Sven
Re: Problem composing mail since switching to SuSE
Hi, * David T-G [2002-06-02 04:40:58 CEST] wrote: > ...and then Kyle Knack said... > % Apparently mutt is still reading in values from /etc/Muttrc, and > % something in there is causing this to happen. The fast_reply option is > % turned off in both my config and the /etc/Muttrc. If anyone is bored Hey, I checked that, in your personal it didn't appear. Mutt also has built-in default values. If an option is not changed anywhere, the built-in default is used. So, in your case, 'turned off' would mean: unset fast_reply ...while it currently is unchanged and not turned off by the config files. > That doesn't make sense; why do you say that mutt is reading from Muttrc > when you then say that fast_reply is turned off in Muttrc? I don't understand it either. > Do you have > #set fast_reply > or > set nofast_reply > in either of your muttrc files? It's unlikely, but perhaps it was > compiled in as "on" by default. I've heard lots of things about heavily patched SuSe kernels (...and people suggesting not to use them) and SuSe at all. Allthough I never used it I would say that SuSe makes lots of changes to sources before they make a package out of it. In less words: It's SuSe and thus maybe not as unlikely as you think. > You mentioned your non-standard config; > where did you get your mutt itself? I think I mentioned it before, but the query-feature from the unstable branch (which didn't seem to make it in 1.4) is extremely usefull in such a case (since it dumps the real value mutt would use, either from init.h, Muttrc or ~/.muttrc). Cheers, Rocco
Re: Problem composing mail since switching to SuSE
* David Thorburn-Gundlach <[EMAIL PROTECTED]> [2002-06-02]: > % Apparently mutt is still reading in values from /etc/Muttrc, and > % something in there is causing this to happen. The fast_reply option is > % turned off in both my config and the /etc/Muttrc. If anyone is bored > That doesn't make sense; why do you say that mutt is reading from > Muttrc when you then say that fast_reply is turned off in Muttrc? he's probably looking for auto_edit.. > % and feels like looking at the /etc/Muttrc, I > % can send it. This brings up the real question > % to solve my problem - is there any way to make > % mutt ignore the /etc/Muttrc completely ? > mutt -h | grep -i muttrc >-F specify an alternate muttrc file >-ncauses Mutt not to read the system Muttrc --> mutt -n -F /dev/null we should tell users to start mutt like this when they *really* want to make sure to check mutt's *default* behaviour. > You mentioned your non-standard config; > where did you get your mutt itself? he probably got mutt from some linux distribution which mucks around with the setup files. *hrmpf* > P.S. I really wish you would quit with the top-posting and > non-trimming. Sven, do you have a .sig for this? ;-) you mean, "TOFU" (text oben, full-quote unten)? well, i sure do now... Sven -- TOFU lusers on mutt-users: Kyle Knack <[EMAIL PROTECTED]>
Re: Problem composing mail since switching to SuSE
* Rocco Rutte <[EMAIL PROTECTED]> [2002-06-02 03:14]: > I've heard lots of things about heavily patched SuSe kernels > (... and people suggesting not to use them) and SuSe at all. oh, SuSE... right. > Allthough I never used it I would say that SuSe makes lots > of changes to sources before they make a package out of it. > In less words: It's SuSe and thus > maybe not as unlikely as you think. "SuSE - the Linux Windows from Nuremberg" ;-) Sven [what would be a good signature now? ah - got it!] -- Sven Guckes [EMAIL PROTECTED] [Linux Distributions, 2000-07-28] LINUX? Which one? BestLinux, BlueCat Linux, Caldera OpenLinux, Conectiva Linux, Corel Linux, Debian GNU/Linux, DragonLinux, easyLinux, Elfstone Linux, Gentus Linux, Jurix Linux, L13Plus, Linux Antarctica, Linux by LibraNet, Linux Mandrake, LinuxOne, LinuxPPC, Linux Pro, LinuxWare, LuteLinux, MaxOS(TM), MkLinux, Platinum Linux, RedHat Linux, Redmond Linux, Rock Linux, RT-Linux, Slackware Linux, Stampede Linux, Storm Linux 2000, S.u.S.E. Linux, TurboLinux, Yellow Dog Linux, Yggdrasil Linux; SMALL Linux Distributions: Armed Linux, Coyote Linux, ChainSaw Linux, DLX Linux, DOS Linux, "File, Print & CD Server", hal91 Floppy Linux, Linux Embedded, Monkey Linux, muLinux, Peanut Linux, Phat Linux, ThinLinux, TINY Linux, tomsrtbt, Trustix Secure Linux, White Dwarf Linux, WinLinux 2000, WholeLinux, ZipHam.
Re: Problem composing mail since switching to SuSE
* Sven Guckes <[EMAIL PROTECTED]> [020601 23:22]: > >he probably got mutt from some linux distribution >which mucks around with the setup files. *hrmpf* > Actually, it's based off of Chris Gushue's .muttrc, with a fair amount of changes of my own. > >you mean, "TOFU" (text oben, full-quote unten)? >well, i sure do now... > >Sven > >-- >TOFU lusers on mutt-users: >Kyle Knack <[EMAIL PROTECTED]> > Point taken. -- Kyle Knack ([EMAIL PROTECTED])
Re: Viewing HTML with "dillo"
* Sven Guckes <[EMAIL PROTECTED]> [06-01-02 22:48]: > * Michael Herman <[EMAIL PROTECTED]> [2002-06-02 02:44]: > > I'm having weird problem. I currently have dillo defined in > > my .mailcap for handling text/html. When I try to view an > > html e-mail (NYT daily news, for example), the web page is > > displayed as the source HTML. This also happens with links. > > Mozilla works properly. Any ideas? > > um, share your configuration so we can see it? please? > > Sven ["what's a 'dillo' - and where can i get one?"] http://dillo.cipsga.org.br/ fast, verrry lite. -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
Re: Viewing HTML
On Sat, Jun 01, 2002 at 09:42:41PM -0500, Michael Herman wrote: > I'm having weird problem. I currently have dillo defined in my > .mailcap for handling text/html. When I try to view an html e-mail (NYT > daily news, for example), the web page is displayed as the source > HTML. This also happens with links. Mozilla works properly. Any > ideas? My guess is that your mailcap entry looks something like this: text/html; dillo -dump %s; copiousoutput Mutt does not add a .html extension to its temporary files by default, so dillo thinks it's reading a plain text file. There are two ways to fix this. Some browsers have an option like -force_html to force the browser to treat the input as HTML. The other way is to use the nametemplate mailcap field: text/html; dillo -dump %s; nametemplate=%s.html; copiousoutput Mozilla works properly because it assumes that everything is HTML unless specified otherwise. At least that's the way my Netscape Navigator seems to work. BTW, I assumed that you wanted this for in-line viewing of HTML e-mail, and I know nothing about dillo, so I assumed that it has a -dump option. HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: FreeBSD compile errors
On Sat, Jun 01, 2002 at 21:58:11 +0200, Rocco Rutte wrote: > Hi, > > * Will Yardley [06/01/02 20:27:28 CEST] wrote: > > [ errors building 1.4 on FreeBSD ] > >> sorry - thought i wrote that. it was 1.4 > >> i believe libiconv is installed, and i did a second install with >> some of the arguments that the port uses: > >> CC="cc -I/usr/local/include" LDFLAGS=-L/usr/local/lib ./configure >> --enable-exact-address --enable-flock --disable-fcntl >> --with-libiconv-prefix=/usr/local > >> and got the same error. > > 1.5 builds fine here, but 1.4 makes problems. > >> i do get: >> checking for iconv... no, consider installing GNU libiconv >> configure: warning: Unable to find an iconv function. See INSTALL for help > >> but configure doesn't fail as it used to. > > Here too. That's stupid. Even more weired is this: > > ,- || pdmef@klaus:/tmp/mutt-1.4$ ./prepare --with-libiconv-prefix=/usr/local |--with-iconv=/usr/local || checking for iconv.h... yes || checking whether iconv.h defines iconv_t... yes || configure: warning: Unable to find an iconv function. See INSTALL for help || [...] || The mutt source code was successfully prepared. || Type make && make install to build and install mutt. > `- > > ...which then runs into the same trouble. And /usr/local is > correct: > > ,- || pdmef@klaus:~$ pkg_info -L iconv-2.0_1 || Information for iconv-2.0_1: || /usr/local/include/iconv.h || /usr/local/lib/libiconv.so || /usr/local/lib/libiconv.so.2 > `- > The iconv port is now at 2.0_3 and no longer installs a libiconv.so, instead it is called libbiconv.so. This library is a way not standard and did not work for mutt-1.3.x. > or... > > ,- || pdmef@klaus:~$ pkg_info -L libiconv-1.7_1 || Information for libiconv-1.7_1: || /usr/local/include/giconv.h || /usr/local/lib/libgiconv.so || /usr/local/lib/libgiconv.so.2 > `- This library is not used by mutt, since it is called libgiconv.so and not libiconv.so. Also the libiconv port is at version 1.7.0.1 which fixes that. Please update both ports and try again. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED]
