Re: [OT] html email
Nick Wilson [EMAIL PROTECTED] asked:
Anyone got the equivelant Procmail recipe for dumping mail if
it's text/html ot not addressed to you? I use this to get the
latter:
:0:
* !(^[EMAIL PROTECTED])
~/Mail/Other/suspect
Which works fine, adding the ability to weed out html would
make it much better.
Actually, I think I'd use one recipe to catch the html messages
first, then dump the messages not explicitly addressed to me
last. Perhaps something like this:
# BEGIN recipe
MAILDIR=${HOME}/Mail
:0 i:
* ^content-type: text\/html
| formail -i X-Spam-reject-reason: HTML-only \
${MAILDIR}/IN-spam
# The following needs to be the last recipe. It dumps anything
# remaining that specifically mentions my addresses into the mail
# spool, and then anything else into the $MAILDIR/IN-spam
# mailbox.
ME='(some happy regexp describing my email addresses)'
:0:
* $ ^TO_$ME
$ORGMAIL
DEFAULT=${MAILDIR}/IN-spam
:0 f:
| formail -i X-Spam-reject-reason: not explicitly addressed to me
# END recipe (and END of ~/.procmailrc file)
-- Mr. Wade
--
Once we've got the bugs ironed out, we'll be running on flat
bugs.
Re: my-hdr entry disappears after editing headers
Andreas Herceg wrote: OK, I did not know that X-Label is that common. Now I thought of just defining 'X-Coprija: coprija'. Now I would like to know if this would be against some standard which I do not know. Will Yardley [EMAIL PROTECTED] replied: my understanding is that X headers are pretty much up for grabs. i say if someone's going to be retarded about you using 'X-Label', screw 'em. it's their problem, not yours (and they can easily edit your message in mutt and remove the offending header, or they can strip it out with procmail if it really bothers them that much). I tend to agree with Will, (even if I don't share his somewhat confrontational attitude.) Header feilds are meant to be useful and informative; although, I sometimes think that some users let them get a bit out of hand. In any case, relying on a user-defined-field for any significant purpose is a bit fool-hardy. An excerpt from RFC #822 Standard for the format of ARPA Internet text messages: *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* 4.7.5 USER-DEFINED-FIELD Individual users of network mail are free to define and use additional header fields. Such fields must have names which are not already used in the current specification or in any definitions of extension-fields, and the overall syntax of these user-defined-fields must conform to this specification's rules for delimiting and folding fields. Due to the extension-field publishing process, the name of a user-defined-field may be pre-empted Note: The prefatory string X- will never be used in the names of Extension-fields. This provides user-defined fields with a protected set of names. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* -- Mr. Wade -- Whip me. Beat me. Make me maintain AIX.
Re: mutt-1.3.?
Lukasz Zamel [EMAIL PROTECTED] wrote: Where I can download versions 1.3.? from? I've checked www.mutt.org and they sey that 1.2.5i is the latest version, but few users on this list use this versions. Have you checked the devel subdirectories at the FTP sites? ftp://ftp.mutt.org/pub/mutt/devel -- Linux: The Choice of the GNU Generation
Re: Reverse search
Jean-Michel Kelbert [EMAIL PROTECTED] asked: How can I do a reverse search in a folder (like Inbox or outgoing) like in vim ? Lawrence Mitchell ([EMAIL PROTECTED]) replied: This is in the help section in mut (got at by pressing ?), a search fro search yields: esc/ backwards search Jean-Michel Kelbert [EMAIL PROTECTED] wrote: Yes but I like to know how I could make a search on the personn how send my the mail ! Jean-Michel, perhaps reading the section of the manual about Patterns would benefit you. -- Linux: The Choice of the GNU Generation
Re: mutt 1.2.5 and noatime filesystems
Matteo [EMAIL PROTECTED] wrote: I'm using mutt 1.2.5 on FreeBSD 4.3-STABLE box. Today I've mounted /var partition with options noatime. I rebooted, but later mutt doesn't work. Each time that I exit from a Mailbox and press TAB+TAB to check for new messages, mutt notifies that there are new messages in mailboxes that I've check before. Then I enter in one of this mailboxes, but there aren't new mex. I've remounted /var without noatime and mutt works fine... As I understand it, Mutt detects new mail by comparing the mailbox's last modification time to the last access time. If you mount the partition with noatime, you've eliminated the access time, so how can you expect Mutt to detect new mail properly? -- Linux: The Choice of the GNU Generation
Re: Simple mutt question ... I think?
On Mon, Jul 16, 2001, Chris Fuchs wrote: on Wed,11 Jul 2001, Mr. Wade wrote: Anthony Green [EMAIL PROTECTED] wrote: I would just like to find out if its possible in mutt to setup so that if you use a signature file, the signature is added to the top of the email, rather than the bottom of the email below the persons original email when replying. I have my signature set in my .muttrc as : set signature=~/signature # file which contains my signature One solution would be to do something like this in your ~/.muttrc file: set attribution=-- \nAnthony.\[EMAIL PROTECTED]\n\nOn %d, %n wrote: macro index r :unset signatureenterreply reply to a message *snip* Maybe something like this will effect what you're trying to accomplish. Unfortunately this doesn't seem to make allowance for prepending a randomly generated signature file using a script. At least backtics only seem to work up to the first \n. Suppose the attribution is this: set attribution=-- \n `script` \n\nOn %d, %n wrote: And the script generates Anthony\nGreen, then only --\n Anthony \n\nOn %d, %n wrote: shows up in the output... unless there is another way of doing this. Yeah,... only the first line of output from the script in backtics. From the manual: Note that since initialization files are line oriented, only the first line of output from the Unix command will be substituted. Hrmm,... there's probably a way of getting the functionality you desire, but I'm not sure how to go about it. Anyway, since the whole idea tends to encourage top-replying, which is pretty snoopy, I find the whole idea to be somewhat pointless and even counter-productive. -- Linux: The Choice of the GNU Generation
Re: Simple mutt question ... I think?
Anthony Green [EMAIL PROTECTED] wrote: I would just like to find out if its possible in mutt to setup so that if you use a signature file, the signature is added to the top of the email, rather than the bottom of the email below the persons original email when replying. I have my signature set in my .muttrc as : set signature=~/signature # file which contains my signature One solution would be to do something like this in your ~/.muttrc file: set attribution=-- \nAnthony.\[EMAIL PROTECTED]\n\nOn %d, %n wrote: macro index m :set signatureentermail compose a new mail message macro pager m :set signatureentermail compose a new mail message macro attach m :set signatureentermail compose a new mail message macro index r :unset signatureenterreply reply to a message macro pager r :unset signatureenterreply reply to a message macro attach r :unset signatureenterreply reply to a message macro index g :unset signatureentergroup-reply reply to all recipients macro pager g :unset signatureentergroup-reply reply to all recipients macro attach g :unset signatureentergroup-reply reply to all recipients macro index L :unset signatureenterlist-reply \ reply to specified mailing list macro pager L :unset signatureenterlist-reply \ reply to specified mailing list macro attach L :unset signatureenterlist-reply \ reply to specified mailing list Maybe something like this will effect what you're trying to accomplish. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: timestamp of mailbox file is not updated
I have also noticed that mbox mailbox files' modification times seem not to be updated when messages are deleted. Whenever a message is added, the file's modification time is updated, though. Unfortunately, I have no idea why. Andy Spiegl [EMAIL PROTECTED] wrote: Hi Mutters, I am gradually getting concerned that no one is caring about this bug (if it's a bug and not a strange feature). Please let me know if there is something I can do to change this strange behaviur of mutt. I can't find anything in the manual and FAQ. Hope I didn't overlook anything. The problem is that my syncronizing software (unison) depends on the timestamp to work correctly. Here is my mail again, just to be sure: I found it very strange to find out that mutt sometimes doesn't update the timestamp of a mailbox file. Here's an example: hamster:~l testmailbox -rw---1 spiegl users 26537 Feb 20 20:57 testmailbox hamster:~grep ^Status: testmailbox zsh: 3666 exit 1 grep -i ^Status testmailbox hamster:~mutt -f testmailbox 4 kept, 0 deleted. hamster:~grep ^Status: testmailbox Status: RO Status: RO Status: O Status: O hamster:~l testmailbox -rw---1 spiegl users 26579 Feb 20 20:57 testmailbox hamster:~mutt -f testmailbox 2 kept, 2 deleted. hamster:~l testmailbox -rw---1 spiegl users 18153 Feb 20 20:57 testmailbox -- Linux: The Choice of the GNU Generation
Re: Defaulting to thread mode
Sam Carleton [EMAIL PROTECTED] wrote: A: Every time I bring up mutt, I am doing a o -- t to get into thread mode. Is there some way I can default the mode to thread mode? set sort=threads B: I am using qmail and ~/Maildir/. Every time I exit mutt, I am prompted with: Move read messages to ~/mbox? ([n]/y): Is there any way to suppress this message? set move=no Sam -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: sourcing different config files
Will Yardley [EMAIL PROTECTED] asked: Is it possible to source different mutt config files somehow based on a shell script type thingie? Using a command line argument, you can specify a different initialization file to read instead of the ~/.muttrc file. For example, to start Mutt using ~/.muttrc.home as the initialization file instead of /.muttrc, you could use the following: mutt -F ~/.muttrc.home Perhaps using this with some nifty scripting or aliasing will do what you want. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Multiple IMAP Servers
Ricardo SIGNES [EMAIL PROTECTED] wrote:
I switched from Pine to mutt nearly a year ago, now, and
there's still only one thing I miss -- multiple IMAP servers.
I have three or four IMAP servers I'd like to deal with, and I
don't consider it an option to just c{servername}FOLDER all the
time. Is there a simple way to define multiple switchable IMAP
servers?
Could I even fake this with multiple .muttrc files that I could
load during a session?
You might try defining folder-hooks that change the relevant
variables as needed.
--
Linux: The Choice of the GNU Generation
Re: How many mailboxes can one set?
Marco Fioretti wrote: I have been happily using Mutt 1.0.1i (2000-01-18) on RH 6.2. Everything was fine until this morning, when I decided to put all the messages from two lists in two new separate mailboxes,. I set up procmail to do it, and that part works perfectly. Mutt however, doesn't tell me that there is new mail in THOSE new mailboxes. More specifically, I changed muttrc from: mailboxes ! =IN.list1 =IN.list2 =IN.list3 =IN.list4 =IN.list5 to: mailboxes ! =IN.list1 =IN.list2 =IN.list3 =IN.list4 =IN.list5 =IN.list6 = IN.list7 In other words, procmail puts all the right new messages in IN.list6 and IN.list7, but mutt doesn't signal any new messages in them. Previous mailboxes (list1 to list5) still work OK, though. Is there anything like a maximum line length allowed in muttrc or what? I don't know about a line length limit, but you might want to use something like this: mailboxes ! `echo $HOME/Mail/IN*` I use something similar and currently have 18 mailboxes declared without problems. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: * when sorting msgs by threads
Gilles CHAUVIN wrote: Just a little question. When I sort my mails by threads, some replies appears with a * instead of - in the pager. I didn't find informations about this in the Mutt's doc. Can someone tell me what does it means ? As I understand it: If the $strict_threads variable is set, threading will only be done according to the In-Reply-To: and References: headers. When $strict_threads is unset, (which it is by default,) threading will also be done according to the Subject: header. The * type of thread tree indicators are to indicate that the message is a pseudo thread due to its subject, rather than an element of a strict thread due to the other headers. A message sorted into a thread that contains a In-Reply-To: and/or a References: header for the thread will have a - type of thread tree indicator. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Fcc: = folder where original message is when replying ?
Lukas Ruf wrote: is there a possibility to configure mutt-1.x the way that fcc: get's automatigally set to the folder where the message is located to that I reply on ? [...] I hope this explains my problem. If this issue has already been addressed somewhere, could you give me a hint under which keyword I should run a search ? Read the portions of the manual regarding the fcc-hook directive. That should help. -- Linux: The Choice of the GNU Generation
Re: dot files
Igor Pruchanskiy wrote: I am sure this question was asked before, but i am not able to find anthing about this How can i view dotfiles in mutt's file browser ? The $mask variable determines which files will be displayed in the file browser. The default value is !^\.[^.], which masks dotfiles. Setting it to . should enable all files to be shown. In my ~/.muttrc file, I have: set mask=. # A regexp defining which files will be shown in the # file browser, (always a case-sensitive match). I hope this is what you meant and it helps. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: MUTT 1.2.5 and RFC 1891
[EMAIL PROTECTED] wrote: Hi, could some1 tell me if Mutt 1.2.5 supports RFC 1891 SMTP Service Extension for Delivery Status Notifications? Tnx a lot Mutt's support for Delivery Status Notifications is outlined in section 4.9 of the manual. 4.9. Delivery Status Notification (DSN) Support In short, the $dsn_notify and $dsn_return variables are employed, so checking those sections of the manual should help. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Word Wrap
Suresh Ramasubramanian wrote: Mr. Wade [mutt-users] 29/05/01 23:32 -0400: I use vim also. Mine will do the word wrap, as you describe, but the adding of new quote marks... how do you accomplish that? If there's a single quotemark at the start of a long line and you wrap it, the entire paragraph is wrapped. Ah, I see. Thanks very much. After a bit of RTFM-ing I dicovered I had been using the default vim formatoptions of tcq, which doesn't behave in the way described. Adding an r, i.e. set fo=tcrq solved the problem. That's much more conveninent than what I had before! -- Linux: The Choice of the GNU Generation
Re: Enabling a 2nd aspell language in compose
Alexander Skwar wrote: So sprach Mr. Wade am Sun, May 20, 2001 at 06:47:44PM -0400: You shouldn't need to do that. Mutt should call whatever you specify by the $ispell variable with the -x switch and the temporary file name on the command line for you. Yeah, and that works very fine, indeed. I've set ispell=aspell -d deutsch -x -c in my muttrc. But, I'd also like to check english texts for spleing errors. So I'd like to have a key which would invoke aspell -d american -x -c How would I go about it? Have you tried something like the following? macro compose i 'enter-commandset ispell=aspell -d deutsch -c \ enterispell' 'Deutsch' macro compose I 'enter-commandset ispell=aspell -d american -c \ enterispell' 'American' Note that the -x switch ought not need to be specified. Mutt alreay includes it on the command line when it calls whatever you specified by the $ispell variable. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Enabling a 2nd aspell language in compose
Alexander Skwar wrote: So sprach Wilhelm Wienemann am Sun, May 20, 2001 at 07:38:53PM +0200: Maybe this will also work for you: macro compose i :set ispell=ispell -T latin1 -p $HOME/.ispell_english macro compose I :set ispell=/path_to_your_aspell\n aspell-american Hmm, I don't understand - what should I put in for 'path_to_your_aspell'? I was looking for a way to give mutt some kind of 'special character', which it would replace by the name of the temporary file. Like (made up): aspell -d deutsch -x -c $1 And when this is executed, mutt would run: aspell -d deutsch -x -c /home/askwar/tmp/mutt-teich-1928-2 so, it would replace '$1' by '/home/askwar/tmp/mutt-teich-1928-2', if '/home/askwar/tmp/mutt-teich-1928-2' is the name of the temporary file with the message body. You shouldn't need to do that. Mutt should call whatever you specify by the $ispell variable with the -x switch and the temporary file name on the command line for you. -- Linux: The Choice of the GNU Generation
Re: Word Wrap
Larry Hignight wrote: I'm not sure how I missed this in the Mutt manual and some online tutorials, but I have some people on another mail list complaining that my email isn't wrapping properly. I am using vim as my editor. Which needs to be configured to setup wrapping at 72? Is it in one of the vim files or the .muttrc? Either, actually! Since you can specify it on the command line, you could use something like this in your ~/.muttrc file: set editor='vim -c set tw=72' There are many other things that you could also specify, but this is the one you mentioned, so... Good luck! =o) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Signature
Masand, Manish wrote: i have removed the quotes... but the problem remains is this problem becoz i am firing mutt on Unix by the following command mutt -a xyz.txt [EMAIL PROTECTED] abc.txt pls advise Manish Masand Hmm... it seems that the contents of the file specified by $signature are NOT appended to all outgoing messages, contrary to the documentation. If the text of the message is taken from a file on the commandline or if mailx emulation is being employed, the signature is omitted. The signature should be appended in the edit buffer when the editor is invoked, though. Perhaps the docs need to be corrected. From the docs: 6.3.180. signature Type: path Default: ~/.signature Specifies the filename of your signature, which is appended to all outgoing messages. If the filename ends with a pipe (``|''), it is assumed that filename is a shell command and input should be read from its stdout. -- Linux: The Choice of the GNU Generation
Re: Signature
darren chamberlain wrote: Masand, Manish ([EMAIL PROTECTED]) said something to this effect on 05/17/2001: any solution to this problem? anyone? Yeah: mutt -a xyz.txt [EMAIL PROTECTED] (cat abc.txt; echo --; cat ~/.signature) If you're going to do it that way, at least include the space after the dashes! :o) $ mutt -a xyz.txt [EMAIL PROTECTED] \ (cat abc.txt; echo -- ; cat ~/.signature) -- Linux: The Choice of the GNU Generation
Re: request for SMTP integration
Thomas Roessler wrote: Pine also includes a crappy editor (pico - which is nevertheless used by some people in order to ruin their configuration files), and a full-blown file manager (pilot, if I recall this correctly). Just don't quote it as an example. (OK, we have a directory browser, too, and a tight integration between editor and mailer has a few pros ;-)) Mutt also has a built-in editor, crappy or otherwise, not that I make a habit of using it very often. unset $editor or specify -x on the commandline, not that I make a practice of using it very often. :o) -- Linux: The Choice of the GNU Generation
Re: Delete and jump to next unread
Jan Chrillesen asked: Is there a way to map a key to delete current mail and jump to next unread? Tab+d won't work, since I don't know if the next message is unread. You could specify a macro to accomplish this. e.g., macro index \cx 'delete-messagenext-new' macro pager \cx 'delete-messagenext-new' This will cause Ctrl-x to do what you appear to be asking in both the index and the pager. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Marking multiple messages as read
Jeroen Valcke wrote: I want to mark multiple msgs as read. I have some mailing lists and I don't want to read all msgs. How can I mark these as read. It is possible to tag them all. But what then. Ctl-R (Mark Thread as read) doesn't work on all the tagged msg only the selected msg Thanks. After tagging the messages, you have to use the tag-prefix operator to apply the subsequent command to tagged messages. The tag-prefix operator is bound to the semicolon (;) by default. The function you ant to apply to the tagged messages is the clear-flag function, bound to W by default. After tagging the messages, typing ;Wn then pressing the enter kay may do what you want. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Marking multiple messages as read
Jeroen Valcke wrote: Hey, I want to mark multiple msgs as read. I have some mailing lists and I don't want to read all msgs. How can I mark these as read. It is possible to tag them all. But what then. Ctl-R (Mark Thread as read) doesn't work on all the tagged msg only the selected msg Thanks. -Jeroen- Please fix your Mail-Followup-To: header. -- Linux: The Choice of the GNU Generation
Re: Mail using non-local SMTP server.
Manoj Naik wrote: I want to use mutt to send mail to non-local SMTP server. Mutt does not do that. What it will do is call a commandline program, (usually sendmail,) and feed it the complete message, header and body. Generally, that commandline program called by Mutt will then send the message out over SMTP, but not necessarily. Whatever it does, though, is independent of Mutt. Mutt leaves transporting mail to the mail transport agent, as it should. I have read FAQ which says it is not mutts job and I have to configyre the MTa for this. Yep. Can anybody help me out on how to configure the MTA like sendmail/null mailer to do this and any changes in mutt configuration required for the purpose. First of all, your $sendmail variable must be correct in the ~/.muttrc file. This is the command Mutt will execute and to which it will feed the message. For example: set sendmail=/usr/sbin/sendmail -oem -oi I don't know about nullmailer, but for sendmail, include this in your sendmail.mc, then regenerate sendmail.cf through the m4 macro processor: define(`SMART_HOST', `the.remote.smtp.server') Then, in your ~/.muttrc file (or some file sourced by ~/.muttrc) you'll probably be best served to set the $envelope_from variable. set envelope_from This will cause Mutt to derive the envelope sender from the From: header. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: next-tag?
Iwan Mouwen asked: Is there a function like next-new (say next-tag) to quickly browse tagged messages? If not, is there a way to temporarily hide untagged messages? To jump to the next tagged message you could use the search function, which is bound by default to /. Try this: /~T. To hide untagged messages, use the limit function, bound by default to l. Try this: l~T. (To clear the limit pattern, use l.) Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: print to status line
Christian H. Stork wrote: How do I print something to the status line eg from a macro? Even better, how could I get input for some scripts on the status line? Well, I don't know about your second question, but to manipulate the status line requires setting the $status_format variable. This could be done with hooks, macros, or manually for that matter! Read about the $status_format variable in the manual. -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Suresh Ramasubramanian wrote: Using a large mallet, Mr. Wade whacked out: folder-hook .'unmy_hdr To:' folder-hook =IN-L-mutt-users 'my_hdr To: [EMAIL PROTECTED]' A problem with this, though, is that list-replies tend to have the list address twice in the To: field. I haven't spent any time determining a method to correct that. Heh, no. Doesnt need to be that way. Trust to mail-followup-to / reply-to set by the list (that takes care of the to) and just set your from header. See my muttrc at http://www.hserus.net/muttrc.html for a list oriented muttrc Well, for one thing, not all lists (this one, for example) modify the Reply-To: header. Also, not all users' MUAs accommodate Mail-Followup-To: headers, but most importantly: not all messages a user sends is a reply to a previous message. Too many users contaminate threads by replying to messages with something that is totally unrelated or break them by not replying where appropriate, beginning new threads. Some are simply too lazy to address an email for themselves, so they just reply, possibly neither understanding nor caring how annoying it is. :) This was an attempt to have Mutt use a default To: address for a mailbox folder, as I understand it. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Suresh Ramasubramanian wrote: Using a large mallet, Mr. Wade whacked out: This was an attempt to have Mutt use a default To: address for a mailbox folder, as I understand it. Yes. And I use procmail with other headers (say Sender: - usually distinctive to the list) to filter each list into a separate mbox I do this as well. I think that perhaps I misunderstood the original question. I was under the impression that the asker wanted to know how to have a default To: [EMAIL PROTECTED] header specified when he loaded his mailing list mailbox folder, so that he wouldn't have to enter that as input. You seem to be discussing sorting incoming mail rather than mail composition. -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Suresh Ramasubramanian wrote: Using a large mallet, Mr. Wade whacked out: I do this as well. I think that perhaps I misunderstood the original question. I was under the impression that the asker wanted to know how to have a default To: [EMAIL PROTECTED] header specified when he loaded his mailing list mailbox folder, so that he wouldn't have to enter that as input. You seem to be discussing sorting incoming mail rather than mail composition. Well, I sort incoming mail, and then use folder hooks to set my from address. Mutt's L (list reply to) along with subscribe foo in muttrc handles things quite OK. I agree,... but what about messages which are NOT replies? I think that's what the original question was about. If he invokes the mail function, (bound to m by default), he must then specify a To: header address. I think that's what he was trying to automate. -- Linux: The Choice of the GNU Generation
Re: sent messages
Jens Chr. Lisner wrote: I've set my sent-mail folder to ~/Mail/sent-mail. Mutt creates the folder, but the mail is not saved. I suppose this should be done, if the $record variable is set. You will need to set $copy as well as $record, e.g. set folder=~/Mail set copy=yes set record=+sent-mail Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: sent messages
Jens Chr. Lisner wrote: I've set my sent-mail folder to ~/Mail/sent-mail. Mutt creates the folder, but the mail is not saved. I suppose this should be done, if the $record variable is set. Mr. Wade advised: You will need to set $copy as well as $record, e.g. set folder=~/Mail set copy=yes set record=+sent-mail Jens Chr. Lisner replied: I've uncommented the $copy line in the .muttrc. It is explicitly set to yes now. But the mail is not written to the sent-mail file. Hmm... be sure that $save_name and $force_name are unset. Also, check to see if you have any fcc-hooks and fcc-save-hooks interfering with what you want. What about the perms on the ~/Mail/sent-mail file? If it's not writable for you, that could cause a problem. This might be wise: $ chmod u+w ~/Mail/sent-mail (I am assuming mbox mailbox format.) If $copy is set to yes, $save_name and $force_name are unset, there are no interfering fcc-hooks, $record is set to the correct path, and you have write permission to that file, it _should_ work, as far as I can tell! =) I hope this helps. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Kai Weber wrote: I am searching for a way defining a default TO: address depending on the actual folder. Let's say I am in the mutt's Mailinglist folder. If I press m I want a default address [EMAIL PROTECTED] there. I think it is an folder-hook thing, but I have no idea how to implement this. Any suggestions tips? This might help or give you a starting place, anyway: folder-hook .'unmy_hdr To:' folder-hook =IN-L-mutt-users 'my_hdr To: [EMAIL PROTECTED]' Obviously, I use =IN-L-mutt-users as the mailing list folder; you should sdjust that accordingly for your situation. A problem with this, though, is that list-replies tend to have the list address twice in the To: field. I haven't spent any time determining a method to correct that. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Kai Weber wrote: I am searching for a way defining a default TO: address depending on the actual folder. Let's say I am in the mutt's Mailinglist folder. If I press m I want a default address [EMAIL PROTECTED] there. I think it is an folder-hook thing, but I have no idea how to implement this. Any suggestions tips? Mr. Wade wrote: This might help or give you a starting place, anyway: folder-hook .'unmy_hdr To:' folder-hook =IN-L-mutt-users 'my_hdr To: [EMAIL PROTECTED]' Obviously, I use =IN-L-mutt-users as the mailing list folder; you should sdjust that accordingly for your situation. A problem with this, though, is that list-replies tend to have the list address twice in the To: field. I haven't spent any time determining a method to correct that. Regarding the problem I described: testing indicates that Mutt will include duplicated addresses in the command-line arguments used to call $sendmail, but it seems my MTA, Sendmail 8.11.3, filters out those duplicate addresses anyway, sending a message only once to each recipient, regardless of multiple mentions of the same recipient addresses on the command-line, so it's a non-issue for me, (but it's good to know! I had been very careful in the past to delete multiple mentions of the same recipient in the recipient fields. I guess that's unnecessary.) -- Mr. Wade -- Linux: The Choice of the GNU Generation
receiving bounced mails (was Re: Mutt issues with Solaris 8)
Masand, Manish wrote: Hi can u help me out please i am trying to configure mutt in such a way that i receive any bounced mails what is happening now is that the bounced mails are not coming back. I'm not sure what this has to do with the Subject line of Mutt issues with Solaris 8 or the text you quoted in your original message, but... You haven't given much to go on, but from what you describe, I would guess that your envelope sender address is incorrect. You might try setting $envelope_from and see if that helps. In your ~/.muttrc file: set envelope_from Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Deleting messages when entering a folder
Brian Nelson wrote: I would like mutt to delete messages older than a certain date when entering my mailing list folders, in other words executing the function: delete-pattern ~d 2w Is there a way to use folder hooks to execute a function? It seems as though hooks only run commands, and only macros use functions. Is this true, or am I just confused? Try using this as the command portion of the folder-hook: push delete-pattern~d 2wenter Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: How to give color to parent message
Efata wrote: How I give sign or color to message (message have child only) in collapse thread? Thanks I think you are asking how to specify index colors for a message that is part of a collapsed thread. Assuming your terminal supports color, this can be done using something like the following in ~/.muttrc or a another sourced file: color index red black ~v Of course, you could substitute whatever colors you like. This has effect only when the thread is collasped. When the thread is not collapsed, the color is not evidenced. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: How to give color to parent message
Efata wrote: How I give sign or color to message (message have child only) in collapse thread? Mr. Wade replied: I think you are asking how to specify index colors for a message that is part of a collapsed thread. Assuming your terminal supports color, this can be done using something like the following in ~/.muttrc or a another sourced file: color index red black ~v David Champion commented: You can also use the approach of setting index_format to contain %?M?%2M%4c? This will display the number of hidden children in a collapsed thread instead of the message size whenever a displayed message is a thread leader. I prefer this, since it gives more information and uses less color. (I save my colors for other things.) (Actually, my index_format the shows the number of children if there are collapsed children, or else the number of attachments if there are attachments, or else the message size. Quite a space-time-saver. :) ) I use a strategey similar to David Champion's index_format method. My $index_format contains %?M?(#%03M)(%4c)? which is nearly identical to what he suggested. I'd be interested, though, in how he managed to get the index_format to display the number of attachments if there are attachments as he said. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Post in Mailing List
Michael Tatge wrote: Mr. Wade muttered: ZHENG, You-Zhong wrote: I've read the sec 4.8 in mutt manual, but I still can't get it. It seems if you use lists, the %L index_format won't work, but list-reply key works in both lists and subscribe patterns. There must be some reasons for mutt author to add the new subscribe keyword, Well, one significant difference is how Mutt generates the Mail-Followup-To header when the $followup_to variable is set. The header will contain only the list's address for a list specified with the subscribe command, but it will contain both the list address and your own email address for lists named with the lists command. It's just the opposit. I humbly disagree; it is as I wrote, not the opposite. -- Linux: The Choice of the GNU Generation
Re: Hello. I need help configuring mutt.
Jonathan Rosebaugh wrote: Ok, I'm new to mutt, and I am very confused. 1) The machine I read mail on is called frodo. I get my mail using fetchmail. 2) My primary email address is [EMAIL PROTECTED], but I also receive mail at email addresses like [EMAIL PROTECTED] or [EMAIL PROTECTED] 3) Unless I specify 'my_hdr From: Jonathan Rosebaugh [EMAIL PROTECTED]', mutt insists on sending my mail as skip@frodo. 4) I would like to: a) Reply to messages with the email address that they were sent to. 'set reverse_name' does not seem to work when coupled with the above 'my_hdr'. b) Be able to specify which email address to use, if I don't want to use the default. c) By default, send email as [EMAIL PROTECTED] Please help me find what I need to put in .muttrc. Thanks very much. First thing's first: wrapping your lines at some point less than 80 characters is a good thing. =o) Using the my_hdr From: seems to supersede the $reverse_name variable. What you probably want to do is to not use the my_hdr to set the From: address, but do this instead: set from=[EMAIL PROTECTED] (Jonathan Rosebaugh) set reverse_name An easy way to be able to specify which email address to use is to create aliases for those addresses, then you can just type in the shorter alias, rather than the entire address. For example (and these are just examples!) alias email [EMAIL PROTECTED] (Skip Rosebaugh) alias plover [EMAIL PROTECTED] (Skip) alias mnsu [EMAIL PROTECTED] (Jonathan Rosebaugh) Doing this would allow you to type email plover or mnsu in order to refer to their respective addresses. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Post in Mailing List
ZHENG, You-Zhong wrote: On 05-01-2001, Suresh Ramasubramanian wrote: So why bother just renaming lists to subscribe? Please read the mutt documentation (should be there on your pc) for why. I've read the sec 4.8 in mutt manual, but I still can't get it. It seems if you use lists, the %L index_format won't work, but list-reply key works in both lists and subscribe patterns. There must be some reasons for mutt author to add the new subscribe keyword, Well, one significant difference is how Mutt generates the Mail-Followup-To header when the $followup_to variable is set. The header will contain only the list's address for a list specified with the subscribe command, but it will contain both the list address and your own email address for lists named with the lists command. -- Linux: The Choice of the GNU Generation
Re: Unsubscribe
Raphaël HALIMI wrote: How do I unsubscribe from that list ? Send an e-mail message to [EMAIL PROTECTED] with the following in the BODY of the message: unsubscribe mutt-users [EMAIL PROTECTED]
Re: How eliminate (same 2) *questions* when exit mutt?
Dr. Christian Seberino wrote: How prevent mutt from always asking if I want to move email to mbox and if I _really_ want to delete the email I just deleted when I exit mutt? Does anyone else not want to answer the same 2 questions every day for the rest of their lives? (Especially when answer is always the same.) Use the $delete aned $move variables. These are both quad-option variables, accepting values of 'yes', 'no', 'ask-yes', and 'ask-no'. For example, in ~/.muttrc (or another sourced file): set delete=yes # Really delete messages when closing or # synchronizing a mailbox, (without asking.) set move=no # Do not move (or ask to move) read messages from # $spoolfile to $mbox Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: easy way to hide messages?
Jason A . Fager wrote: Is there an easy way to get mutt to ignore messages that match a certain pattern? I figure I could use l with an inverse pattern, but I have not been able to figure out how to use multiple invocations of l multiple times with cumulative effect (like you can use t multiple times). jafager Read the section of the manual regarding Complex Patterns for that info. You can specify more than one criterion to have them logically ANDed. You can use parentheses for logical grouping. There are logical NOT and OR operators, etc. -- Linux: The Choice of the GNU Generation
Re: Help - domain does not exist
Rodrigo Vega Fonseca wrote: snip Mutt can send mail to everyone I try but when it comes to my own account ([EMAIL PROTECTED]) the server returns my mail with the message: Diagnostic-Code: SMTP; 501 5.1.8 [EMAIL PROTECTED]... Domain of sender address [EMAIL PROTECTED] does not exist and my message won't post... What does that mean? Does it mean that I have to setup a network with a real domain just to use Mutt? I don't think so. snip I've already ready the man pages, online help and other resources and modified my .muttrc file with the parameters: set hostname=uai.com.br set pop_host=pop.uai.com.br set pop_user=vvega set hdrs #to include my_hdr lines to message headers and my_hdr From: Rodrigo Fonseca [EMAIL PROTECTED] snip Another annoying thing is that every mail I fetch from the server is kept there and every time I download the new messages, the old ones come again. I need to download the new messages from the server and then delete them. Don't really know what's happening... You might try setting the $envelope_from variable. That could help eliminate the error you are receiving from the mailserver. In ~/.muttrc (or some file sourced by ~/.muttrc): set envelope_from Also, to delete messages aff the POP host after downloading them, set the $pop_delete variable. In ~/.muttrc (or some file sourced by ~/.muttrc): set pop_delete You might, however, be better served to not use Mutt's mail retrieval functions and use a mail retrieval utility like fetchmail instead. Personally, I find it more convenient and useful, especially since it has more flexibility and can handle multiple accounts, (although, with some clever hooks, I guess Mutt could emulate some of the functionality.) Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Mailing list From: field in index
Brian Nelson wrote:
I recently added the mailing lists I subscribe to using the
'subscribe' setting in my muttrc. Apparently, by default, when mutt
recognizes an email from mailing list, it changes the display in the
index to show 'To [EMAIL PROTECTED]' or 'CC [EMAIL PROTECTED]' for
example instead of the name of the person who sent the email.
This is undesirable since I already sort my mailing lists into folders
with procmail. It's not very helpful to see that every email in the
folder was send to the mailing list.
How would I override this behavior to make mutt show the 'From' field
in the index for mailing lists instead of 'To' or 'CC'?
Thanks.
--
Brian Nelson [EMAIL PROTECTED]
You'll want to take a look at the $index_format variable. Like
many things in Mutt, the format of the index is highly
configurable.
As an example, I am currently using:
set index_format=%4C %S %{%m/%d} %-18.18n %?M?(#%03M)(%4c)? %s
Good luck.
-- Mr. Wade
--
Linux: The Choice of the GNU Generation
Re: Default subject
Eugene P. Guilaran wrote: When replying to a message with an empty subject, Mutt defaults the subject to you mail. Is there a way I can change this? Joshua Haberman wrote: snip It seems to be hard-coded, so you'd have to change the above source in send.c and recompile. Alternatively, you could pipe you outgoing mail through a script that checks the Subject: header using formail and alters it to whatever you like if it maches Re: your mail, again using formail. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: open collapsed automatically
Johannes Zellner wrote: Hi, is it possible to have the index pages opened with all threads collapsed automatically? -- Johannes You could try something along the lines of: folder-hook =foldername set sort=threads; push collapse-all (This assumes that $folder is set at some point prior to this line.) Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Using multiple mail server for uploading mail
Rod Pike wrote: Can a send hook be used so that ultimately, a different mail server will be used to send the mail? Just off the top of my head... you could use a send-hook to change the $sendmail variable to call a script that would copy an alternate sendmail.cf into /etc/sendmail.cf before passing the email to sendmail. Of course,... overwriting /etc/sendmail.cf would require root access, necessitating the use of sudo. Hmm... I guess it's more complicated than I first thought. =) -- Linux: The Choice of the GNU Generation
Re: Colors when replying to messages
Marco Fioretti wrote: I have colors set in .muttrc as I like both in the index and when I read messages. When I *send* messages, however, i.e. whenever I hit either the r or the m keys, mutt colors headers and quotes in a different and unreadable way. I haven't found in the manual or in the .muttrc files I downloaded from the net anything about this, and even the /etc/Muttrc file doesn't contain anything related to colors. I guess I could patch this with a send-hook which applies to ALL outgoing messages, but I'd like to know both why does this happen, and if there are more elegant/proper ways to do it. Any help/pointers/muttrc examples explaining how to set colors only when sending messages would be really appreciated. If you are talking about the colors in your editor while you are composing the message, then Mutt is not responsible for coloring. You will need to address that issue with your editor's configuration files or settings. Note that the $editor variable specifies which editor is used by Mutt. It defaults to the value of the $EDITOR or $VISUAL environment variables, or to vi. If $editor is null, then Mutt seems to use some sort of mailx-like internal editor (in which coloring is not an issue.) If you are talking about how message bodies look in the pager before sending, then I don't know how to help you. They are not colored the same way a message is colored when viewed in the pager, (but the headers are not displayed, so I am thinking you are talking about this, since you specifically mentioned the headers.) If readability is impaired, the object normal may help improve that, e.g. color normal cyan black I hope you get it fixed to your liking. :) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Two questions (maildir and mailinig lists)
Horace G. Friend III wrote: On Mon, Apr 23, 2001 at 01:15:44PM +0300, Micha Berdichevsky wrote: 2. When I post to a mailing list, I see my messages (in the idnex) with the 'From' field saying 'To list@host' instead of my name. Any ideas? I'm using the mbox mailbox format. I'm also experiencing problem 2. I have always thought of it as a default of Mutt when dealing with incoming mail which originated from yourself such as your replies to mailing lists. Well, would anyone know if problem no. 2 is indeed a problem or Mutt's default? If it is the latter, how can we change this behavior? You'll want to take a look at the $index_format variable. Like many things in Mutt, the format of the index is highly configurable. Good luck. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Thread trees (was: Re: mutt as newsreader?)
Daniel Nielsen wrote: Another thing about configuring mutt perhaps a bit [OT] ) when (in ~/.muttrc) using set ascii-chars it uses ` , | to view threads etc. but when having $ascii-chars unset it uses @ and other weird symbols. Funny thing is though, that it only happens when i use mutt at my university. It doesn't happen if i ssh in from home... (then it looks 'nice') Does anyone have a clue why? It is probably the console font being used at the terminal you are using at your University. Some of the console fonts I have on my box display such weird symbols for the thread trees, so I selected one that looks nice for my own use. I'm not sure, though, if you will have that luxury. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: notation?
Daniel Nielsen wrote: It seems that (when using $ascii_chars) and someone replies to a mail in a thread. somtimes it shows `- other times it shows `* what does it do? My guess is something with guessing whether or not the msg. 100% surely belongs in this thread, but I'm just curious... My observations indicate that if $strict_threads is unset, then Mutt uses the * notation you describe if it is placing the message in the psuedo-thread based upon the Subject: header field. It uses the - notation you describe when it is placing the message in the thread because of an In-Reply-To: or References: header field. If $strict_threads is set, then you won't get sorting into pseudo-threads by the Subject: header field, and the * notations will not be there either. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Console fonts (was: Re: Thread trees...)
Daniel Nielsen wrote: Oki, this might seem newbieish... but where and how do you view your current consolefont / change it I will have to admit ignorance here, but what I am about to describe might be distribution-specific; I don't know, but... I use Slackware Linux; there is a setfont command that does the job of setting the console screen font. It is part of the kbd package. That package also has a fontconfig script that will setup the default font for the system, but should be run as root, of course. Also, /usr/lib/kbd/consolefonts is the default font directory. I find a great number of fonts in there, (in excess of 150.) I use: $ setfont -v lat4a-16+.psfu.gz I like that font because it's clear and large, making it easy to read, (for me). Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
