Sending messages w/ attachments from the command prompt
To whom it may concern: So far I have been fairly impressed by your program. I'm a newbie to it, and I downloaded it for a specific reason, which so far I haven't been able to do. What I was hoping to be able to do was to send an e-mail from the command prompt with an attachment without any interaction with Mutt other than entering the original command from the prompt. The reason that I want to do it this way is so that I can include it in an automated script that runs on a daily basis. I originally tried doing this automation with Linux mail, but I was unable to send an attachment, and the text file that I was trying to send was too wide to fit in the e-mail window, and it would wrap and become unreadable if I tried to send it in the body of the message. So what I'm looking for is a way to send a message with a blank body and a text file attachment to 1 or more users in one command line entry without it prompting for me to verify who it is sent to, what the subject is, and finally having to enter "y" to send the message. If there is a way to do this, I would really appreciate you telling me how, and if not, what in the source code I might be able to hack to cause it to not prompt for the above mentioned items. Hopefully this e-mail made sense to you, and if not, feel free to contact me and have me clarify it more for you. Sincerely, Rayne Wolery -- Rayne Wolery Applications Programmer Zoot Enterprises Bozeman, MT (406)586-5050 x234
mailbox
Hi All, Forgive my trivial question. Where does mutt by default store the mailbox once it is looked upon? Cause i saved my own mailbox in /var/mail/root (logged on as root). And once i looked some mails, all was gone next time. I guess mutt saves it and then cleans up root? I dont want this. Further more.. will mutt have in the future apop support? What is better? apop or imap? Last question, how can i see what version i run of mutt? Sincerely, Reinoud.
mutt 1.0 compile problem
I just downloaded mutt 1.0 tonight and tried to compile it with: ./configure --with-slang --disable-nls make make install it gives up with a lot of errors about /usr/share/i18n/charmaps/ISO_8859-1,GL and the fact that keymap_defs.h is non-existant. After running configure at least once without --disable-nls, the make works. And then when I do make install, it gives up with this error: make[1]: Entering directory /home/nathan/src/mutt-1.0-us/m4' make[1]: @SHELL@: Command not found make[1]: *** [install-am] Error 127 make[1]: Leaving directory /home/nathan/src/mutt-1.0-us/m4' make: *** [install-recursive] Error 1 What am I doing wrong? Is there some subtle internationalization point that I'm missing here? -- /nathan | [EMAIL PROTECTED] | http://www.rose-hulman.edu/~froydnj/ Is this *idiocy*? Or something soIf the human brain were so simple brilliant that it just *looks*that we could understand it, we stupid? --Gary Kasparov would be so simple we couldn't.
Re: mailbox
* Reinoud Koornstra ([EMAIL PROTECTED]) [991116 09:21]: Hi All, Forgive my trivial question. Where does mutt by default store the mailbox once it is looked upon? Cause i saved my own mailbox in /var/mail/root (logged on as root). And once i looked some mails, all was gone next time. I guess mutt saves it and then cleans up root? My mutt definitely did not do this. Perhaps you had some sort of tricky race condition on the mailbox, or perhaps you deleted your mail? You might want to check the value of the variables 'move' and 'mbox', like so: :set ?move :set ?mbox from within mutt. mbox is the file your mail will be copied to, and 'move' controls whether it is so copied. By default, mutt will ask you, and the question will default to no. I dont want this. Furthermore.. will mutt have in the future apop support? Not sure.. maybe some developer types can pitch in here? (after some searching) it seems there's a patch to an older mutt version here, for apop. http://www-utheal.phys.s.u-tokyo.ac.jp/~ginga/mutt/mutt.html Maybe you can bring it forward to the current release? ...(read read) It seems there was some dissent back in the summertime about whether POP support should migrate out of mutt proper into external programs. Or not. See: http://www.egroups.com/MessagesPage?method=performActionlistName=mutt-devstart=5190search=apop What is better? apop or imap? APOP is a simple modification of POP3 which eliminates clear text passwords on the network. IMAP provides lots of other goodies. Whether simple is better, or complex is better is a matter of opinion. APOP is (relatively) easy to implement. IMAP is not. One sad fact is that both of these protocols are poorly supported in general. APOP simply isn't available with lots of software, and IMAP generally suffers from incomplete, shoddy, and/or insecure implementations. Take your pick. Last question, how can i see what version i run of mutt? user@hostname:~ mutt -v Mutt 1.0i (1999-10-22) Copyright (C) 1996-9 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 [...] Sincerely, Reinoud. Use vertical whitespace! -josh -- SuSE Inc. Tel: +1-510-628-3380 580 2nd Street, #210Fax: +1-510-628-3381 Oakland, CA 94607 Email: [EMAIL PROTECTED] USA WWW: http://www.suse.com
Re: Sending messages w/ attachments from the command prompt
On Mon, Nov 15 1999, at 17:06 -0700, Rayne Wolery wrote: So far I have been fairly impressed by your program. I'm a newbie to it, and I downloaded it for a specific reason, which so far I haven't been able to do. What I was hoping to be able to do was to send an e- mail from the command prompt with an attachment without any interaction with Mutt other than entering the original command from the prompt. The reason that I want to do it this way is so that I can include it in an automated script that runs on a daily basis. I originally tried doing this automation with Linux mail, but I was unable to send an attachment, and the text file that I was trying to send was too wide to fit in the e-mail window, and it would wrap and become unreadable if I tried to send it in the body of the message. So what I'm looking for is a way to send a message with a blank body and a text file attachment to 1 or more users in one command line entry without it prompting for me to verify who it is sent to, what the subject is, and finally having to enter "y" to send the message. If there is a way to do this, I would really appreciate you telling me how, and if not, what in the source code I might be able to hack to cause it to not prompt for the above mentioned items. Hopefully this e-mail made sense to you, and if not, feel free to contact me and have me clarify it more for you. Woo hoo, what an essay on a matter as simple as that. :-) $ mutt [EMAIL PROTECTED] -a FILE /dev/null Marco
Re: Sending messages w/ attachments from the command prompt
On 1999-11-15 17:06:45 -0700, Rayne Wolery wrote: So what I'm looking for is a way to send a message with a blank body and a text file attachment to 1 or more users in one command line entry without it prompting for me to verify who it is sent to, what the subject is, and finally having to enter "y" to send the message. $ mutt -s "silly subject" -a attach1 -a attach2 -a attach3 \ recip1 recip2 recip3 body.txt Obviously, body.txt is just a placehlder - you may use /dev/null instead, or you could do something like this: $ echo | mutt -s "..." -a .. recip1 ... -- http://www.guug.de/~roessler/
Re: Mutt silently ignores color definitions. I'd call it a bug!
I had many problems with colors when I first started using mutt. Who doesn't? :-) I was using some old version of ncurses then. So, you are saying, it's not mutt's fault at all? Doesn't mutt have any chance to check whether ncurses/slang accepted the defined colors? (Actually, even now I do not get precisely all the colours I want, both with slang 1.2.2 and ncurses 4.2.0. Maybe it's time to upgrade again?) Mine is linked against slang 1.3.9. Bye, Andy. -- E-Mail: [EMAIL PROTECTED] URL: http://andy.spiegl.de Finger [EMAIL PROTECTED] for my PGP key o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ Harrisberger's Fourth Law of the Lab: Experience is directly proportional to the amount of equipment ruined.
Re: mutt 1.0 compile problem
Nathan Froyd writes: I just downloaded mutt 1.0 tonight and tried to compile it with: ./configure --with-slang --disable-nls make make install it gives up with a lot of errors about /usr/share/i18n/charmaps/ISO_8859-1,GL and the fact that keymap_defs.h is non-existant. After running configure at If this happens, just make keymap_defs.h ; make least once without --disable-nls, the make works. And then when I do make install, it gives up with this error: make[1]: Entering directory /home/nathan/src/mutt-1.0-us/m4' make[1]: @SHELL@: Command not found make[1]: *** [install-am] Error 127 make[1]: Leaving directory /home/nathan/src/mutt-1.0-us/m4' make: *** [install-recursive] Error 1 You need to have the current versions of autoconf (2.13) and automake (1.4).
Re: mutt-users-digest V1 #244
From: [EMAIL PROTECTED]
John P. Looney [EMAIL PROTECTED] wrote on Mon, 15 Nov 1999:
I'm using 1.1.1 and 1.0, and both are giving me the same problems.
I had to read your message twice before I noticed the error in the
Subject line. I think I read somewhere some sort of hints for email
writing which included the suggestion "never assume the reader has read
the subject line". Seems to be true enough.
No worries. First two times I read your email address, my brain translated
it to "Mikka Hakkinen".
Enabling flock will likely not help with fcntl problems, even if I don't
know that much about file locking. You could try --disable-fcntl in
addition to --enable-flock. (That's how I compile my Mutt, anyway.)
On the other hand, depending on what file locking methods your MDA uses,
this could be dangerous and you could lose mail.
I stuck this in, and it worked fine!
Why is it trying to make locks, if I'm using IMAP ?
Because it likely is trying to access your default incoming spool
folder, which it thinks is local (/var/spool/mail/username or
something, probably).
Try setting $spoolfile in your .muttrc, eg
set spoolfile={gpo}inbox
Tried that, and it didn't seem to work. So I recompiled it with
--with-homespool={gpo}inbox and it works fine! Once I beat this
procmail/qmail thing into submission, I'll be a happy camper.
Kate
--
Microsoft. The best reason in the world to drink beer.
http://www.redbrick.dcu.ie/~valen
Problem running mutt in rxvt terminal window
I have a minor display problem when running mutt in an rxvt window that doesn't occur when running in a (Solaris) xterm window. It's basically a problem of reverse video highlighting not always getting turned off as it should. The most obvious occurrence is when you start mutt the bottom *two* lines of the screen are in reverse video instead of just the status line. I have tried changing the TERM variable (usually xterm, I've tried vt100 and vt102) with no effect and I've tried building mutt with different compilers to no effect. The problem occurs with both version 1.1 and with 1.1.1 on two different Solaris 2.6 systems. Strangely when I telnet into a remote Linux system from an rxvt terminal window and then run mutt (1.0) on the Linux system I *don't* get the problem. Does anyone have any ideas? Mutt reports as follows:- Mutt 1.1.1i (1999-11-08) Copyright (C) 1996-9 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: SunOS 5.6 Compile options: -DOMAIN -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP -USE_GSS +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr2/chris/share/mutt" SYSCONFDIR="/usr2/chris/etc" -ISPELL To contact the developers, please mail to [EMAIL PROTECTED]. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Compile problem with S-Lang
While trying to fathom out my problem in an rxvt I have been trying to compile with S-Lang but I get the following error druing compilation:- cc -DSHAREDIR=\"/usr2/chris/share/mutt\" -DSYSCONFDIR=\"/usr2/chris/etc\" -DBINDIR=\"/usr2/chris/bin\" -DHAVE_CONFIG_H=1 -I. -I/usr2/chris/include -I/usr/local/include -I/usr2/chris/mutt-1.1.1/intl -g -c curs_lib.c "curs_lib.c", line 258: syntax error before or at: SLcurses_wattrset cc: acomp failed for curs_lib.c I have slang-1.3.10 installed and it works OK for building slrn. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
mangling a from header
Hi there, I'm using mutt at work and want to set the 'From:' header to my private mail address when writing private mail. I already have this in my .muttrc: send-hook . "my_hdr From: [EMAIL PROTECTED]" send-hook "^ *[fF]vwm" "my_hdr From: [EMAIL PROTECTED]" send-hook "^ *[mM]utt" "my_hdr From: [EMAIL PROTECTED]" ... This efficiently takes care of mailing list mail. But now I'd like to do the same if I just 'r'eply to list mail not 'L'ist reply. Can this be done? Bye Dominik ^_^ -- Dominik Vogt, Agilent Technologies, Dept. BVS Herrenberger Str.130, 71034 Boeblingen, Germany phone: 07031/464-4596, fax: 07031/464-3883, [EMAIL PROTECTED]
IMAP folders - what commands are available using mutt 1.1.1
I am using the 1.1.1 development version of mutt (not here, this is 1.0) and want to know what I can do to IMAP folders with it, if anything! For example:- Can I create an IMAP folder (as opposed to a mail file)? Can I delete an IMAP folder or mailbox Can I move an IMAP folder (again, as opposed to mailbox)? -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Mutt silently ignores color definitions. I'd call it a bug!
On Tue, Nov 16, 1999 at 11:51:22AM +0100, Andy Spiegl wrote: I was using some old version of ncurses then. So, you are saying, it's not mutt's fault at all? It seemed so to me then. I tried creating a little program to test ncurses and discovered, that color change just after an attribute change (e.g. BOLD) was ignored by the library (or something like that; I don't quite remember). I think that was ncurses version 1.9.9 or something. However Mutt (due to its vast configurability) has the questionable honor of being first to expose various screen handling library bugs. Marius Gedminas -- I don't want to achieve immortality through my work. I want to achieve immortality through not dying. -- Woody Allen
Re: IMAP folders - what commands are available using mutt 1.1.1
On Tue, Nov 16, 1999 at 02:49:20PM -0500, Brendan Cully wrote: On Tuesday, 16 November 1999 at 16:13, Chris Green wrote: I am using the 1.1.1 development version of mutt (not here, this is 1.0) and want to know what I can do to IMAP folders with it, if anything! For example:- Can I create an IMAP folder (as opposed to a mail file)? no Can I delete an IMAP folder or mailbox no Can I move an IMAP folder (again, as opposed to mailbox)? no Oh dear! :-( I've started implementing create/delete, but it's not going to be aware of whether it can contain subfolders or messages right away. On some servers you probably get that for free by creating something like "Friends/" instead of "Friends", where "Friends/" contains subfolders and "Friends" contains messages. Yes, on the IMAP server I use at present the folders have a trailing '.' to differentiate them from the mailboxes. Are these actually separate entities on the IMAP server? It's rather confusing as the server I use doesn't itself actually acknowledge that hierarchical folders are possible but you can create them. I don't actually know whether MOVE is part of the IMAP RFC or not. You may have to tag all messages and copy them into a new folder for the forseeable future. Note that's not as slow as it sounds - it's all done server-side. That doesn't sound too difficult. The problem I'm facing at the moment is that the IMAP server (a free Web service) doesn't itself allow creation of a folder hierarchy using the Web interface and I can't create folders with mutt. Thus I need to use another mail program simply to create a folder hierarchy. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
[OT] dingus clicking in rxvt?
Where does one get the patches to make dingus clicking work in rxvt? --timball -- Send mail with subject "send pgp key" for public key. pub 1024R/CFF85605 1999-06-10 Timothy L. Ball [EMAIL PROTECTED] Key fingerprint = 8A 8E 64 D6 21 C0 90 29 9F D6 1E DC F8 18 CB CD
Re: IMAP folders - what commands are available using mutt 1.1.1
On Tuesday, 16 November 1999 at 20:02, Chris Green wrote: On Tue, Nov 16, 1999 at 02:49:20PM -0500, Brendan Cully wrote: I've started implementing create/delete, but it's not going to be aware of whether it can contain subfolders or messages right away. On some servers you probably get that for free by creating something like "Friends/" instead of "Friends", where "Friends/" contains subfolders and "Friends" contains messages. Yes, on the IMAP server I use at present the folders have a trailing '.' to differentiate them from the mailboxes. Are these actually separate entities on the IMAP server? It's rather confusing as the server I use doesn't itself actually acknowledge that hierarchical folders are possible but you can create them. They aren't separate entities, they're just listed twice because there are two operations availabe (descend and select), but only one "execute" key. This will be redone, hopefully soon. I've been busier than I thought lately... I don't actually know whether MOVE is part of the IMAP RFC or not. You may have to tag all messages and copy them into a new folder for the forseeable future. Note that's not as slow as it sounds - it's all done server-side. That doesn't sound too difficult. The problem I'm facing at the moment is that the IMAP server (a free Web service) doesn't itself allow creation of a folder hierarchy using the Web interface and I can't create folders with mutt. Thus I need to use another mail program simply to create a folder hierarchy. Note mutt does have a back door for creating mailboxes - save a message to a path that doesn't exist, and mutt will offer to create it for you. ie pick a random mailbox and copy a message to "=Newfolder/Newmx" and mutt should create it for you. -Brendan
Re: [OT] dingus clicking in rxvt?
On Tue, Nov 16, 1999 at 02:04:22PM -0600, Timothy Ball wrote: Where does one get the patches to make dingus clicking work in rxvt? What the is "dingus clicking"? I use rxvt so it *might* be useful to me! :-) -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: IMAP folders - what commands are available using mutt 1.1.1
On Tue, Nov 16, 1999 at 03:26:40PM -0500, Brendan Cully wrote: That doesn't sound too difficult. The problem I'm facing at the moment is that the IMAP server (a free Web service) doesn't itself allow creation of a folder hierarchy using the Web interface and I can't create folders with mutt. Thus I need to use another mail program simply to create a folder hierarchy. Note mutt does have a back door for creating mailboxes - save a message to a path that doesn't exist, and mutt will offer to create it for you. ie pick a random mailbox and copy a message to "=Newfolder/Newmx" and mutt should create it for you. Ah, thanks! Very useful. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: fcntl: No locks available (errno = 37)
Dan Lipofsky ([EMAIL PROTECTED]) said: I am using mutt-1.0pre3us on Red Hat 6.1 Linux. When ever I try to save a message to a file on a network file system I get fcntl: No locks available (errno = 37) Is lockd running? What sort of NFS server are you trying to save to? Bill
Re: fcntl: No locks available (errno = 37)
* Dan Lipofsky ([EMAIL PROTECTED]) [991116 21:53]: I am using mutt-1.0pre3us on Red Hat 6.1 Linux. When ever I try to save a message to a file on a network file system I get fcntl: No locks available (errno = 37) If the file does not exist it successfully creates it but leaves it length zero. If I try to save to a file on the local file system it works fine. Can anyone help me out here? - Dan I think the problem here lies with fcntl somehow wanting to make use of a lock daemon on the nfs file server. Someone correct me if wrong. Note that NFS lock daemons have a history of sucking, on pretty much all platforms. Userspace Linux NFS servers simply have _no_ lock daemon. The kernel nfs daemon has a lock daemon, if you run it, though I'm not sure it's perfect. As a result, I pretty much always build mutt with --disable-fcntl --enable-flock on linux. I don't know what I'm missing, but at least it works. -josh -- SuSE Inc. Tel: +1-510-628-3380 580 2nd Street, #210Fax: +1-510-628-3381 Oakland, CA 94607 Email: [EMAIL PROTECTED] USA WWW: http://www.suse.com
Re: fcntl: No locks available (errno = 37)
On Tue, Nov 16, 1999 at 08:07:30PM -0200, Lalo Martins wrote: ditto Ok, ``me too''s suck :-) more info: Copying to falcon/teste...lockd: failed to monitor 192.168.0.76 fcntl: No available locks (errno = 79) So it is a lockd issue. I don't run a lockd. (Debian, mutt 1.0pre3-1.2 - newer ones didn't compile on the sparc port, it seems, but the version in the PCs gives the same error) []s, |alo + -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:[EMAIL PROTECTED] pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness -- http://zope.gf.com.br/BroDar
Re: fcntl: No locks available (errno = 37)
Oh, one more tidbit: I _can_ save attachments. Go figure. []s, |alo + -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:[EMAIL PROTECTED] pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness -- http://zope.gf.com.br/BroDar
Re: Sending messages w/ attachments from the command prompt
Rayne Wolery [EMAIL PROTECTED] wrote: What I was hoping to be able to do was to send an e-mail from the command prompt with an attachment without any interaction Sounds like you want "mpack". That's what it does. Aris Mulyono [EMAIL PROTECTED] wrote: Can we specify a specific MIME type too for each attachment? Mutt finds the MIME type by searching your .mime.types file for the file extension. Mpack lets you specify it on the command line. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Sending messages w/ attachments from the command prompt
Mikko Hänninen [EMAIL PROTECTED] wrote: wizard@chamber:~ mutt wizard -a /dev/null -s foo /dev/null stty: standard input: Not a typewriter stty: standard input: Not a typewriter stty: standard input: Not a typewriter When Mutt spawns an external command (such as "sendmail"), it uses your exec-shell (/bin/sh? /bin/bash?) to launch that command. Some shells run startup sequences, based on environment variables such as $ENV. Bash runs .bashrc. You may be running an stty command from in one of these. Or several, perhaps, since you see it multiple times. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: fcntl: No locks available (errno = 37)
Lalo Martins [EMAIL PROTECTED] wrote: Oh, one more tidbit: I _can_ save attachments. Go figure. That's because attachments are saved to *files*, while messages are saved to *folders*. So attachments don't require any locking (unless you're saving a message/rfc822 type, which is a message, but now it's getting confusing). Basically, Mutt wants to fcntl-lock the folder, to be safe against someone else writing to it. Your NFS client is not running the necessary daemon to coordinate that lock with the server, so it fails, and Mutt gives up rather than possibly trash your mailbox. If you are *certain* that every mail-handling program at your site uses the same dot-locking mechanism, you can reconfigure Mutt with --disable-fcntl, and then you won't have this problem. But if you're wrong, and there is some program that does try to perform fcntl-locks as the only method to prevent synchronization problems, then the two programs can collide and trash the folder if they access it at the same time. Best is to fix the locking problem, as you may have other programs that want to lock files, too. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: mangling a from header
Dominik Vogt [EMAIL PROTECTED] wrote: send-hook . "my_hdr From: [EMAIL PROTECTED]" send-hook "^ *[fF]vwm" "my_hdr From: [EMAIL PROTECTED]" send-hook "^ *[mM]utt" "my_hdr From: [EMAIL PROTECTED]" You seem to have a few minor nits that I'd like to pick at, here... The first is that you seem to assume that Mutt can only use a simple regular expression here. Actually, Mutt expects a "pattern", of which there is a section in the manual. You could do better to specify which part of the address you're matching on, such as the From:, To:, or Cc:. The default, if you give a simple expression, is to match all three. send-hook '~C ^fvwm' "my_hdr From: ..." might be closer to the effect you're looking for. The second is that you are assuming that the pattern matches the entire header line, so that you need to match some whitespace coming before the address. This is not true; Mutt only matches on the actual address, when you use an address pattern. So, if your pattern is '~t ^fvwm', and the header says "To: Those Guys that Do FVWM [EMAIL PROTECTED]", the pattern will match, because the only string that Mutt will attempt a match on is "[EMAIL PROTECTED]"; it will ignore the full-name portion. The third is that you need to force Mutt to look for upper and lower case characters with your pattern. This is not true; Mutt will match the pattern case-insensitively, if your pattern contains no upper-case characters. So you should be able to use these instead: send-hook ."my_hdr From: [EMAIL PROTECTED]" send-hook '~C ^fvwm' "my_hdr From: [EMAIL PROTECTED]" send-hook '~C ^mutt' "my_hdr From: [EMAIL PROTECTED]" These ought to work, whether you are replying, or list-replying, as long as one of the recipients (To or Cc) matches "fvwm" or "mutt". Of course, if they match both, you will get the latter as your From: header. That's how hooks work. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
forward with attached files
sniors, how to forward mail with its attached files? thanks reed
