Re: vim and a junk sig
Joe Rice wrote: please excuse me if this made to the list already. i had some subscription problems. hi, I'm using vim as the editor for mutt. just recently i started to get this huge line of random characters at the bottom of all the email i compose. This had never happened before. I upgraded vim to the latest version thinking it had something to do with "Malicious embedded VIM control codes". the problem still persisted. I then upgraded mutt to 1.3.17i and it is still happening. I've never used a sig and i don't have any thing in my .muttrc that would include one. If anyone can help solve this problem i would appreciate it. Thanks joe As I responded the first time, in case Joe didn't receive it: I believe the $signature variable defaults to "~/.signature" if you have not specified something else. Have you checked to see if somehow you or something has created a ~/.signature file, perhaps unintentionally? -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: vim and a junk sig
Joe Rice wrote: hi, I'm using vim as the editor for mutt. just recently i started to get this huge line of random characters at the bottom of all the email i compose. This had never happened before. I upgraded vim to the latest version thinking it had something to do with "Malicious embedded VIM control codes". the problem still persisted. I then upgraded mutt to 1.3.17i and it is still happening. I've never used a sig and i don't have any thing in my .muttrc that would include one. If anyone can help solve this problem i would appreciate it. Thanks joe I believe the $signature variable defaults to "~/.signature" if you have not specified something else. Have you checked to see if somehow you or something has created a ~/.signature file, perhaps unintentionally? -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Orphaned tmp files?
Suresh Ramasubramanian wrote: Jim Lambert proclaimed on mutt-users that: I've noticed that mutt occasionally forgets to clean up tmp files. It seems to be an intermittent problem and I was wondering if other users had seen it. Check your editor settings - if its vim, it'll be something like set nobackup" do not keep a backup file, use versions instead I've noticed mutt files building up in /tmp too. I use vim for the editor, and nobackup seems to be the default. In any case, I have nobackup set, but I still get the files accumulating in /tmp so I'm not sure what the story is about that. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: fetchmail mutt
Dave Murray wrote:
Suresh Ramasubramanian wrote on mutt-users:
Something is fubarred with the permissions of /var/spool/mail I
expect. Try chmod 777 /var/spool/mail, chmod +t /var/spool/mail
And have something listening on port 25 unless you use procmail as
your mda ("/usr/bin/procmail -d %T" should do very nicely)
Thank you, that fixed it but now my mail goes to /var/spool/mail/me
where it was spooling to ~/Mail/inbox. My other folders are in
~/Mail/somenames. Is there a convenient way to get the new mail
in /var/spool/mail/me to ~/Mail/inbox ?
Regards and thanks again,
Dave
This is somewhat off-topic; where your mail is delivered is the
job of the mail delivery agent (MDA) and not that of the mail
user agent (MUA). For example, if you are using procmail as the
MDA, as I am, then if you specify a value for $DEFAULT in your
~/.procmailrc file, then any mail that "falls off the end" of the
rcfile will be delivered to $DEFAULT. Is that what you
desire?
-- Mr. Wade
--
Linux: The Choice of the GNU Generation
Re: Features not quite working for me
CB wrote: I've got a couple of things that I can't make work right. The main one that I'm interested in is saving sent messages. Refer to my attached muttrc. Can you tell me why it's not saving sent messages to ~~/nsmail/Sent? snip # Folder and Mailbox ## #set write_inc = 10 set sort_browser = reverse-date set record = "Sent" #set pipe_split = no #set pipe_decode = no #set pipe_sep = "\n" #set move = ask-no #set mask = "!^\\.[^.]" #set mbox = ~/nsmail #set mbox_type = mbox #set mh_purge = no #set confirmappend = yes #set confirmcreate = yes set copy = yes #set default_hook = "~f %s !~P | (~P ~C %s)" #set fcc_attach = yes #set fcc_clear = no set folder = "~/nsmail" #set folder_format = "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f" #set folder_format="%N %-8.8u %8s %d %N %f" #set force_name = no $record needs to be the path to the mailbox where you want your outgoing mail saved, e.g. set record="~/nsmail/Sent" By the way, if you specify $folder before $record, then you can use "+" or "=" in the path name. The "+" or "=" will expand to the value of $folder, e.g. set folder=~/nsmail set record=+Sent Good luck. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: scrolling in a message
Jeroen Valcke wrote: But how can I scroll line by line, I just can't find this simple thing. Found something about '' and '' but this only works in the message lister. In the pager, you can use the previous-line function to scroll up one line. I believe the default binding for this is the backspace key. For scrolling down one line in the pager, use the next-line function, which is bound by default to the enter key. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Finding new mail
CB wrote: On Sat, Apr 14, 2001 at 06:18:43PM +0200, Andre Berger wrote: Did you set "mailboxes", like in mailboxes ! +mutt-users +onemoremailbox +anothermailbox No, I do not have the plus sign in front of any of my mailboxes that I have listed. I'll try that. Also, is it case-sensitve? I'll assume that it is. The mailboxes you specify are filenames of mailboxes that you want Mutt to recognize as those that receive mail. When you use "+" or "=" as part of the filename, it expands to the value of the $folder variable. Note, also, that "!" expands to the value of the $spool variable. It's important to specify these before the mailboxes commands in the ~/.muttrc file. maybe in combination with subscribe mutt-users mutt-users@mutt\.org I am using the subscribe function, but mine do not look like this. I don't have the second parameter. I just list all of my subscribed lists on three long lines. Maybe that's part of my problem. You need only specify as much of the address of the mailing list as you need to ensure a lack of ambiguity; also, you can specify a number of mailing lists on a single line. I have it sorted reverse date, so I just use my thinking cap and figure out where Not that I could think of. BTW sorting by threads is way better IMHO. I have folder hook set to sort all folders by thread. The only thing that sorts by reverse date is the folder list. But I think I've got some major misunderstanding of the parameter settings and need to go modify them before I ask further questions. Is there a comprehensive parameter listing anywhere? I've not been able to find one, but I'm probably looking at the wrong places. The man page for mutt says nothing about the muttrc file and there's no man page for muttrc, so I'm coming up with parameters from people's examples. Have you not read the docs?! On my system it is located at /usr/local/doc/mutt/manual.txt Also, there is a default macro that pipes it through less when I press the F1 key. Reading that file is an absolute must! =o) It should help to clear up a lot for you. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Finding new mail
Ailbhe Leamy wrote: If anyone does know a way of displaying only folders with new mail when one presses "c", I'd love to hear about it. I asked a few days ago, and no-one seems to know. I'd like to know how to do that, too. I thought about it the first time you mentioned it, and couldn't come up with anything using the Mutt commands. I guess one could write a script to examine a mailbox file's last modification time and last access time... that would let you know which one's have new mail, but how to incorporate that into Mutt smoothly is a bit beyond me. :) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Finding new mail
Wade A. Mosely wrote: The mailboxes you specify are filenames of mailboxes that you want Mutt to recognize as those that receive mail. When you use "+" or "=" as part of the filename, it expands to the value of the $folder variable. Note, also, that "!" expands to the value of the $spool variable. It's important to specify these before the mailboxes commands in the ~/.muttrc file. Ermm... I meant $spoolfile instead of $spool for the variable I mentioned. Sorry! :) -- Linux: The Choice of the GNU Generation
Re: [OT] well slightly
Tim Whitehead wrote: The resulting line from that was my_hdr X-Operating-System: `uname -rsm` `uptime | sed s/.*up/up/ | sed s/,[[:space:]0-9]*users.*$//` so I adopted it to my_hdr X-Mailer: `mutt -v| grep Mutt -n|grep 1:|sed s/.*Mutt/Mutt/` As you can see this is a round about way of doing it... But it also leaves on the day I compiled this version of Mutt. What would be the best way to chop that date off? For one thing, Mutt already includes a "User-Agent:" header line. Is it really necessary to duplicate that information in an "X-Mailer:" line? If so, then this should do what you want: my_hdr X-Mailer: `mutt -v | sed s/"[:space:]*(.*"//` (Because it is line oriented, only the first line of output from the command should be substituted, eliminating your greps.) By the way, your "X-Operating-System:" my_hdr could be simplified slightly by this: my_hdr X-Operating-System: `uname -smr` `uptime | sed \ 's/.*\(up.*\),\ \+[0-9]\+\ user.*/\1/'` This uses only one sed command rather than two. It's generally better to use fewer processes when possible. :o) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: two mutt questions
Dave Csercsics wrote: Ok, Mutt ios a great program and all that but I have a couple questions. Well a problem and a question. The problem is that I cannot figure out how to tell mutt the name of my smtp server so that I can get mutt to send mail. I can receive fine but not send. Any help with this would be greatly appreciated. Now my question. When I am done editing the body of my message why is it put into the message that I am about to send as an attachment rather than in the message body? How would you change that so that when you edit a message it gets put in the body of the message you are about to send. That is all I have for now. I think this program is great and I would like it even more if I could send my mail. Firstly, please wrap your text at less than 80 characters. Secondly, Mutt calls a command line program, (usually sendmail,) to send mail. Generally, the command line program will send the message out over SMTP, but there is nothing that guarantees that. Mutt leaves transporting mail to the mail transport agent, (as it should!) Lastly, I'm not sure what you mean in that your message body appears as an attachment. In the compose screen, I guess, the first "attachment" listed is the message body. I assume that's what you mean. If so, then you need not worry; it's the message body, not really a MIME part attachment like you might be thinking. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Colors aren't quite working
Ailbhe Leamy wrote: Nothing I've tried has allowed me to colour ^X-(anything except X-Mailer:) seperately from X-Mailer: XMailer: always gets trapped in the X- colouring. Try specifying the X- coloring before the X-Mailer coloring, e.g. color header green black ^X-.*: color header white black ^X-Mailer: Good luck. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Colors aren't quite working
Ailbhe Leamy wrote: On (05/04/01 15:26), Wade A. Mosely wrote: Ailbhe Leamy wrote: Nothing I've tried has allowed me to colour ^X-(anything except X-Mailer:) seperately from X-Mailer: XMailer: always gets trapped in the X- colouring. Try specifying the X- coloring before the X-Mailer coloring, e.g. color header green black ^X-.*: color header white black ^X-Mailer: Sadly, this doesn't work. Nor does reversing the order. Is there a way to construct a muttrc-friendly regexp to match "^X-(.*!'Mailer'):" or something? Hmm... what I posted works for me without problems. I'm using Mutt/1.2.5i. -- Linux: The Choice of the GNU Generation
Re: set pgp_encryptself: unknown variable
Rod Pike wrote: Greetings, I'm using version 1.2.5i of Mutt. Why do I get an error when I try to "set pgp_encryptself" in my muttrc? Cheers, Rod -- Rod Pike rodneyp @ utanet.at Your subject line says it all. -- Linux: The Choice of the GNU Generation
Re: URL becomes header automatically
Eric Smith wrote: Often I send an url like http:/somewhere.com/whatever The line of the URL is the only line in the body - mutt takes the line and makes a header out of it. /not/ what I want. How do I get round this? If you have $edit_headers unset in your ~/.muttrc file, then the described phenomenon should not occur. If, however, you have $edit_headers set, then simply leave a blank line after the last header line in the edit buffer of your editor before the start of the body. That should solve the problem. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: mailboxes
Marius Strom wrote:
Better to use ls -1. You bypass a lot of fstat() calls when doing the
ls -l, you probably don't need the -a (unless you have boxes that start
with a "."), and by doing ls -1 you bypass the need for the awk command.
ls -1 $HOME/mail/* | grep -v sent
Much better, and more efficient on a large mailbox structure.
That scheme could get ugly if you happen to have an MH mailbox in
$HOME/mail like I do. ;o) I really don't want a bunch of numerically
named files mistakenly declared in the mailboxes command. Eliminating
the asterisk ("*") might be more proper; then it won't descend into
subdirectories. ("ls -1 $HOME/mail/ | grep -v sent")
My solution is this: Like many others, I adopt a naming convention in
which all mailboxes receiving incoming email start with "IN.", e.g.
IN.work gets all email addressed to my work email account, etc. This
does three things for me:
1. My incoming mailboxes are all listed together in the file browser.
2. My incoming mailboxes are listed first, since capital letters
come before lowercase and I avoid capital letters in the mailbox
names.
3. I can use the IN\..* pattern for folder-hooks, etc.
So, to include my spool mailbox ($spool) and all =IN\..* mailboxes in the
mailboxes declaration, I use this in ~/.muttrc :
mailboxes ! `echo $HOME/Mail/IN.*` # $spool and =IN\..* receive incoming mail.
The only problem I have with this is that the nice little message
telling me I have new mail in any newly created mailboxes isn't active
until the next time I startup Mutt (or :source .muttrc).
-- Mr. Wade
--
Linux: The Choice of the GNU Generation
Re: how-to elimintate headers in folder-hooks
Thomas Duterme wrote: Hi everyone, I'm pretty new to mutt, but I love it so far. My one problem: I'd like to eliminate, or reduce headers at least in my mailboxes. Actually, I'ld like to if possible just keep the basic headers like Subject and From, rather than get the entire envelope. Is this possible? TIA, Thomas If you mean you want to reduce what is displayed in the pager, then you'll want to take advantage of Mutt's header weeding. Check out the sections of the manual dealing with that topic, especially the 'ignore' and 'unignore' commands, the 'weed' variable, and the 'display-toggle-weed' function. However, if you mean you want the headers actually removed from the email, then it sounds like a job for a mail formatter like formail, probably most conveniently invoked from a mail processor like procmail as the messages are coming in, (that's how I do it, anyway.) (BTW, good form requires you to limit your line length to less than 80 characters.) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: too many messages saturates slow link
Carlos Puchol wrote: this saturates my modem line for a little while. because (it seems) there is a lot of redraws printing the message count (one line per message?). is there some way to turn it off or just make it show the XX% part (assuming it is not printed at every message)? Have you tried setting $read_inc and $write_inc to greater values? Perhaps that would help. -- Linux: The Choice of the GNU Generation
Re: Randomly change From: and signature using Macros
Ailbhe Leamy wrote:
Subject: "Randomly" change From: and signature using Macros
Is this possible? I can't find anything really useful using a Google
search.
For the "From:" you could specify a shell script that outputs
your desired "From:" address on stdout, then use a send-hook to
call it. For example, if the script to generate your "From:"
address is ~/.mutt/selectfrom (and is mode +x) you could:
send-hook . "set from=\"`~/.mutt/selectfrom`\""
(Note the use of backquotes for command substitution.)
For the signature, just specify the script with a pipe. If
$signature ends with a pipe ('|'), it is treated as a shell
command and its stdout is used as the signature. If you had a
script ~/.mutt/createsig that delivered a random signature on
stdout, then:
set signature='~/.mutt/createsig|'
Good luck. :)
-- Mr. Wade
--
Linux: The Choice of the GNU Generation
Re: Randomly change From: and signature using Macros
Ailbhe Leamy wrote: However, I obviously expressed myself badly. What I actually want is the ability to hit ^foo and have it change the From and Sig to a pre-determined one, presumably using a :set command. ^bar to change to a different one. I'd prefer to be able to do this _after_ composing a message, but will accept answers on how to do it in the index. I'm not sure about the signature being changed after composition by a keyboard macro, an example to change the "From:" address to '[EMAIL PROTECTED] (name)' using ^W : macro compose \cw 'edit-fromhome(enteredit-from \ [EMAIL PROTECTED] (name)enter' 'change to "From: name [EMAIL PROTECTED]"' I hope it helps! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: set return-path?
Zach Thompson wrote: I notice that the Return-Path header it set to [EMAIL PROTECTED], which is me at my workstation. I have the reply-to and from header set to [EMAIL PROTECTED], but I think that the mailing list program at mysql is trying to use the bertha address... I had a similar problem until I discovered I needed to set $envelope_from to solve the problem for me. You might try that. In ~/.muttrc : set envelope_from I hope it helps. Note, however, that this will be passed to $sendmail with the '-f' switch. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Mutt, procmail, and sendmail
I want to use procmail to do some pre-processing of outgoing mail before sending. I have created an rcfile for procmail that does what I want called ~/.procoutrc which does the processing I want using formail and passes the mail to sendmail for sending. It works as I expect and want if I cat message | procmail ~/.procoutrc My problem is that I don't know what to use for ~/.muttrc in the $sendmail variable. I tried set sendmail="cat | procmail ~/.procoutrc" It didn't work. That Mutt appends destination addresses to the command line appears to be the issue. I am using the '-t' switch in sendmail to determine destination addresses, so ignoring those command line addresses is OK. How can I accomplish this? (Is there a better way than what I am doing?) Thanks, -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Mutt, procmail, and sendmail
BTW, one of the main things I am trying to accomplish is changing
the recipient headers ("To:", "Cc:", "Bcc:") in outgoing messages
Based upon their contents. Send-hooks don't seem to work to do
this.
From /usr/local/doc/mutt/manual.txt :
"... note that my_hdr commands which modify recipient headers, or
the message's subject, don't have any effect on the current
message when executed from a send-hook."
Is there an easier way than what I am attempting in using
procmail/formail before sending?
--
Linux: The Choice of the GNU Generation
Mutt, procmail, and sendmail
Lars Hecking wrote: Well, passing the message to a very simple one line script seems to work. I made a ~/.mutt/mailout (mode +x to make it executable): #!/bin/sh cat | procmail ~/.procoutrc # End of ~/.mutt/mailout [Splutter] Useless Use of cat. Thanks, Lars, for that marvelously helpful comment. I didn't find any better solution on my own, though. Using 'set sendmail="procmail ~/.procoutrc"' didn't seem to work because of the recipients being included on the command line by Mutt. Is there a better way to get the message passed to procmail from Mutt? Also, I apologize for breaking a couple of message threads. It was unintentional, of course. =) -- Linux: The Choice of the GNU Generation
Re: Mutt, procmail, and sendmail
Tony Collins wrote: Completely off-topic, I notice that your X-Operating-System header contains the kernel version and the uptime. What have you got in your .muttrc to make it put these things in your headers? I use: my_hdr X-Operating-System: `uname -smr` `uptime | sed s/.*up/up/ \ | sed s/,[[:space:]0-9]*users.*$//` It's probably clumsy, but it works! =) -- Linux: The Choice of the GNU Generation
Re: thread collapsing
David Rock wrote: There must be a way, since the ^d deletes an entire thread If the collapse-thread and collapse-all functions did what their names suggest and if they had uncollapsing counterpart functions, then it would be easy. Instead, the named functions act as toggles, which complicates the matter. Maybe someone smarter than I can figure it out; I have been unsuccessful so far. =) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: vim and mutt question
Timothy Legant wrote: You might not always want to move down 6 lines. Perhaps in the future you will add a new header (using my_hdr) to certain messages. You might want to consider the following instead: set editor="vim -c ':0;/^$'" which will search for and move to the first blank line. In an email message that should be the first line after all the headers, no matter how many header lines there are. That's great, Tim! It sure beats what I had been using before. However, I like to edit my replies after quoted messages, so I think '-c ":$;?^$"' is a better command line argument for me, since it places the cursor on the last blank line, i.e. after any quoted text but before my signature. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: spell checking
Robert Barish wrote: Hello I am just getting my feet wet with mutt and trying it out to see if it will be my email client of choice. So far I really like the speed of mutt. I have a real basic question. How does one incoporate a spell checker with mutt? Does it use ispell. If you can use a spell checker how does one activate it. Thanks for all help ahead of time. Bob ispell is invoked with the ispell function. The default binding for this is "i" when composing a message. Note that invocation of ispell is governed by the $ispell variable, which must be set to the path of ispell. (The default is: "/usr/bin/ispell".) -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: FWD with attached files...
Todd Holloway wrote: I"m using 1.3.13i and when I get an attached HTML files (I haven't tested other types yet) and I use "f" to forward, the HTML part itsn't included. Even when I first "view" the HTML...and then forward with "f"... it still isn't included. I figured out how-to fwd the full headers (by using "h" to view then and then forwarding them...what I'm I doing wrong here. thanks, todd -- Todd "Pier" Holloway Have a happy mind... I am no Mutt expert, but I'll take a shot at this one. :o) If I'm wrong, I'll shut up and go off into the corner until I know better. It seems as if you want to forward the message as a MIME part. Check the status of $mime_forward and $mime_forward_decode. If $mime_forward is set, (actually, you might want to use 'ask-yes' or 'ask-no' since it's a quad-option variable, selecting yes,) and $mime_forward_decode is unset, then the forwarded message with all of it's attachments should be included as an attachment to the message you are composing. Alternatively, you could use the attach-message command, which is bound to 'A' by default in compose. Either of these approaches might yield the results you desire. -- Mr. Wade -- Linux: The Choice of the GNU Generation
