Re: Module to add mailinglist-names from the header in .muttrc
* Oliver Fuchs [EMAIL PROTECTED] [2002-10-03 15:29]: Is there something similar no more hand work for/in mutt? Example: Extract the mailing-list address from the header, add it in .muttrc to the mailbox and the list/subscribe feature? Didn't see the original message, I apologize for the minor thread breaking. It's possible to set up procmail to automatically recognize most lists, and then siphon that into a folder based on list name. Like mutt-users goes to a folder [EMAIL PROTECTED] You could create a shell script, so that when procmail sees a list mail, it siphons off into that folder, and calls this shell-script with the name of the folder. Shell scripts checks some file to see if you've got things defined, if not, it adds them, and source this file from muttrc. But I'm sure I'm getting off-topic.
Folder specific mailing, smart fcc-save-hooks, question.
I was recently unsubscribed (I am subscribed again now), saw a message from Bernard Massot in the archives, asking about folder-specific macros for 'm', to send mail to the right participants. He thought it would be a good idea to send this to the list, so here it is, with a bit more tacked on the end, along with a question at the end. --- What I do is admittedly a little complicated. Procmail automatically creates folders for lists (ask for the recipe if you want, I got it off the net somewhere...) and puts them in folders like this: (Snipped output, but explanatory enough...) apex:~/.Mail/lists$ ls [EMAIL PROTECTED]/ [EMAIL PROTECTED]/ [EMAIL PROTECTED]/ I also have save hooks to save to the email address of the sender, and save sent messages to that folder, if it exists. [ed note: appended on bottom] What you want is here: # These use macros to specify a default recipient for the folders it # makes sense for. folder-hook . 'macro index m mail' folder-hook . 'macro pager m mail' source ~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/| source ~/.mutt/hooks/folder.recip.sh ~/.Mail/people/| With me so far? ~~/.mutt/hooks/folder.recip.sh is the following: #!/bin/sh # Generates folder-hooks of the form: # # folder-hook DIRNAME 'macro index m mailDIRNAMEenter' if [ $# -ne 1 ]; then echo Usage: $0 name; exit 127; fi for i in $(ls $1);do echo folder-hook $i 'macro index m \mail$ienter\'; echo folder-hook $i 'macro pager m \mail$ienter\'; done # end And there we have it. # These generate fcc-save-hooks for each address/list that already has # its own folder. source ~/.mutt/hooks/save.sh ~/.Mail/lists/| source ~/.mutt/hooks/save.sh ~/.Mail/people/| save-hook . =people/%a ~~/.mutt/hooks/save.sh is this: #!/bin/sh # Generates fcc-save-hooks of the form: # fcc-save-hook DIRNAME =DIR/ADDRESS if [ $# -ne 1 ]; then echo Usage: $0 name; exit 127; fi for i in $(ls $1);do\ echo fcc-save-hook $i =$(basename $1)/$i;\ done And then that's done too. If you don't have a folder for a person, it throws a message sent to them into record, if you do, it puts it in there. Now the question: Can I make these all case insensitive? For instance right now things to [EMAIL PROTECTED] and [EMAIL PROTECTED] or [EMAIL PROTECTED] are all treated differently, so with a mail sent to each of these addresses, only the one that matches the folder name including case sensitivity gets put there, the others go into record. Thanks in advance.
Sourcing scripts, screen flashes.
Since I've added source lines for a couple scripts, when I start up mutt, the screen flashes several times. source ~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/| source ~/.mutt/hooks/folder.recip.sh ~/.Mail/people/| That sort of thing. Anything I can do to avoid this?
Command on reply.
I'm looking for something that'll do the following: When I reply to a message, and the reply is sent (ie not aborted), save the replied-to message to the right folder. Save-hook is set up already for the latter part. Thanks in advance.
Re: Command on reply.
* Sven Guckes [EMAIL PROTECTED] [020903]: * Ryan Sorensen [EMAIL PROTECTED] [2002-09-03 07:00]: Save-hook is set up already for the latter part. your request is sufficiently confusing to be irrelevant. congratulations. Shall I try again? Given a message in a folder like so: 1 + Jan 1 Mr Foo ( 1) Subject I want to reply to this message, and when the reply is succesfully sent, just save the original message, the one from Mr Foo.
Re: followups (was Re: mutt and gnupg setup)
* Will Yardley [EMAIL PROTECTED] [020829]: Markus Nißl wrote: I will do so! Thanks again. BTW: no cc: to my address necessary, I'm subscribed to this list for a year now. well you're the one who has: Mail-Followup-To: Markus Nißl [EMAIL PROTECTED], [EMAIL PROTECTED] set. perhaps you want 'subscribe mutt-users' instead of 'lists mutt-users' in your .muttrc? Or in case you seperate lists into folders and find the default from for listed things annoying, look into 'followup_to'.
Re: Complex fcc-hook?
msg.pgp Description: PGP message
Complex fcc-hook?
I have procmail and mutt set up so mails for lists are automatically put in =lists/listname, and mutt recognizes every subdirectory name in that directory as a list. listname is the part before the , like mutt-users for this one. Default save for other things, people, mainly, is in =people/name, where again, name is the part before the . How can I create fcc-hooks to put sent mail in the right directories?
Re: Mutt hanging on new message. [Solution enclosed!]
It's been a long, hard road, but we're here again. Recap of the problem: Mutt would work fine, except when trying to compose a new message, it would hang after entering subject. Cause of problem: set signature='~/.sig' Now, for the $1000 prize, what could be wrong with that that would cause mutt to hang the way it was? 'twas a broken pipe. But we're all better now. Thanks for the responses from the list.
Mutt hanging on new message.
So, a couple days ago, best I can figure, after a reboot, mutt now can't open temp files, or at least that's what I'm guessing, because it hangs after entering subject and hitting enter. GDB is saying it's on an open() call. It hangs indefinitely. This reboot didn't change much, I did it because apache-ssl wasn't working after a Debian upgrade, and I just upgraded again and rebooted. No kernel change, nothing weird installing. /tmp has permissions drwxrwxrwt, changing tmpdir to $HOME doesn't help, subdirectories of it don't help, nothing.. I didn't change any rc files. mutt's version is 1.4.0-2, and like I say, nothing weird changed. All the rc files hadn't changed for about 4 days before it got weird. And even that was just an unmy_hdr. I'm completely stumped, and sending this through /usr/bin/mail.
